link to cross compiling howto

git-svn-id: https://svn.code.sf.net/p/nsis/code/NSIS/trunk@3639 212acab6-be3b-0410-9dea-997c60f758d6
This commit is contained in:
kichik 2004-08-21 10:58:25 +00:00
parent 7c6eea5d98
commit ec0b2c6d26

View file

@ -8,7 +8,7 @@ If you don't have Microsoft Visual C++, you can download the free \W{http://msdn
You can also compile NSIS using \W{http://www.mingw.org/}{MinGW} and \W{http://www.mingw.org/msys.shtml}{MSYS} or \W{http://www.cygwin.com/}{Cygwin}, but this results in noticeably larger exeheads. To compile using MinGW, simply use `make'. Borland C++ or Open Watcom C/C++ should also work but probably require some makefile changes.
As of NSIS 2.01, the compiler, makensis, also compiles on POSIX platforms. POSIX platforms include Linux, *BSD, Mac OS X and others. You must first compile the exeheads to be able to compile makensis. This can be done on Windows using the methods explained above, or using a cross compiler. Once the exeheads are compiled, you must copy over the .h files in Source\\exehead\\Release-*. These .h files are automatically generated during the build process from the compiled exeheads. Official NSIS source code releases for POSIX include these .h files, so it is only needed to manually compile them if the source code was taken from CVS.
As of NSIS 2.01, the compiler, makensis, also compiles on POSIX platforms. POSIX platforms include Linux, *BSD, Mac OS X and others. You must first compile the exeheads to be able to compile makensis. This can be done on Windows using the methods explained above, or using a cross compiler (\W{http://www.libsdl.org/extras/win32/cross/README.txt}{HOWTO}). Once the exeheads are compiled, you must copy over the .h files in Source\\exehead\\Release-*. These .h files are automatically generated during the build process from the compiled exeheads. Official NSIS source code releases for POSIX include these .h files, so it is only needed to manually compile them if the source code was taken from CVS.
\\<b\\>Important notes for Microsoft Visual C++ 6.0 users:\\</b\\> You should install the latest \W{http://www.microsoft.com/msdownload/platformsdk/sdkupdate/}{Platform SDK}. Because of flaws in the libraries distributed with Microsoft Visual C++ 6.0, not installing the Platform SDK will result in crashes when using the CopyFiles command, see \W{http://forums.winamp.com/showthread.php?s=&threadid=131964}{this forum topic} for more information. Installing the \W{http://msdn.microsoft.com/vstudio/downloads/tools/ppack/download.aspx}{Processor Pack} is also highly recommended to decrease the size of the installer overhead.