Cross Compiling

From GNUstepWiki

(Difference between revisions)
Revision as of 14:53, 9 May 2008
Hns (Talk | contribs)
Cross Compiling and GNUstep
← Previous diff
Revision as of 14:59, 9 May 2008
Hns (Talk | contribs)
I have a GNUstep source running on Linux/GNUstep and want the same application to run on OSX
Next diff →
Line 7: Line 7:
=== I have a GNUstep source running on Linux/GNUstep and want the same application to run on OSX === === I have a GNUstep source running on Linux/GNUstep and want the same application to run on OSX ===
-You have several options - more or less complex. +You have several options - more or less complex.
-a) Copy source files to OSX +a) Copy source files to OSX and use gnustep-make
 + 
 +The simplest, and best option is obviously to install gnustep-make
 + 
 + ./configure
 + make
 + sudo make install
 + 
 +and then compile your project by typing 'make'. You get a native Apple OSX application compiled against the Apple OSX ObjC frameworks ... using
 +the same GNUmakefiles you were using on GNU/Linux/*BSD/Windows. :-)
 +
 +b) Copy source files to OSX and build using Xcode
Add a wrapping Xcode project (in addition to the GNUstep makefile) and configure it to compile directly on OSX for OSX using the OSX Cocoa frameworks. Add a wrapping Xcode project (in addition to the GNUstep makefile) and configure it to compile directly on OSX for OSX using the OSX Cocoa frameworks.
Line 24: Line 35:
The OSX .app bundle runs only on OSX, i.e. there is no single bundle that covers all architectures (unless you do some additional tricks). The OSX .app bundle runs only on OSX, i.e. there is no single bundle that covers all architectures (unless you do some additional tricks).
-b) Install GNUstep on OSX using MacPorts. +c) Install GNUstep on OSX using MacPorts.
Then, you can set up an identical build environment on both machines. Then, you can set up an identical build environment on both machines.
The drawback is that you don't have a "native" OSX application which you can easily launch by a double-click on the .app icon. The drawback is that you don't have a "native" OSX application which you can easily launch by a double-click on the .app icon.
-c) Real cross-compiling +Benoit Astruc writes: I think I have done this :
 +- I installed GNUstep Make and BaseAdditions on Mac OS X 10.3 (it was 2 years ago so not the Make 2.0 version, I don't know if it works with
 +the new version),
 +- I used a GNUmakefile like this one :
 + # This usually happens when you source GNUstep.sh, then run ./configure,
 + # then log out, then log in again and try to compile
 + ifeq ($(GNUSTEP_MAKEFILES),)
 + $(error You need to run the GNUstep configuration script before compiling!)
 + endif
 + include $(GNUSTEP_MAKEFILES)/common.make
 + APP_NAME = WRP
 + WRP_MAIN_MODEL_FILE = MainMenu
 + WRP_APPLICATION_ICON = WRP.icns
 + WRP_PRINCIPAL_CLASS = NSApplication
 + WRP_RESOURCE_FILES = gui/* Images/* Resources/*
 + WRP_OBJC_FILES = main.m \
 + ...
 + snip a bunch of sources files
 + ...
 + DEGeneralPrefsController.m \
 + GSStringCat.m
 + include GNUmakefile.preamble
 + include $(GNUSTEP_MAKEFILES)/application.make
 + 
 +There was a trick however, the first time I had to write manually some file, WRPInfo.plist if I remember well, and then it was used.
 +I don't do anything on this app since 2 years ago so I don't remember well, but I am pretty sure I had nothing more to do.
 +And the result was a perfectly Mac OS X app build with GNUstep make.
 + 
 + 
 +d) Real cross-compiling (building on Linux for MacOS X)
This means that you have a gcc version on your Linux machine that emits executables that run on OSX. Unfortunately, OSX uses MACH-O binaries and building a cross-compiling gcc is very tricky. This means that you have a gcc version on your Linux machine that emits executables that run on OSX. Unfortunately, OSX uses MACH-O binaries and building a cross-compiling gcc is very tricky.

Revision as of 14:59, 9 May 2008

Cross Compiling and GNUstep

depends on what you want to achieve.

The following is based on this discussion [[1]]

I have a GNUstep source running on Linux/GNUstep and want the same application to run on OSX

You have several options - more or less complex.

a) Copy source files to OSX and use gnustep-make

The simplest, and best option is obviously to install gnustep-make

 ./configure
 make
 sudo make install

and then compile your project by typing 'make'. You get a native Apple OSX application compiled against the Apple OSX ObjC frameworks ... using the same GNUmakefiles you were using on GNU/Linux/*BSD/Windows. :-)

b) Copy source files to OSX and build using Xcode

Add a wrapping Xcode project (in addition to the GNUstep makefile) and configure it to compile directly on OSX for OSX using the OSX Cocoa frameworks. You can share the sources e.g. through SVN. There is no problem having GNUmakefiles and some .xcodeproj in the same source code directory.

Examples: 1. SWK Browser from the GNUstep SWK project, DataBuilder from 2. GSCoreData (look into the sources at www.gna.org)

Development is done by either working on Linux and using GORM/Project Center and compiling for Linux. or on OSX opening the project in Xcode. The only thing to keep in mind is that you also update the Xcode project or the GNUmakefile if you add source files or resources. The GNUstep .app bundle is different and runs on Linux only. The OSX .app bundle runs only on OSX, i.e. there is no single bundle that covers all architectures (unless you do some additional tricks).

c) Install GNUstep on OSX using MacPorts.

Then, you can set up an identical build environment on both machines. The drawback is that you don't have a "native" OSX application which you can easily launch by a double-click on the .app icon.

Benoit Astruc writes: I think I have done this : - I installed GNUstep Make and BaseAdditions on Mac OS X 10.3 (it was 2 years ago so not the Make 2.0 version, I don't know if it works with the new version), - I used a GNUmakefile like this one :

 # This usually happens when you source GNUstep.sh, then run ./configure, 
 # then log out, then log in again and try to compile 
 ifeq ($(GNUSTEP_MAKEFILES),) 
    $(error You need to run the GNUstep configuration script before compiling!) 
 endif 
 include $(GNUSTEP_MAKEFILES)/common.make 
 APP_NAME = WRP 
 WRP_MAIN_MODEL_FILE = MainMenu 
 WRP_APPLICATION_ICON = WRP.icns 
 WRP_PRINCIPAL_CLASS = NSApplication 
 WRP_RESOURCE_FILES = gui/* Images/* Resources/* 
 WRP_OBJC_FILES = main.m \ 
 ... 
 snip a bunch of sources files 
 ... 
 DEGeneralPrefsController.m \ 
 GSStringCat.m 
 include GNUmakefile.preamble 
 include $(GNUSTEP_MAKEFILES)/application.make 

There was a trick however, the first time I had to write manually some file, WRPInfo.plist if I remember well, and then it was used. I don't do anything on this app since 2 years ago so I don't remember well, but I am pretty sure I had nothing more to do. And the result was a perfectly Mac OS X app build with GNUstep make.


d) Real cross-compiling (building on Linux for MacOS X)

This means that you have a gcc version on your Linux machine that emits executables that run on OSX. Unfortunately, OSX uses MACH-O binaries and building a cross-compiling gcc is very tricky. So I would not consider this as a reasonable option.

I have an Xcode project and want to run on Linux

a) your target machine has a compiler Here, you have to check that you are not using too specific frameworks. Then, add a GNUmakefile. Copy the files to your Linux system and run the GNUstep makefile.

b) your target machine is an embedded system In this case, you need a cross-compiler on the build host. This can be a full Linux machine or a OSX machine (but it is more difficult to get a working cross-compiler running on OSX).