usr/local/gcc-4.5.2-for-linux32/bin/i586-pc-linux-gcc -static for C linking You can add this path to your PATH shell variable, or invoke the tools with their full path name: for example /usr/local/gcc-4.5.2-for-linux32/bin/i586-pc-linux-gcc for gcc.įor better portability of Linux tools built with theses cross compilation chains, invoke the linker with the -static option, for example:
Within the installed directory, the contents.txt file contains the detail of cross-compiled archives.Īll tools are located in the bin sub directory. This is a cross compilation of GCC on Mac OS X.Ī package installs all files in the given installation directory. You can find here older releases of cross compilers for i386 Linux Yes, it is an error, ppc binaries for versions 1 and 2 install in an i386… directory. usr/local/i386-mingw32-3.4.5/ MinGW Binaries for ppcīinaries for pcc should work on Mac OS X.3 and later. MinGW 4.3.0 for Mac OS X (Intel).2 (40.7 MB)Ĭ, C++, Objective-C, Java, Ada, Fortran 77 MinGW Binaries for IntelĬ, C++, Objective-C, Objective C++, Java, Fortran You can find some sample code in MinGW sample code page.
Note tool names always begin by i386, even for Power PC: for example, /usr/local/ppc-mingw32-4.3.0/bin/i386-mingw32-gcc. You can add this path to your $PATH shell variable, or invoke the tools with their full path name: for example /usr/local/i386-mingw32-3.4.5/bin/i386-mingw32-gcc for gcc. This is a cross compilation of MinGW on Mac OS X.Ī package installs all files in the given intallation directory, for example in /usr/local/i386-mingw32-3.4.5for release 2 for Intel Mac.Īll tools are located in the bin sub directory.
Then I have built Mac OS X packages in order to make installation simplest. As I mainly work on Mac, I have decided to built GCC cross compilers for Windows and Linux. For some of my softwares, I needed to built a multi platform distribution package, including executable for Windows and Linux.
0 kommentar(er)
