[](https://gitter.im/jl777/SuperNET?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
iguana is easy to build. Start by cloning (or downloading) this repository.
this still needs to be ported, pthreads is the only non-native windows system functions being used. OS_portable.c and OS_nonportable.c have the few windows functions that are needed to be ported and also a compile/link process needs to be done. I think cygwin or even mingw would work, alternatively compiling the codebase with VS shouldnt be too much work. until this is done the instructions below about m_win32 and m_win64 wont actually work
##For native (win32, win64)##
This still needs to be ported, pthreads is the only non-native windows system functions being used. OS_portable.c and OS_nonportable.c have the few windows functions that are needed to be ported and also a compile/link process needs to be done. I think cygwin or even mingw would work, alternatively compiling the codebase with VS shouldnt be too much work. Until this is done the instructions below about m_win32 and m_win64 wont actually work.
##for chrome app##
you need to make sure the nacl sdk is properly installed and you are able to build the examples
Now you will need to get the external libs, which can be built from scratch using naclports or
there use the reference builds of libssl.a, libcrypto.a, libcurl.a and libz.a in the SuperNET/libs
You can just copy those over into $(NACL_SDK_ROOT)/lib/pnacl
##For chrome app##
You need to make sure the nacl sdk is properly installed and you are able to build the examples.
Now you will need to get the external libs, which can be built from scratch using naclports or there use the reference builds of libssl.a, libcrypto.a, libcurl.a and libz.a in the SuperNET/libs. You can just copy those over into $(NACL_SDK_ROOT)/lib/pnacl.
#ONETIME#
Now you are ready to build.
I try to make the build process as simple as possible, so there are no autoconf, autoreconf, configure, cmake, make, to get properly installed and running and run, etc. You do need a C compiler, like gcc
I try to make the build process as simple as possible, so there are no `autoconf`, `autoreconf`,`configure`, `cmake`, `make`, to get properly installed and running and run, etc. You do need a C compiler, like gcc.
The first time you need to build libcrypto777.a and to do that you need to run:
The **first time** you need to build libcrypto777.a and to do that you need to run:
For unix: ```./m_onetime m_unix```
For osx: ```./m_onetime m_osx```
For win32: ```./m_onetime m_win32```
@ -39,15 +47,10 @@ For win64: ```./m_win64```
The m_(OS) is a standard I follow and should be self explanatory. within each is usually just a few lines, ie compile all the .c files and link with the standard libs.
To build just iguana, you can ```cd``` into SuperNET/iguana and do ```./m_unix``` (or ```./m_osx```, ...)
To build just iguana, you can ```cd``` into SuperNET/iguana and do ```./m_unix``` (or ```./m_osx```, ...).
```./m_clean``` will remove the files created from the building
The above one line gets SuperNET installed, built and launched for unix.
After that ```./m_unix``` updates to latest
#RUNNING#
The native versions are command line applications: agents/iguana {JSON}
The chrome app pexe requires that the chrome is launched with a command line parameter (tools/chrome.localhost) and then browse to *http://127.0.0.1:7777* to see the pexe
flamingice
9 years ago