If you haven’t built Iguana before, first set up some environmental variables that the build system uses. Okay so to build Iguana assuming you are in the main directory of the mercurial git repo, execute the following commands:
cd ~/main2/Iguana
make thirdpartymake -j
You should see something like this, except you probably won’t unless you have a magical set of environmental variables set.
...
/wiki/spaces/DE/pages/4259841.
By the time the compile has finished you’ll see something like this:
...
See how it has produced the output iguana.tar.gz file?
The -j4 j flag is a little optimization which tells make that it’s okay to do a parallel make which makes the initial build of Iguana much faster. Subsequent builds are usually faster since they are incremental. You can read more about the /wiki/spaces/DEVELOPMEN/pages/1933329.
To run Iguana as a command line program you will need to change to the DBD directory, then type:
./iguana --run
...
This should start up Iguana on the default port. Open up the URL it shows at the bottom in a web browser.
...
The username and password will be set to the default “admin” and “password”. Log in and you should see a screen that requires you to enter a license key like this:
...
The easiest way to generate a license key for development purposes is to compile the command line license key utility by going to the directory it is in and compiling it:
...
Just run it, make sure you put in your own unique Iguana ID and it should spit out a license code for you:
...
Copy and past the license code into Iguana, it should look something like this:
...
You should now have a fully functional copy of Iguana running in your development sandbox.
If you want to delete all the files that the compilation process produces, use “make clean” in the Iguana directory. This a standard technique with make to remove files that are produced by the compilation. This is what make clean will look like:
...
/app/bin/iguana