How to create your own GTools project ------------------------------------- - Create the directory /LocalDeveloper - Copy the Headers directory into /LocalDeveloper - In a terminal window: cd /LocalDeveloper/Headers/GKappkit make This creates the precompiled header GKappkit.p - Run ProjectBuilder - Create a new project of the type 'Bundle' - In the 'Attributes' section, set 'Install in:' to $(HOME)/Library/GTools - In the 'Attributes' section, set 'Extension:' to GTool If you do not use NEXTSTEP 3.2, you can't set the Extension. - Create the md file. You can use the md file of any other GTool as template. Add the md file to 'Other Resources' in the PB section 'Files'. You might have to modify the 'Makefile.preamble', so that /LocalDeveloper/Headers will be amongst the include directories. Proceed as usual. When you did your first succesful 'make debug', create a symbolic link from the <name>.[bundle|GTool] directory in your source directory into ~/Library/GTools. Rename the link inside ~/Library/GTools from <name>.bundle to <name>.GTool if necessary. Tips for debugging: It is easiest to create a '.gdbinit' file inside your home directory. This should look about like this (modify the sourcepaths!) --------------------- dir ~/Projects/GTools/MyProject view set autoload-symbols on --------------------- To debug your GTool: in a terminal window, cd into the GTools.app directory. Call gdb: gdb GTools Then when ready: run You can't set breakpoints in your code, until your GTool has been loaded. (With the exception of 'fb', read the gdb manual). If you need to debug the startup of your GTool, have it loaded, set the breakpoint, and restart with 'run'. You can also use the 'SampleGTool' project as a template.
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Netfuture.ch.
