Difference between revisions of "Gorm Installation On Windows"
Jump to navigation
Jump to search
| Line 22: | Line 22: | ||
4) CVS versions of Gorm have install-windows.sh which contains the commands listed above. | 4) CVS versions of Gorm have install-windows.sh which contains the commands listed above. | ||
| + | |||
| + | === Why is the build process different on Windows? === | ||
| + | |||
| + | Because Windows uses the PE-COFF executable format which does not support weak-symbols. Unlike ELF, all symbols in programs using COFF (or one of it's variants) must have any and all symbols defined at compile time. Gorm utilizes weak symbols because it's palettes take advantage of some of the code in the Gorm application. This is normally okay on most operating systems, but on Windows it's not. | ||
| + | |||
| + | I am currently refactoring Gorm's build process to make it cleaner and to help symplify the it on all platforms. | ||
Revision as of 15:37, 26 March 2005
Steps to build Gorm on Windows
1) Install mingw as described here:
2) Go to the Gorm directory under gnustep/dev-apps/Gorm
3) Executing the following commands:
# First build the InterfaceBuilder library... ln -s GormLib InterfaceBuilder cd InterfaceBuilder make install
# Now build Gorm itself... cd ../ make
# Now install the palettes into the app and install make install
4) CVS versions of Gorm have install-windows.sh which contains the commands listed above.
Why is the build process different on Windows?
Because Windows uses the PE-COFF executable format which does not support weak-symbols. Unlike ELF, all symbols in programs using COFF (or one of it's variants) must have any and all symbols defined at compile time. Gorm utilizes weak symbols because it's palettes take advantage of some of the code in the Gorm application. This is normally okay on most operating systems, but on Windows it's not.
I am currently refactoring Gorm's build process to make it cleaner and to help symplify the it on all platforms.