Writing portable code - Revision history

Hns: /* When platform-specific code cannot be avoided */

2009-01-30T12:12:27Z

When platform-specific code cannot be avoided

Bheron: /* Xcode conversion */

2008-11-26T23:16:34Z

Xcode conversion

Bheron: /* Porting .nib files from OPENSTEP or Mac OS X 10.1 and earlier */

2008-11-26T23:15:33Z

Porting .nib files from OPENSTEP or Mac OS X 10.1 and earlier

Bheron: /* Porting .nib files from OPENSTEP or Mac OS X 10.1 and earlier */

2008-11-26T23:13:28Z

Porting .nib files from OPENSTEP or Mac OS X 10.1 and earlier

Geroldr: /* Porting from GNUstep to Cocoa */

2008-09-14T06:33:07Z

Porting from GNUstep to Cocoa

Geroldr: /* Porting from GNUstep to Cocoa */

2008-09-14T06:29:09Z

Porting from GNUstep to Cocoa

Martin: /* Xcode conversion */ add link

2007-10-28T03:36:34Z

Xcode conversion: add link

Cbv: Minor changes as suggested by Max Berger

2007-04-26T14:23:01Z

Minor changes as suggested by Max Berger

JC: /* Porting from GNUstep to Cocoa */

2007-03-26T02:51:52Z

Porting from GNUstep to Cocoa

Comrade: Messed-up MediaWiki link corrected ;-)

2006-09-12T18:48:37Z

Messed-up MediaWiki link corrected ;-)

← Older revision		Revision as of 12:12, 30 January 2009
Line 145:		Line 145:

	[[Category:Project procedures]]		[[Category:Project procedures]]
		+
		+	=== Cross Compiling ===
		+
		+	See [[Cross_Compiling]]

@@ Line 123: / Line 123: @@
 * how to convert Xcode project to GNUstep project (creating a GNUstep [http://www.gnustep.it/nicola/Tutorials/WritingMakefiles/index.html Makefile] or [[ProjectCenter]])
-* [[pbxbuild]]
+* [[pbxbuild]] - this program converts an Xcode project into a set of targets and directories in which you can build by simply using make.
 * PBTOMAKE. [http://www.macdevcenter.com/pub/a/mac/2004/04/20/xcodetounix.html xcodetounix] (download at [http://members.bellatlantic.net/%7Evze35xda/software.html]) is a tool for converting Xcode and Project Builder files to generic Unix Makefiles.  It would probably be a good start for converting to a GNUstep makefile.

← Older revision		Revision as of 23:15, 26 November 2008
Line 116:		Line 116:

	Since it's possible to load nibs into GNUstep application now, it should be easy to convert 10.2 or later nibs by simply loading them into Gorm and saving them as .gorm files. This is not strictly necessary since GNUstep can handle them natively.		Since it's possible to load nibs into GNUstep application now, it should be easy to convert 10.2 or later nibs by simply loading them into Gorm and saving them as .gorm files. This is not strictly necessary since GNUstep can handle them natively.
		+
		+	NOTE: Our recommendation for this is not to use the nib2gmodel conversion and simply to use the nibs directly, if you can or to convert them as described above by loading them into Interface Builder and saving them as the newer nib format.

	=== Xcode conversion ===		=== Xcode conversion ===

@@ Line 87: / Line 87: @@
 === Porting .nib files from OPENSTEP or Mac OS X 10.1 and earlier ===
-On Mac OS X, this is a simple matter of loading the .nibs into InterfaceBuilder.app and saving them in the new format. Another possibility is using nib2gmodel, the only one when porting from OPENSTEP, and mind you, you need to do the converting ''there''. First, get [http://freshmeat.net/projects/nib2gmodel/ nib2gmodel], follow the included instructions to build and install it.  Once that's done you're ready to begin:
+GNUstep can handle nibs from 10.2 or later of Mac OS X, but it can't read nibs made with NeXTSTEP, OpenStep or Mac OS 10.1 or earlier.   On the latest version of Mac OS X, this is a simple matter of loading the .nibs into Interface Builder.app and saving them in the 10.2 format.  Another possibility is using nib2gmodel, the only one when porting from OPENSTEP, and, mind you, you need to do the converting ''there''. First, get [http://freshmeat.net/projects/nib2gmodel/ nib2gmodel], follow the included instructions to build and install it.  Once that's done you're ready to begin:
 Run the nib2gmodel program on your nib:
@@ Line 112: / Line 112: @@
 After you've defined all of the unknown classes, Gorm should complete the conversion.  Once this is done you should save the result to make sure you don't loose your work.
 === Xcode conversion ===

@@ Line 62: / Line 62: @@
 * Enter the name and location you wish the Project to reside at
 * Copy your files from your GNUstep application into the new project
-* Using the "Add Existing Files" option to add these file to your project
+* Using the "Add Existing Files" option to add these files to your project
 You should preserve your original directory structure if you want to distribute one package for both GNUstep and Cocoa.

@@ Line 58: / Line 58: @@
 Do the following:
-* Open Xcode.
+* Open Xcode
 * Choose Application (if your project is an application)
 * Enter the name and location you wish the Project to reside at
 * Copy your files from your GNUstep application into the new project
-* Using the "Add Existing Files" option to add these file to your project.
+* Using the "Add Existing Files" option to add these file to your project
 You should preserve your original directory structure if you want to distribute one package for both GNUstep and Cocoa.

← Older revision		Revision as of 03:36, 28 October 2007
Line 116:		Line 116:

	* how to convert Xcode project to GNUstep project (creating a GNUstep [http://www.gnustep.it/nicola/Tutorials/WritingMakefiles/index.html Makefile] or [[ProjectCenter]])		* how to convert Xcode project to GNUstep project (creating a GNUstep [http://www.gnustep.it/nicola/Tutorials/WritingMakefiles/index.html Makefile] or [[ProjectCenter]])
		+
		+	* [[pbxbuild]]

	* PBTOMAKE. [http://www.macdevcenter.com/pub/a/mac/2004/04/20/xcodetounix.html xcodetounix] (download at [http://members.bellatlantic.net/%7Evze35xda/software.html]) is a tool for converting Xcode and Project Builder files to generic Unix Makefiles. It would probably be a good start for converting to a GNUstep makefile.		* PBTOMAKE. [http://www.macdevcenter.com/pub/a/mac/2004/04/20/xcodetounix.html xcodetounix] (download at [http://members.bellatlantic.net/%7Evze35xda/software.html]) is a tool for converting Xcode and Project Builder files to generic Unix Makefiles. It would probably be a good start for converting to a GNUstep makefile.

@@ Line 42: / Line 42: @@
 # [[Writing Makefiles|Write a new GNUstep make file]] for the project (very easy, still there is currently no automatic way to do so).
-# Make sure the Nib files are readable by GNUstep.  Make certain that they are 10.2.x or later nibs so that they can be read by GUI.  Another option is to load them into Gorm and convert them into .gorm files. If they're from OPENSTEP or Mac OS X 10.1 or earlier, see [[#Porting_.nib_files_from_OPENSTEP_or_Mac_OS_X_10.1_and_earlier|below]].
+# Make sure the Nib files are readable by GNUstep.
 # Provide an Info.plist.
@@ Line 73: / Line 75: @@
   #import <AppKit/AppKit.h>
-So you can easily work around this by providing your own or replace your include of <Cocoa/Cocoa.h> with just the above, which will also work on OS-X.
+On older GNUstep systems, you may have to work around this by providing your own or replace your include of <Cocoa/Cocoa.h> with just the above, which will also work on OS-X.
 === Distinguishing Between Cocoa and GNUstep ===

@@ Line 49: / Line 49: @@
 This should be an easy transition since GNUstep implements most of Cocoa, except for the very Apple specific classes such as the scripting extensions. Since Gorm does not yet save .nib files, you will need to create the interfaces using IB.   Also there is a gorm reading/parsing framework for Cocoa in the works as well, so please stay tuned.
-Will will need to:
+Will need to:
 * Make a Project Builder project for your app or

@@ Line 130: / Line 130: @@
 === When platform-specific code cannot be avoided ===
-There are cases where you may need to write platform-specific code, especially in the case of desktop applications and services which make use of facilities not standardised by POSIX or by the FoundationKit and AppKit  specifications, at least use [[standard platform macros|Identifying the target platform]].
+There are cases where you may need to write platform-specific code, especially in the case of desktop applications and services which make use of facilities not standardised by POSIX or by the FoundationKit and AppKit  specifications, at least use [[Identifying the target platform|standard platform macros]].
 These platform-specific, or even desktop-specific requirements could be re-used by other projects - and even enhance desktop-integration efforts for GNUstep applications - by abstracting out common code into currently hypothetical [[PlatformKit]] and [[DesktopServicesKit]] frameworks.
 [[Category:Project procedures]]