| | 71 | |
| | 72 | === Installing SpiderMonkey on *nix system === |
| | 73 | |
| | 74 | To Install SpiderMonkey Libraries on *nix systems: |
| | 75 | |
| | 76 | * Download the source code, either from mozilla site or from our site |
| | 77 | |
| | 78 | * Unpack in a temporary directory (let's call it $temp) |
| | 79 | |
| | 80 | * Change the directory into $temp/js/src/ cd $temp/js/src |
| | 81 | |
| | 82 | * Build the source using make -f Makefile.ref all followed by make -f Makefile.ref export |
| | 83 | |
| | 84 | * This last step will have put all the built binaries, libraries and headers in either $temp/dist/Linux_All_DBG.OBJ for linux systems, or $temp/dist/Darwin_DBG.OBJ for mac os x |
| | 85 | |
| | 86 | * Change directory into $temp/dist/Linux_All_DBG.OBJ (or Darwin_DBG_OBJ) cd $temp/dist/Linux_All_DBG.OBJ |
| | 87 | |
| | 88 | * Copy everything under include/ into the place where the compiler usually looks for header files (usually /usr/include) into a new directory called js, ie: cd include followed cp * /usr/include/js (Note: you might need to use su or sudo to get permission to copy these files) |
| | 89 | |
| | 90 | * Copy everything under lib/ into the directory where the runtime directories are located (usually /usr/lib) cd ../lib followed by cp * /usr/lib (Note: you might need to use su or sudo to get permission to copy these files) |
| | 91 | |
| | 92 | * Run ldconfig (if you don't, the library might not be found at runtime) |
| | 93 | |
| | 94 | * You are free to copy the binaries under bin/ into your system binary path as well (usuall /usr/bin), but it won't be necessary to build the engine |
| | 95 | Note: There are further instructions in build/workspaces/required-libraries-linux.txt |
