https://mediawiki.gnustep.org/api.php?action=feedcontributions&feedformat=atom&user=Tjyang 2026-04-05T02:43:12Z User contributions MediaWiki 1.35.7 https://mediawiki.gnustep.org/index.php?title=Developer_FAQ&diff=5341 2008-11-01T14:21:29Z

<p>Tjyang: /* How can I take part with a GNUstep autobuilder for the testfarm? */</p> <hr /> <div>[[Category:FAQ]]<br /> <br /> Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.<br /> <br /> == Compatibility ==<br /> <br /> === Is it easy to port OPENSTEP programs to GNUstep? ===<br /> <br /> It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === How about porting between Cocoa and GNUstep? ===<br /> <br /> It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === Tools for porting ===<br /> <br /> While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.<br /> <br /> * '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).<br /> * '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.<br /> * '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.<br /> * '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.<br /> * '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.<br /> <br /> === Can I transfer archived data from GNUstep to Cocoa? ===<br /> <br /> Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.<br /> <br /> The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.<br /> <br /> === Does distributed objects work between GNUstep and Cocoa? ===<br /> <br /> See the answer to the previous question (on archive compatibility) for why this won't work either.<br /> <br /> === Is there an Interface Builder for GNUstep? ===<br /> <br /> There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].<br /> <br /> === Can I use my original NIB files? ===<br /> It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later. <br /> <br /> Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.<br /> <br /> === Can one use the hybrid &quot;Objective-C++&quot; ? ===<br /> <br /> Yes. As of release 4.1 the GNU C Compiler (GCC) supports &quot;Objective-C++&quot;.<br /> <br /> === Is there a plan to support the Java/YellowBox Bindings? ===<br /> <br /> Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects. <br /> <br /> === What if I compile GNUstep under OPENSTEP/MacOS X? ===<br /> <br /> GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.<br /> <br /> You can, however, use a GNUstep program with an X11 server running on MacOSX.<br /> <br /> === Is the Objective C API for GTK related? ===<br /> <br /> No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.<br /> <br /> The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks. <br /> <br /> === How about implementing parts of the Application Kit with GTK? ===<br /> <br /> Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.<br /> <br /> That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome. <br /> <br /> == Compiling and Developing ==<br /> <br /> === How can I get started programming? ===<br /> Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)<br /> <br /> === Why doesn't GDB support Objective-C? ===<br /> As of GDB 6.0, gdb supports debugging of Objective-C code.<br /> <br /> == How can I help with GNUstep? ==<br /> <br /> The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.<br /> <br /> Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep. <br /> <br /> Here are the next steps: <br /> * Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]<br /> * Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.<br /> * For a bigger challenge, finish off part of the [[Roadmap]]<br /> <br /> === How do I start writing applications? ===<br /> <br /> You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.<br /> <br /> Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.<br /> <br /> === Helping develop GNUstep === <br /> <br /> There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.<br /> <br /> Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].<br /> <br /> Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.<br /> <br /> Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.<br /> <br /> Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation. <br /> <br /> Specific tasks are noted in the developers section on the GNUstep website.<br /> <br /> === Helping document GNUstep ===<br /> <br /> All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.<br /> <br /> Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.<br /> <br /> More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!<br /> <br /> Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.<br /> <br /> GNUstep documentation should have copyright assigned to the Free Software Foundation.<br /> <br /> === How do I assign my contribution? ===<br /> <br /> Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).<br /> <br /> === How do I update the task list? ===<br /> <br /> The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).<br /> <br /> One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.<br /> <br /> Send any changes or additions to bug-gnustep@gnu.org.<br /> <br /> A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.<br /> <br /> If a class or method is<br /> <br /> * in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.<br /> * in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP<br /> * in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X<br /> <br /> There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.<br /> <br /> === How do I start writing tests? ===<br /> <br /> You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.<br /> <br /> To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.<br /> <br /> === How can I help with the GNUstep website? ===<br /> <br /> '''Please consider contributing to this Wiki as opposed to the website.'''<br /> Contact Adam Fedor fedor@gnu.org, the maintainer.<br /> <br /> The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.<br /> <br /> If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.<br /> <br /> If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.<br /> <br /> The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.<br /> <br /> === How can I take part with a GNUstep autobuilder for the testfarm? ===<br /> * General Procedure<br /> ** Make sure your build system have a gcc compiler with objc support.<br /> *** run &quot;gcc -v&quot; to see if obc is on the list of --enable-language option<br /> ** mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> ** tar xjf startup.current.tar.bz2 ; tar xjf core.current.tar.bz2<br /> ** cd startup/scripts<br /> ** ./test-gnustep<br /> <br /> The results get posted to the gnustep-dev@gnu.org list and to http://ftp.gnustep.org/pub/testfarm/. <br /> The test script will automatically update using SVN if possible.<br /> ==== Fedora 9 ====<br /> An example on Fedora9 <br /> Error<br /> &lt;pre&gt;<br /> conftest.c:58:23: error: objc/objc.h: No such file or directory<br /> &lt;/pre&gt;<br /> <br /> Prework:<br /> &lt;pre&gt;<br /> sudo yum install libobjc gcc-objc gcc-objc++<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> [test@fc9 ~]$ gcc -v<br /> Using built-in specs.<br /> Target: i386-redhat-linux<br /> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-cpu=generic --build=i386-redhat-linux<br /> Thread model: posix<br /> gcc version 4.3.0 20080428 (Red Hat 4.3.0-8) (GCC)<br /> [test@fc9 ~]$ mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> [test@fc9 gnustep-testfarm]$ wget http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> --2008-11-01 08:28:12-- http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> Resolving ftp.gnustep.org... 81.201.178.155<br /> Connecting to ftp.gnustep.org|81.201.178.155|:80... connected.<br /> HTTP request sent, awaiting response... 200 OK<br /> Length: 3832637 (3.7M) [application/x-bzip2]<br /> Saving to: `startup.current.tar.bz2'<br /> <br /> 100%[======================================&gt;] 3,832,637 394K/s in 8.5s<br /> <br /> 2008-11-01 08:28:22 (443 KB/s) - `startup.current.tar.bz2' saved [3832637/3832637]<br /> <br /> [test@fc9 gnustep-testfarm]$ wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> --2008-11-01 08:28:32-- http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> Resolving ftp.gnustep.org... 81.201.178.155<br /> Connecting to ftp.gnustep.org|81.201.178.155|:80... connected.<br /> HTTP request sent, awaiting response... 200 OK<br /> Length: 8481316 (8.1M) [application/x-bzip2]<br /> Saving to: `core.current.tar.bz2'<br /> <br /> 100%[======================================&gt;] 8,481,316 519K/s in 18s<br /> <br /> 2008-11-01 08:28:50 (466 KB/s) - `core.current.tar.bz2' saved [8481316/8481316]<br /> <br /> [test@fc9 gnustep-testfarm]$ tar xjf startup.current.tar.bz2 ;tar xjf core.current.tar.bz2<br /> [test@fc9 gnustep-testfarm]$ cd startup/scripts/<br /> [test@fc9 scripts]$<br /> &lt;/pre&gt;<br /> <br /> ==== Solaris ====<br /> ==== Solaris 10 x86 ====<br /> * Solaris 10 x86 Procedure<br /> ** OS info<br /> *** Solaris 10 x86 Update 4, with everything installed.<br /> &lt;pre&gt;<br /> bash-3.00# cat /etc/release<br /> Solaris 10 8/07 s10x_u4wos_12b X86<br /> Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.<br /> Use is subject to license terms.<br /> Assembled 16 August 2007<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> * gcc<br /> ** Make sure you have a gcc compiler with objc support.<br /> *** gcc come with Solaris U4 doesn't have objective-C enabled.<br /> &lt;pre&gt;<br /> bash-3.00# /usr/sfw/bin/gcc -v<br /> Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs<br /> Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure <br /> --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as <br /> --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared<br /> Thread model: posix<br /> gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> <br /> ** TBA.<br /> <br /> == GNU Objective C Compiler and Runtime ==<br /> <br /> === What is the Objective C Runtime? ===<br /> <br /> The Objective C Runtime Library provides C functions and data structures required to execute an Objective C program.<br /> <br /> The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @&quot;&quot;-style string objects).<br /> <br /> It also has several differences over NeXT's implementation:<br /> <br /> * GNU's runtime provides &quot;selector-types&quot; along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).<br /> <br /> * Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.<br /> <br /> Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.<br /> <br /> <br /> === Where can I get a gcc compiler with Objective C support? ===<br /> *TBA.<br /> === How I can compile my own gcc compiler with objective-C support ? ===<br /> * TBA.<br /> === How I check if my gcc compiler has good objective C environment ? ===<br /> * TBA.<br /> <br /> == GNUstep Base Library ==<br /> <br /> === What is the GNUstep Base Library? ===<br /> <br /> The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops, and random number generators.<br /> <br /> It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).<br /> <br /> === What is its current state of development? ===<br /> <br /> GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.<br /> <br /> === What are the features of GNU Distributed Objects? ===<br /> <br /> GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.<br /> <br /> NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.<br /> Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU &quot;typed selector&quot; mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like. <br /> <br /> == GNUstep GUI Library ==<br /> <br /> === What is the GUI Library? ===<br /> <br /> The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many peripheral classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.<br /> <br /> It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.<br /> <br /> === Explain the organization of the front- and back-ends ===<br /> <br /> The GNUstep GUI Library is divided into a front- and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X Windows. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. Much work will be saved by this clean separation between front- and back-end, because it allows different platforms to share the large amount of front-end code.<br /> <br /> === What is the current state of development of the front-end? ===<br /> Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.<br /> <br /> === What is the current state of development of the back-ends? ===<br /> <br /> There are several backends currently available:<br /> <br /> * '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing. <br /> * '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality. It is currently the standard backend (as long as the required libraries are installed). <br /> * '''w32:''' This backend works on Windows and uses basic Windows drawing <br /> * '''cairo:''' An up-and-coming backend. It still relies on unpublished functions in the cairo library so using it is not for the beginner. <br /> <br /> == GNUstep DisplayGhostScript Server ==<br /> <br /> === What is the Display Ghostscript Server? ===<br /> <br /> It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.<br /> <br /> At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.<br /> <br /> === What is its current state of development? ===<br /> <br /> GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.<br /> <br /> Further development on DGS has been abandoned in favor of libraries such as Cairo and libart.<br /> <br /> === What is the relationship between the Display Ghostscript Server and X Windows? ===<br /> <br /> Display Ghostscript runs on top of X Windows.</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Developer_FAQ&diff=5340 2008-11-01T14:11:11Z

<p>Tjyang: /* Solaris 10 x86 */</p> <hr /> <div>[[Category:FAQ]]<br /> <br /> Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.<br /> <br /> == Compatibility ==<br /> <br /> === Is it easy to port OPENSTEP programs to GNUstep? ===<br /> <br /> It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === How about porting between Cocoa and GNUstep? ===<br /> <br /> It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === Tools for porting ===<br /> <br /> While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.<br /> <br /> * '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).<br /> * '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.<br /> * '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.<br /> * '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.<br /> * '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.<br /> <br /> === Can I transfer archived data from GNUstep to Cocoa? ===<br /> <br /> Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.<br /> <br /> The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.<br /> <br /> === Does distributed objects work between GNUstep and Cocoa? ===<br /> <br /> See the answer to the previous question (on archive compatibility) for why this won't work either.<br /> <br /> === Is there an Interface Builder for GNUstep? ===<br /> <br /> There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].<br /> <br /> === Can I use my original NIB files? ===<br /> It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later. <br /> <br /> Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.<br /> <br /> === Can one use the hybrid &quot;Objective-C++&quot; ? ===<br /> <br /> Yes. As of release 4.1 the GNU C Compiler (GCC) supports &quot;Objective-C++&quot;.<br /> <br /> === Is there a plan to support the Java/YellowBox Bindings? ===<br /> <br /> Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects. <br /> <br /> === What if I compile GNUstep under OPENSTEP/MacOS X? ===<br /> <br /> GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.<br /> <br /> You can, however, use a GNUstep program with an X11 server running on MacOSX.<br /> <br /> === Is the Objective C API for GTK related? ===<br /> <br /> No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.<br /> <br /> The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks. <br /> <br /> === How about implementing parts of the Application Kit with GTK? ===<br /> <br /> Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.<br /> <br /> That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome. <br /> <br /> == Compiling and Developing ==<br /> <br /> === How can I get started programming? ===<br /> Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)<br /> <br /> === Why doesn't GDB support Objective-C? ===<br /> As of GDB 6.0, gdb supports debugging of Objective-C code.<br /> <br /> == How can I help with GNUstep? ==<br /> <br /> The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.<br /> <br /> Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep. <br /> <br /> Here are the next steps: <br /> * Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]<br /> * Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.<br /> * For a bigger challenge, finish off part of the [[Roadmap]]<br /> <br /> === How do I start writing applications? ===<br /> <br /> You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.<br /> <br /> Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.<br /> <br /> === Helping develop GNUstep === <br /> <br /> There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.<br /> <br /> Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].<br /> <br /> Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.<br /> <br /> Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.<br /> <br /> Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation. <br /> <br /> Specific tasks are noted in the developers section on the GNUstep website.<br /> <br /> === Helping document GNUstep ===<br /> <br /> All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.<br /> <br /> Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.<br /> <br /> More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!<br /> <br /> Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.<br /> <br /> GNUstep documentation should have copyright assigned to the Free Software Foundation.<br /> <br /> === How do I assign my contribution? ===<br /> <br /> Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).<br /> <br /> === How do I update the task list? ===<br /> <br /> The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).<br /> <br /> One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.<br /> <br /> Send any changes or additions to bug-gnustep@gnu.org.<br /> <br /> A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.<br /> <br /> If a class or method is<br /> <br /> * in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.<br /> * in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP<br /> * in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X<br /> <br /> There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.<br /> <br /> === How do I start writing tests? ===<br /> <br /> You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.<br /> <br /> To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.<br /> <br /> === How can I help with the GNUstep website? ===<br /> <br /> '''Please consider contributing to this Wiki as opposed to the website.'''<br /> Contact Adam Fedor fedor@gnu.org, the maintainer.<br /> <br /> The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.<br /> <br /> If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.<br /> <br /> If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.<br /> <br /> The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.<br /> <br /> === How can I take part with a GNUstep autobuilder for the testfarm? ===<br /> * General Procedure<br /> ** Make sure your build system have a gcc compiler with objc support.<br /> *** run &quot;gcc -v&quot; to see if obc is on the list of --enable-language option<br /> ** mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> ** tar xjf startup.current.tar.bz2<br /> ** tar xjf core.current.tar.bz2<br /> ** cd startup/scripts<br /> ** ./test-gnustep<br /> <br /> The results get posted to the gnustep-dev@gnu.org list and to http://ftp.gnustep.org/pub/testfarm/. <br /> The test script will automatically update using SVN if possible.<br /> ==== Fedora 9 ====<br /> An example on Fedora9 <br /> Error<br /> &lt;pre&gt;<br /> conftest.c:58:23: error: objc/objc.h: No such file or directory<br /> &lt;/pre&gt;<br /> <br /> Prework:<br /> &lt;pre&gt;<br /> sudo yum install libobjc gcc-objc gcc-objc++<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> [test@fc9 ~]$ gcc -v<br /> Using built-in specs.<br /> Target: i386-redhat-linux<br /> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-cpu=generic --build=i386-redhat-linux<br /> Thread model: posix<br /> gcc version 4.3.0 20080428 (Red Hat 4.3.0-8) (GCC)<br /> [test@fc9 ~]$ mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> [test@fc9 gnustep-testfarm]$ wget http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> --2008-11-01 08:28:12-- http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> Resolving ftp.gnustep.org... 81.201.178.155<br /> Connecting to ftp.gnustep.org|81.201.178.155|:80... connected.<br /> HTTP request sent, awaiting response... 200 OK<br /> Length: 3832637 (3.7M) [application/x-bzip2]<br /> Saving to: `startup.current.tar.bz2'<br /> <br /> 100%[======================================&gt;] 3,832,637 394K/s in 8.5s<br /> <br /> 2008-11-01 08:28:22 (443 KB/s) - `startup.current.tar.bz2' saved [3832637/3832637]<br /> <br /> [test@fc9 gnustep-testfarm]$ wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> --2008-11-01 08:28:32-- http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> Resolving ftp.gnustep.org... 81.201.178.155<br /> Connecting to ftp.gnustep.org|81.201.178.155|:80... connected.<br /> HTTP request sent, awaiting response... 200 OK<br /> Length: 8481316 (8.1M) [application/x-bzip2]<br /> Saving to: `core.current.tar.bz2'<br /> <br /> 100%[======================================&gt;] 8,481,316 519K/s in 18s<br /> <br /> 2008-11-01 08:28:50 (466 KB/s) - `core.current.tar.bz2' saved [8481316/8481316]<br /> <br /> [test@fc9 gnustep-testfarm]$ tar xjf startup.current.tar.bz2 ;tar xjf core.current.tar.bz2<br /> [test@fc9 gnustep-testfarm]$ cd startup/scripts/<br /> [test@fc9 scripts]$<br /> &lt;/pre&gt;<br /> <br /> ==== Solaris ====<br /> ==== Solaris 10 x86 ====<br /> * Solaris 10 x86 Procedure<br /> ** OS info<br /> *** Solaris 10 x86 Update 4, with everything installed.<br /> &lt;pre&gt;<br /> bash-3.00# cat /etc/release<br /> Solaris 10 8/07 s10x_u4wos_12b X86<br /> Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.<br /> Use is subject to license terms.<br /> Assembled 16 August 2007<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> * gcc<br /> ** Make sure you have a gcc compiler with objc support.<br /> *** gcc come with Solaris U4 doesn't have objective-C enabled.<br /> &lt;pre&gt;<br /> bash-3.00# /usr/sfw/bin/gcc -v<br /> Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs<br /> Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure <br /> --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as <br /> --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared<br /> Thread model: posix<br /> gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> <br /> ** TBA.<br /> <br /> == GNU Objective C Compiler and Runtime ==<br /> <br /> === What is the Objective C Runtime? ===<br /> <br /> The Objective C Runtime Library provides C functions and data structures required to execute an Objective C program.<br /> <br /> The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @&quot;&quot;-style string objects).<br /> <br /> It also has several differences over NeXT's implementation:<br /> <br /> * GNU's runtime provides &quot;selector-types&quot; along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).<br /> <br /> * Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.<br /> <br /> Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.<br /> <br /> <br /> === Where can I get a gcc compiler with Objective C support? ===<br /> *TBA.<br /> === How I can compile my own gcc compiler with objective-C support ? ===<br /> * TBA.<br /> === How I check if my gcc compiler has good objective C environment ? ===<br /> * TBA.<br /> <br /> == GNUstep Base Library ==<br /> <br /> === What is the GNUstep Base Library? ===<br /> <br /> The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops, and random number generators.<br /> <br /> It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).<br /> <br /> === What is its current state of development? ===<br /> <br /> GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.<br /> <br /> === What are the features of GNU Distributed Objects? ===<br /> <br /> GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.<br /> <br /> NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.<br /> Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU &quot;typed selector&quot; mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like. <br /> <br /> == GNUstep GUI Library ==<br /> <br /> === What is the GUI Library? ===<br /> <br /> The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many peripheral classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.<br /> <br /> It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.<br /> <br /> === Explain the organization of the front- and back-ends ===<br /> <br /> The GNUstep GUI Library is divided into a front- and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X Windows. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. Much work will be saved by this clean separation between front- and back-end, because it allows different platforms to share the large amount of front-end code.<br /> <br /> === What is the current state of development of the front-end? ===<br /> Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.<br /> <br /> === What is the current state of development of the back-ends? ===<br /> <br /> There are several backends currently available:<br /> <br /> * '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing. <br /> * '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality. It is currently the standard backend (as long as the required libraries are installed). <br /> * '''w32:''' This backend works on Windows and uses basic Windows drawing <br /> * '''cairo:''' An up-and-coming backend. It still relies on unpublished functions in the cairo library so using it is not for the beginner. <br /> <br /> == GNUstep DisplayGhostScript Server ==<br /> <br /> === What is the Display Ghostscript Server? ===<br /> <br /> It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.<br /> <br /> At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.<br /> <br /> === What is its current state of development? ===<br /> <br /> GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.<br /> <br /> Further development on DGS has been abandoned in favor of libraries such as Cairo and libart.<br /> <br /> === What is the relationship between the Display Ghostscript Server and X Windows? ===<br /> <br /> Display Ghostscript runs on top of X Windows.</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Developer_FAQ&diff=5339 2008-11-01T13:56:14Z

<p>Tjyang: /* Fedora 9 */</p> <hr /> <div>[[Category:FAQ]]<br /> <br /> Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.<br /> <br /> == Compatibility ==<br /> <br /> === Is it easy to port OPENSTEP programs to GNUstep? ===<br /> <br /> It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === How about porting between Cocoa and GNUstep? ===<br /> <br /> It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === Tools for porting ===<br /> <br /> While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.<br /> <br /> * '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).<br /> * '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.<br /> * '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.<br /> * '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.<br /> * '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.<br /> <br /> === Can I transfer archived data from GNUstep to Cocoa? ===<br /> <br /> Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.<br /> <br /> The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.<br /> <br /> === Does distributed objects work between GNUstep and Cocoa? ===<br /> <br /> See the answer to the previous question (on archive compatibility) for why this won't work either.<br /> <br /> === Is there an Interface Builder for GNUstep? ===<br /> <br /> There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].<br /> <br /> === Can I use my original NIB files? ===<br /> It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later. <br /> <br /> Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.<br /> <br /> === Can one use the hybrid &quot;Objective-C++&quot; ? ===<br /> <br /> Yes. As of release 4.1 the GNU C Compiler (GCC) supports &quot;Objective-C++&quot;.<br /> <br /> === Is there a plan to support the Java/YellowBox Bindings? ===<br /> <br /> Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects. <br /> <br /> === What if I compile GNUstep under OPENSTEP/MacOS X? ===<br /> <br /> GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.<br /> <br /> You can, however, use a GNUstep program with an X11 server running on MacOSX.<br /> <br /> === Is the Objective C API for GTK related? ===<br /> <br /> No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.<br /> <br /> The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks. <br /> <br /> === How about implementing parts of the Application Kit with GTK? ===<br /> <br /> Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.<br /> <br /> That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome. <br /> <br /> == Compiling and Developing ==<br /> <br /> === How can I get started programming? ===<br /> Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)<br /> <br /> === Why doesn't GDB support Objective-C? ===<br /> As of GDB 6.0, gdb supports debugging of Objective-C code.<br /> <br /> == How can I help with GNUstep? ==<br /> <br /> The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.<br /> <br /> Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep. <br /> <br /> Here are the next steps: <br /> * Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]<br /> * Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.<br /> * For a bigger challenge, finish off part of the [[Roadmap]]<br /> <br /> === How do I start writing applications? ===<br /> <br /> You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.<br /> <br /> Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.<br /> <br /> === Helping develop GNUstep === <br /> <br /> There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.<br /> <br /> Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].<br /> <br /> Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.<br /> <br /> Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.<br /> <br /> Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation. <br /> <br /> Specific tasks are noted in the developers section on the GNUstep website.<br /> <br /> === Helping document GNUstep ===<br /> <br /> All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.<br /> <br /> Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.<br /> <br /> More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!<br /> <br /> Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.<br /> <br /> GNUstep documentation should have copyright assigned to the Free Software Foundation.<br /> <br /> === How do I assign my contribution? ===<br /> <br /> Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).<br /> <br /> === How do I update the task list? ===<br /> <br /> The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).<br /> <br /> One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.<br /> <br /> Send any changes or additions to bug-gnustep@gnu.org.<br /> <br /> A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.<br /> <br /> If a class or method is<br /> <br /> * in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.<br /> * in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP<br /> * in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X<br /> <br /> There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.<br /> <br /> === How do I start writing tests? ===<br /> <br /> You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.<br /> <br /> To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.<br /> <br /> === How can I help with the GNUstep website? ===<br /> <br /> '''Please consider contributing to this Wiki as opposed to the website.'''<br /> Contact Adam Fedor fedor@gnu.org, the maintainer.<br /> <br /> The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.<br /> <br /> If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.<br /> <br /> If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.<br /> <br /> The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.<br /> <br /> === How can I take part with a GNUstep autobuilder for the testfarm? ===<br /> * General Procedure<br /> ** Make sure your build system have a gcc compiler with objc support.<br /> *** run &quot;gcc -v&quot; to see if obc is on the list of --enable-language option<br /> ** mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> ** tar xjf startup.current.tar.bz2<br /> ** tar xjf core.current.tar.bz2<br /> ** cd startup/scripts<br /> ** ./test-gnustep<br /> <br /> The results get posted to the gnustep-dev@gnu.org list and to http://ftp.gnustep.org/pub/testfarm/. <br /> The test script will automatically update using SVN if possible.<br /> ==== Fedora 9 ====<br /> An example on Fedora9 <br /> Error<br /> &lt;pre&gt;<br /> conftest.c:58:23: error: objc/objc.h: No such file or directory<br /> &lt;/pre&gt;<br /> <br /> Prework:<br /> &lt;pre&gt;<br /> sudo yum install libobjc gcc-objc gcc-objc++<br /> &lt;/pre&gt;<br /> <br /> &lt;pre&gt;<br /> [test@fc9 ~]$ gcc -v<br /> Using built-in specs.<br /> Target: i386-redhat-linux<br /> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-cpu=generic --build=i386-redhat-linux<br /> Thread model: posix<br /> gcc version 4.3.0 20080428 (Red Hat 4.3.0-8) (GCC)<br /> [test@fc9 ~]$ mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> [test@fc9 gnustep-testfarm]$ wget http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> --2008-11-01 08:28:12-- http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> Resolving ftp.gnustep.org... 81.201.178.155<br /> Connecting to ftp.gnustep.org|81.201.178.155|:80... connected.<br /> HTTP request sent, awaiting response... 200 OK<br /> Length: 3832637 (3.7M) [application/x-bzip2]<br /> Saving to: `startup.current.tar.bz2'<br /> <br /> 100%[======================================&gt;] 3,832,637 394K/s in 8.5s<br /> <br /> 2008-11-01 08:28:22 (443 KB/s) - `startup.current.tar.bz2' saved [3832637/3832637]<br /> <br /> [test@fc9 gnustep-testfarm]$ wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> --2008-11-01 08:28:32-- http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> Resolving ftp.gnustep.org... 81.201.178.155<br /> Connecting to ftp.gnustep.org|81.201.178.155|:80... connected.<br /> HTTP request sent, awaiting response... 200 OK<br /> Length: 8481316 (8.1M) [application/x-bzip2]<br /> Saving to: `core.current.tar.bz2'<br /> <br /> 100%[======================================&gt;] 8,481,316 519K/s in 18s<br /> <br /> 2008-11-01 08:28:50 (466 KB/s) - `core.current.tar.bz2' saved [8481316/8481316]<br /> <br /> [test@fc9 gnustep-testfarm]$ tar xjf startup.current.tar.bz2 ;tar xjf core.current.tar.bz2<br /> [test@fc9 gnustep-testfarm]$ cd startup/scripts/<br /> [test@fc9 scripts]$<br /> &lt;/pre&gt;<br /> <br /> ==== Solaris ====<br /> ==== Solaris 10 x86 ====<br /> * Solaris 10 x86 Procedure<br /> ** OS info<br /> *** Solaris 10 x86 Update 4, with everything installed.<br /> &lt;pre&gt;<br /> bash-3.00# cat /etc/release<br /> Solaris 10 8/07 s10x_u4wos_12b X86<br /> Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.<br /> Use is subject to license terms.<br /> Assembled 16 August 2007<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> ** Make sure you have a gcc compiler with objc support.<br /> *** gcc come with Solaris U4 doesn't have objective-C enabled.<br /> &lt;pre&gt;<br /> bash-3.00# /usr/sfw/bin/gcc -v<br /> Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs<br /> Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure <br /> --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as <br /> --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared<br /> Thread model: posix<br /> gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> <br /> ** TBA.<br /> <br /> == GNU Objective C Compiler and Runtime ==<br /> <br /> === What is the Objective C Runtime? ===<br /> <br /> The Objective C Runtime Library provides C functions and data structures required to execute an Objective C program.<br /> <br /> The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @&quot;&quot;-style string objects).<br /> <br /> It also has several differences over NeXT's implementation:<br /> <br /> * GNU's runtime provides &quot;selector-types&quot; along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).<br /> <br /> * Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.<br /> <br /> Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.<br /> <br /> <br /> === Where can I get a gcc compiler with Objective C support? ===<br /> *TBA.<br /> === How I can compile my own gcc compiler with objective-C support ? ===<br /> * TBA.<br /> === How I check if my gcc compiler has good objective C environment ? ===<br /> * TBA.<br /> <br /> == GNUstep Base Library ==<br /> <br /> === What is the GNUstep Base Library? ===<br /> <br /> The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops, and random number generators.<br /> <br /> It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).<br /> <br /> === What is its current state of development? ===<br /> <br /> GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.<br /> <br /> === What are the features of GNU Distributed Objects? ===<br /> <br /> GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.<br /> <br /> NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.<br /> Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU &quot;typed selector&quot; mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like. <br /> <br /> == GNUstep GUI Library ==<br /> <br /> === What is the GUI Library? ===<br /> <br /> The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many peripheral classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.<br /> <br /> It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.<br /> <br /> === Explain the organization of the front- and back-ends ===<br /> <br /> The GNUstep GUI Library is divided into a front- and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X Windows. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. Much work will be saved by this clean separation between front- and back-end, because it allows different platforms to share the large amount of front-end code.<br /> <br /> === What is the current state of development of the front-end? ===<br /> Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.<br /> <br /> === What is the current state of development of the back-ends? ===<br /> <br /> There are several backends currently available:<br /> <br /> * '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing. <br /> * '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality. It is currently the standard backend (as long as the required libraries are installed). <br /> * '''w32:''' This backend works on Windows and uses basic Windows drawing <br /> * '''cairo:''' An up-and-coming backend. It still relies on unpublished functions in the cairo library so using it is not for the beginner. <br /> <br /> == GNUstep DisplayGhostScript Server ==<br /> <br /> === What is the Display Ghostscript Server? ===<br /> <br /> It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.<br /> <br /> At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.<br /> <br /> === What is its current state of development? ===<br /> <br /> GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.<br /> <br /> Further development on DGS has been abandoned in favor of libraries such as Cairo and libart.<br /> <br /> === What is the relationship between the Display Ghostscript Server and X Windows? ===<br /> <br /> Display Ghostscript runs on top of X Windows.</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Developer_FAQ&diff=5338 2008-11-01T13:53:51Z

<p>Tjyang: /* Fedora 9 */</p> <hr /> <div>[[Category:FAQ]]<br /> <br /> Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.<br /> <br /> == Compatibility ==<br /> <br /> === Is it easy to port OPENSTEP programs to GNUstep? ===<br /> <br /> It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === How about porting between Cocoa and GNUstep? ===<br /> <br /> It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === Tools for porting ===<br /> <br /> While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.<br /> <br /> * '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).<br /> * '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.<br /> * '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.<br /> * '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.<br /> * '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.<br /> <br /> === Can I transfer archived data from GNUstep to Cocoa? ===<br /> <br /> Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.<br /> <br /> The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.<br /> <br /> === Does distributed objects work between GNUstep and Cocoa? ===<br /> <br /> See the answer to the previous question (on archive compatibility) for why this won't work either.<br /> <br /> === Is there an Interface Builder for GNUstep? ===<br /> <br /> There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].<br /> <br /> === Can I use my original NIB files? ===<br /> It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later. <br /> <br /> Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.<br /> <br /> === Can one use the hybrid &quot;Objective-C++&quot; ? ===<br /> <br /> Yes. As of release 4.1 the GNU C Compiler (GCC) supports &quot;Objective-C++&quot;.<br /> <br /> === Is there a plan to support the Java/YellowBox Bindings? ===<br /> <br /> Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects. <br /> <br /> === What if I compile GNUstep under OPENSTEP/MacOS X? ===<br /> <br /> GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.<br /> <br /> You can, however, use a GNUstep program with an X11 server running on MacOSX.<br /> <br /> === Is the Objective C API for GTK related? ===<br /> <br /> No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.<br /> <br /> The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks. <br /> <br /> === How about implementing parts of the Application Kit with GTK? ===<br /> <br /> Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.<br /> <br /> That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome. <br /> <br /> == Compiling and Developing ==<br /> <br /> === How can I get started programming? ===<br /> Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)<br /> <br /> === Why doesn't GDB support Objective-C? ===<br /> As of GDB 6.0, gdb supports debugging of Objective-C code.<br /> <br /> == How can I help with GNUstep? ==<br /> <br /> The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.<br /> <br /> Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep. <br /> <br /> Here are the next steps: <br /> * Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]<br /> * Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.<br /> * For a bigger challenge, finish off part of the [[Roadmap]]<br /> <br /> === How do I start writing applications? ===<br /> <br /> You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.<br /> <br /> Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.<br /> <br /> === Helping develop GNUstep === <br /> <br /> There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.<br /> <br /> Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].<br /> <br /> Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.<br /> <br /> Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.<br /> <br /> Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation. <br /> <br /> Specific tasks are noted in the developers section on the GNUstep website.<br /> <br /> === Helping document GNUstep ===<br /> <br /> All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.<br /> <br /> Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.<br /> <br /> More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!<br /> <br /> Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.<br /> <br /> GNUstep documentation should have copyright assigned to the Free Software Foundation.<br /> <br /> === How do I assign my contribution? ===<br /> <br /> Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).<br /> <br /> === How do I update the task list? ===<br /> <br /> The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).<br /> <br /> One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.<br /> <br /> Send any changes or additions to bug-gnustep@gnu.org.<br /> <br /> A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.<br /> <br /> If a class or method is<br /> <br /> * in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.<br /> * in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP<br /> * in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X<br /> <br /> There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.<br /> <br /> === How do I start writing tests? ===<br /> <br /> You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.<br /> <br /> To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.<br /> <br /> === How can I help with the GNUstep website? ===<br /> <br /> '''Please consider contributing to this Wiki as opposed to the website.'''<br /> Contact Adam Fedor fedor@gnu.org, the maintainer.<br /> <br /> The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.<br /> <br /> If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.<br /> <br /> If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.<br /> <br /> The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.<br /> <br /> === How can I take part with a GNUstep autobuilder for the testfarm? ===<br /> * General Procedure<br /> ** Make sure your build system have a gcc compiler with objc support.<br /> *** run &quot;gcc -v&quot; to see if obc is on the list of --enable-language option<br /> ** mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> ** tar xjf startup.current.tar.bz2<br /> ** tar xjf core.current.tar.bz2<br /> ** cd startup/scripts<br /> ** ./test-gnustep<br /> <br /> The results get posted to the gnustep-dev@gnu.org list and to http://ftp.gnustep.org/pub/testfarm/. <br /> The test script will automatically update using SVN if possible.<br /> ==== Fedora 9 ====<br /> An example on Fedora9 <br /> &lt;pre&gt;<br /> [test@fc9 ~]$ gcc -v<br /> Using built-in specs.<br /> Target: i386-redhat-linux<br /> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-cpu=generic --build=i386-redhat-linux<br /> Thread model: posix<br /> gcc version 4.3.0 20080428 (Red Hat 4.3.0-8) (GCC)<br /> [test@fc9 ~]$ mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> [test@fc9 gnustep-testfarm]$ wget http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> --2008-11-01 08:28:12-- http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> Resolving ftp.gnustep.org... 81.201.178.155<br /> Connecting to ftp.gnustep.org|81.201.178.155|:80... connected.<br /> HTTP request sent, awaiting response... 200 OK<br /> Length: 3832637 (3.7M) [application/x-bzip2]<br /> Saving to: `startup.current.tar.bz2'<br /> <br /> 100%[======================================&gt;] 3,832,637 394K/s in 8.5s<br /> <br /> 2008-11-01 08:28:22 (443 KB/s) - `startup.current.tar.bz2' saved [3832637/3832637]<br /> <br /> [test@fc9 gnustep-testfarm]$ wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> --2008-11-01 08:28:32-- http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> Resolving ftp.gnustep.org... 81.201.178.155<br /> Connecting to ftp.gnustep.org|81.201.178.155|:80... connected.<br /> HTTP request sent, awaiting response... 200 OK<br /> Length: 8481316 (8.1M) [application/x-bzip2]<br /> Saving to: `core.current.tar.bz2'<br /> <br /> 100%[======================================&gt;] 8,481,316 519K/s in 18s<br /> <br /> 2008-11-01 08:28:50 (466 KB/s) - `core.current.tar.bz2' saved [8481316/8481316]<br /> <br /> [test@fc9 gnustep-testfarm]$ tar xjf startup.current.tar.bz2 ;tar xjf core.current.tar.bz2<br /> [test@fc9 gnustep-testfarm]$ cd startup/scripts/<br /> [test@fc9 scripts]$<br /> &lt;/pre&gt;<br /> <br /> error<br /> &lt;pre&gt;<br /> conftest.c:58:23: error: objc/objc.h: No such file or directory<br /> <br /> sudo yum install libobjc gcc-objc gcc-objc++<br /> &lt;/pre&gt;<br /> <br /> ==== Solaris ====<br /> ==== Solaris 10 x86 ====<br /> * Solaris 10 x86 Procedure<br /> ** OS info<br /> *** Solaris 10 x86 Update 4, with everything installed.<br /> &lt;pre&gt;<br /> bash-3.00# cat /etc/release<br /> Solaris 10 8/07 s10x_u4wos_12b X86<br /> Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.<br /> Use is subject to license terms.<br /> Assembled 16 August 2007<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> ** Make sure you have a gcc compiler with objc support.<br /> *** gcc come with Solaris U4 doesn't have objective-C enabled.<br /> &lt;pre&gt;<br /> bash-3.00# /usr/sfw/bin/gcc -v<br /> Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs<br /> Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure <br /> --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as <br /> --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared<br /> Thread model: posix<br /> gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> <br /> ** TBA.<br /> <br /> == GNU Objective C Compiler and Runtime ==<br /> <br /> === What is the Objective C Runtime? ===<br /> <br /> The Objective C Runtime Library provides C functions and data structures required to execute an Objective C program.<br /> <br /> The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @&quot;&quot;-style string objects).<br /> <br /> It also has several differences over NeXT's implementation:<br /> <br /> * GNU's runtime provides &quot;selector-types&quot; along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).<br /> <br /> * Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.<br /> <br /> Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.<br /> <br /> <br /> === Where can I get a gcc compiler with Objective C support? ===<br /> *TBA.<br /> === How I can compile my own gcc compiler with objective-C support ? ===<br /> * TBA.<br /> === How I check if my gcc compiler has good objective C environment ? ===<br /> * TBA.<br /> <br /> == GNUstep Base Library ==<br /> <br /> === What is the GNUstep Base Library? ===<br /> <br /> The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops, and random number generators.<br /> <br /> It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).<br /> <br /> === What is its current state of development? ===<br /> <br /> GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.<br /> <br /> === What are the features of GNU Distributed Objects? ===<br /> <br /> GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.<br /> <br /> NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.<br /> Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU &quot;typed selector&quot; mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like. <br /> <br /> == GNUstep GUI Library ==<br /> <br /> === What is the GUI Library? ===<br /> <br /> The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many peripheral classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.<br /> <br /> It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.<br /> <br /> === Explain the organization of the front- and back-ends ===<br /> <br /> The GNUstep GUI Library is divided into a front- and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X Windows. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. Much work will be saved by this clean separation between front- and back-end, because it allows different platforms to share the large amount of front-end code.<br /> <br /> === What is the current state of development of the front-end? ===<br /> Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.<br /> <br /> === What is the current state of development of the back-ends? ===<br /> <br /> There are several backends currently available:<br /> <br /> * '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing. <br /> * '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality. It is currently the standard backend (as long as the required libraries are installed). <br /> * '''w32:''' This backend works on Windows and uses basic Windows drawing <br /> * '''cairo:''' An up-and-coming backend. It still relies on unpublished functions in the cairo library so using it is not for the beginner. <br /> <br /> == GNUstep DisplayGhostScript Server ==<br /> <br /> === What is the Display Ghostscript Server? ===<br /> <br /> It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.<br /> <br /> At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.<br /> <br /> === What is its current state of development? ===<br /> <br /> GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.<br /> <br /> Further development on DGS has been abandoned in favor of libraries such as Cairo and libart.<br /> <br /> === What is the relationship between the Display Ghostscript Server and X Windows? ===<br /> <br /> Display Ghostscript runs on top of X Windows.</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Developer_FAQ&diff=5337 2008-11-01T13:50:10Z

<p>Tjyang: /* Fedora 9 */</p> <hr /> <div>[[Category:FAQ]]<br /> <br /> Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.<br /> <br /> == Compatibility ==<br /> <br /> === Is it easy to port OPENSTEP programs to GNUstep? ===<br /> <br /> It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === How about porting between Cocoa and GNUstep? ===<br /> <br /> It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === Tools for porting ===<br /> <br /> While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.<br /> <br /> * '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).<br /> * '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.<br /> * '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.<br /> * '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.<br /> * '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.<br /> <br /> === Can I transfer archived data from GNUstep to Cocoa? ===<br /> <br /> Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.<br /> <br /> The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.<br /> <br /> === Does distributed objects work between GNUstep and Cocoa? ===<br /> <br /> See the answer to the previous question (on archive compatibility) for why this won't work either.<br /> <br /> === Is there an Interface Builder for GNUstep? ===<br /> <br /> There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].<br /> <br /> === Can I use my original NIB files? ===<br /> It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later. <br /> <br /> Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.<br /> <br /> === Can one use the hybrid &quot;Objective-C++&quot; ? ===<br /> <br /> Yes. As of release 4.1 the GNU C Compiler (GCC) supports &quot;Objective-C++&quot;.<br /> <br /> === Is there a plan to support the Java/YellowBox Bindings? ===<br /> <br /> Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects. <br /> <br /> === What if I compile GNUstep under OPENSTEP/MacOS X? ===<br /> <br /> GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.<br /> <br /> You can, however, use a GNUstep program with an X11 server running on MacOSX.<br /> <br /> === Is the Objective C API for GTK related? ===<br /> <br /> No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.<br /> <br /> The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks. <br /> <br /> === How about implementing parts of the Application Kit with GTK? ===<br /> <br /> Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.<br /> <br /> That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome. <br /> <br /> == Compiling and Developing ==<br /> <br /> === How can I get started programming? ===<br /> Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)<br /> <br /> === Why doesn't GDB support Objective-C? ===<br /> As of GDB 6.0, gdb supports debugging of Objective-C code.<br /> <br /> == How can I help with GNUstep? ==<br /> <br /> The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.<br /> <br /> Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep. <br /> <br /> Here are the next steps: <br /> * Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]<br /> * Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.<br /> * For a bigger challenge, finish off part of the [[Roadmap]]<br /> <br /> === How do I start writing applications? ===<br /> <br /> You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.<br /> <br /> Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.<br /> <br /> === Helping develop GNUstep === <br /> <br /> There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.<br /> <br /> Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].<br /> <br /> Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.<br /> <br /> Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.<br /> <br /> Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation. <br /> <br /> Specific tasks are noted in the developers section on the GNUstep website.<br /> <br /> === Helping document GNUstep ===<br /> <br /> All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.<br /> <br /> Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.<br /> <br /> More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!<br /> <br /> Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.<br /> <br /> GNUstep documentation should have copyright assigned to the Free Software Foundation.<br /> <br /> === How do I assign my contribution? ===<br /> <br /> Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).<br /> <br /> === How do I update the task list? ===<br /> <br /> The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).<br /> <br /> One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.<br /> <br /> Send any changes or additions to bug-gnustep@gnu.org.<br /> <br /> A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.<br /> <br /> If a class or method is<br /> <br /> * in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.<br /> * in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP<br /> * in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X<br /> <br /> There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.<br /> <br /> === How do I start writing tests? ===<br /> <br /> You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.<br /> <br /> To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.<br /> <br /> === How can I help with the GNUstep website? ===<br /> <br /> '''Please consider contributing to this Wiki as opposed to the website.'''<br /> Contact Adam Fedor fedor@gnu.org, the maintainer.<br /> <br /> The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.<br /> <br /> If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.<br /> <br /> If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.<br /> <br /> The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.<br /> <br /> === How can I take part with a GNUstep autobuilder for the testfarm? ===<br /> * General Procedure<br /> ** Make sure your build system have a gcc compiler with objc support.<br /> *** run &quot;gcc -v&quot; to see if obc is on the list of --enable-language option<br /> ** mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> ** tar xjf startup.current.tar.bz2<br /> ** tar xjf core.current.tar.bz2<br /> ** cd startup/scripts<br /> ** ./test-gnustep<br /> <br /> The results get posted to the gnustep-dev@gnu.org list and to http://ftp.gnustep.org/pub/testfarm/. <br /> The test script will automatically update using SVN if possible.<br /> ==== Fedora 9 ====<br /> An example on Fedora9 <br /> &lt;pre&gt;<br /> [test@fc9 ~]$ gcc -v<br /> Using built-in specs.<br /> Target: i386-redhat-linux<br /> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-cpu=generic --build=i386-redhat-linux<br /> Thread model: posix<br /> gcc version 4.3.0 20080428 (Red Hat 4.3.0-8) (GCC)<br /> [test@fc9 ~]$ mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> [test@fc9 gnustep-testfarm]$ wget http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> --2008-11-01 08:28:12-- http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> Resolving ftp.gnustep.org... 81.201.178.155<br /> Connecting to ftp.gnustep.org|81.201.178.155|:80... connected.<br /> HTTP request sent, awaiting response... 200 OK<br /> Length: 3832637 (3.7M) [application/x-bzip2]<br /> Saving to: `startup.current.tar.bz2'<br /> <br /> 100%[======================================&gt;] 3,832,637 394K/s in 8.5s<br /> <br /> 2008-11-01 08:28:22 (443 KB/s) - `startup.current.tar.bz2' saved [3832637/3832637]<br /> <br /> [test@fc9 gnustep-testfarm]$ wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> --2008-11-01 08:28:32-- http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> Resolving ftp.gnustep.org... 81.201.178.155<br /> Connecting to ftp.gnustep.org|81.201.178.155|:80... connected.<br /> HTTP request sent, awaiting response... 200 OK<br /> Length: 8481316 (8.1M) [application/x-bzip2]<br /> Saving to: `core.current.tar.bz2'<br /> <br /> 100%[======================================&gt;] 8,481,316 519K/s in 18s<br /> <br /> 2008-11-01 08:28:50 (466 KB/s) - `core.current.tar.bz2' saved [8481316/8481316]<br /> <br /> [test@fc9 gnustep-testfarm]$ tar xjf startup.current.tar.bz2 ;tar xjf core.current.tar.bz2<br /> [test@fc9 gnustep-testfarm]$ cd startup/scripts/<br /> [test@fc9 scripts]$<br /> &lt;/pre&gt;<br /> <br /> error<br /> &lt;pre&gt;<br /> conftest.c:58:23: error: objc/objc.h: No such file or directory<br /> <br /> sudo yum install libobjc.i386<br /> &lt;/pre&gt;<br /> <br /> ==== Solaris ====<br /> ==== Solaris 10 x86 ====<br /> * Solaris 10 x86 Procedure<br /> ** OS info<br /> *** Solaris 10 x86 Update 4, with everything installed.<br /> &lt;pre&gt;<br /> bash-3.00# cat /etc/release<br /> Solaris 10 8/07 s10x_u4wos_12b X86<br /> Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.<br /> Use is subject to license terms.<br /> Assembled 16 August 2007<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> ** Make sure you have a gcc compiler with objc support.<br /> *** gcc come with Solaris U4 doesn't have objective-C enabled.<br /> &lt;pre&gt;<br /> bash-3.00# /usr/sfw/bin/gcc -v<br /> Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs<br /> Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure <br /> --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as <br /> --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared<br /> Thread model: posix<br /> gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> <br /> ** TBA.<br /> <br /> == GNU Objective C Compiler and Runtime ==<br /> <br /> === What is the Objective C Runtime? ===<br /> <br /> The Objective C Runtime Library provides C functions and data structures required to execute an Objective C program.<br /> <br /> The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @&quot;&quot;-style string objects).<br /> <br /> It also has several differences over NeXT's implementation:<br /> <br /> * GNU's runtime provides &quot;selector-types&quot; along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).<br /> <br /> * Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.<br /> <br /> Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.<br /> <br /> <br /> === Where can I get a gcc compiler with Objective C support? ===<br /> *TBA.<br /> === How I can compile my own gcc compiler with objective-C support ? ===<br /> * TBA.<br /> === How I check if my gcc compiler has good objective C environment ? ===<br /> * TBA.<br /> <br /> == GNUstep Base Library ==<br /> <br /> === What is the GNUstep Base Library? ===<br /> <br /> The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops, and random number generators.<br /> <br /> It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).<br /> <br /> === What is its current state of development? ===<br /> <br /> GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.<br /> <br /> === What are the features of GNU Distributed Objects? ===<br /> <br /> GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.<br /> <br /> NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.<br /> Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU &quot;typed selector&quot; mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like. <br /> <br /> == GNUstep GUI Library ==<br /> <br /> === What is the GUI Library? ===<br /> <br /> The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many peripheral classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.<br /> <br /> It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.<br /> <br /> === Explain the organization of the front- and back-ends ===<br /> <br /> The GNUstep GUI Library is divided into a front- and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X Windows. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. Much work will be saved by this clean separation between front- and back-end, because it allows different platforms to share the large amount of front-end code.<br /> <br /> === What is the current state of development of the front-end? ===<br /> Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.<br /> <br /> === What is the current state of development of the back-ends? ===<br /> <br /> There are several backends currently available:<br /> <br /> * '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing. <br /> * '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality. It is currently the standard backend (as long as the required libraries are installed). <br /> * '''w32:''' This backend works on Windows and uses basic Windows drawing <br /> * '''cairo:''' An up-and-coming backend. It still relies on unpublished functions in the cairo library so using it is not for the beginner. <br /> <br /> == GNUstep DisplayGhostScript Server ==<br /> <br /> === What is the Display Ghostscript Server? ===<br /> <br /> It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.<br /> <br /> At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.<br /> <br /> === What is its current state of development? ===<br /> <br /> GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.<br /> <br /> Further development on DGS has been abandoned in favor of libraries such as Cairo and libart.<br /> <br /> === What is the relationship between the Display Ghostscript Server and X Windows? ===<br /> <br /> Display Ghostscript runs on top of X Windows.</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Developer_FAQ&diff=5336 2008-11-01T13:49:46Z

<p>Tjyang: /* Fedora 9 */</p> <hr /> <div>[[Category:FAQ]]<br /> <br /> Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.<br /> <br /> == Compatibility ==<br /> <br /> === Is it easy to port OPENSTEP programs to GNUstep? ===<br /> <br /> It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === How about porting between Cocoa and GNUstep? ===<br /> <br /> It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === Tools for porting ===<br /> <br /> While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.<br /> <br /> * '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).<br /> * '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.<br /> * '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.<br /> * '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.<br /> * '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.<br /> <br /> === Can I transfer archived data from GNUstep to Cocoa? ===<br /> <br /> Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.<br /> <br /> The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.<br /> <br /> === Does distributed objects work between GNUstep and Cocoa? ===<br /> <br /> See the answer to the previous question (on archive compatibility) for why this won't work either.<br /> <br /> === Is there an Interface Builder for GNUstep? ===<br /> <br /> There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].<br /> <br /> === Can I use my original NIB files? ===<br /> It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later. <br /> <br /> Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.<br /> <br /> === Can one use the hybrid &quot;Objective-C++&quot; ? ===<br /> <br /> Yes. As of release 4.1 the GNU C Compiler (GCC) supports &quot;Objective-C++&quot;.<br /> <br /> === Is there a plan to support the Java/YellowBox Bindings? ===<br /> <br /> Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects. <br /> <br /> === What if I compile GNUstep under OPENSTEP/MacOS X? ===<br /> <br /> GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.<br /> <br /> You can, however, use a GNUstep program with an X11 server running on MacOSX.<br /> <br /> === Is the Objective C API for GTK related? ===<br /> <br /> No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.<br /> <br /> The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks. <br /> <br /> === How about implementing parts of the Application Kit with GTK? ===<br /> <br /> Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.<br /> <br /> That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome. <br /> <br /> == Compiling and Developing ==<br /> <br /> === How can I get started programming? ===<br /> Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)<br /> <br /> === Why doesn't GDB support Objective-C? ===<br /> As of GDB 6.0, gdb supports debugging of Objective-C code.<br /> <br /> == How can I help with GNUstep? ==<br /> <br /> The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.<br /> <br /> Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep. <br /> <br /> Here are the next steps: <br /> * Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]<br /> * Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.<br /> * For a bigger challenge, finish off part of the [[Roadmap]]<br /> <br /> === How do I start writing applications? ===<br /> <br /> You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.<br /> <br /> Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.<br /> <br /> === Helping develop GNUstep === <br /> <br /> There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.<br /> <br /> Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].<br /> <br /> Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.<br /> <br /> Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.<br /> <br /> Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation. <br /> <br /> Specific tasks are noted in the developers section on the GNUstep website.<br /> <br /> === Helping document GNUstep ===<br /> <br /> All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.<br /> <br /> Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.<br /> <br /> More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!<br /> <br /> Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.<br /> <br /> GNUstep documentation should have copyright assigned to the Free Software Foundation.<br /> <br /> === How do I assign my contribution? ===<br /> <br /> Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).<br /> <br /> === How do I update the task list? ===<br /> <br /> The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).<br /> <br /> One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.<br /> <br /> Send any changes or additions to bug-gnustep@gnu.org.<br /> <br /> A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.<br /> <br /> If a class or method is<br /> <br /> * in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.<br /> * in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP<br /> * in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X<br /> <br /> There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.<br /> <br /> === How do I start writing tests? ===<br /> <br /> You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.<br /> <br /> To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.<br /> <br /> === How can I help with the GNUstep website? ===<br /> <br /> '''Please consider contributing to this Wiki as opposed to the website.'''<br /> Contact Adam Fedor fedor@gnu.org, the maintainer.<br /> <br /> The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.<br /> <br /> If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.<br /> <br /> If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.<br /> <br /> The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.<br /> <br /> === How can I take part with a GNUstep autobuilder for the testfarm? ===<br /> * General Procedure<br /> ** Make sure your build system have a gcc compiler with objc support.<br /> *** run &quot;gcc -v&quot; to see if obc is on the list of --enable-language option<br /> ** mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> ** tar xjf startup.current.tar.bz2<br /> ** tar xjf core.current.tar.bz2<br /> ** cd startup/scripts<br /> ** ./test-gnustep<br /> <br /> The results get posted to the gnustep-dev@gnu.org list and to http://ftp.gnustep.org/pub/testfarm/. <br /> The test script will automatically update using SVN if possible.<br /> ==== Fedora 9 ====<br /> An example on Fedora9 <br /> &lt;pre&gt;<br /> [test@fc9 ~]$ gcc -v<br /> Using built-in specs.<br /> Target: i386-redhat-linux<br /> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-cpu=generic --build=i386-redhat-linux<br /> Thread model: posix<br /> gcc version 4.3.0 20080428 (Red Hat 4.3.0-8) (GCC)<br /> [test@fc9 ~]$ mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> [test@fc9 gnustep-testfarm]$ wget http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> --2008-11-01 08:28:12-- http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> Resolving ftp.gnustep.org... 81.201.178.155<br /> Connecting to ftp.gnustep.org|81.201.178.155|:80... connected.<br /> HTTP request sent, awaiting response... 200 OK<br /> Length: 3832637 (3.7M) [application/x-bzip2]<br /> Saving to: `startup.current.tar.bz2'<br /> <br /> 100%[======================================&gt;] 3,832,637 394K/s in 8.5s<br /> <br /> 2008-11-01 08:28:22 (443 KB/s) - `startup.current.tar.bz2' saved [3832637/3832637]<br /> <br /> [test@fc9 gnustep-testfarm]$ wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> --2008-11-01 08:28:32-- http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> Resolving ftp.gnustep.org... 81.201.178.155<br /> Connecting to ftp.gnustep.org|81.201.178.155|:80... connected.<br /> HTTP request sent, awaiting response... 200 OK<br /> Length: 8481316 (8.1M) [application/x-bzip2]<br /> Saving to: `core.current.tar.bz2'<br /> <br /> 100%[======================================&gt;] 8,481,316 519K/s in 18s<br /> <br /> 2008-11-01 08:28:50 (466 KB/s) - `core.current.tar.bz2' saved [8481316/8481316]<br /> <br /> [test@fc9 gnustep-testfarm]$ tar xjf startup.current.tar.bz2 ;tar xjf core.current.tar.bz2<br /> [test@fc9 gnustep-testfarm]$ cd startup/scripts/<br /> [test@fc9 scripts]$<br /> &lt;/pre&gt;<br /> <br /> error<br /> &lt;pre&gt;<br /> conftest.c:58:23: error: objc/objc.h: No such file or directory<br /> &lt;/pre&gt;<br /> <br /> ==== Solaris ====<br /> ==== Solaris 10 x86 ====<br /> * Solaris 10 x86 Procedure<br /> ** OS info<br /> *** Solaris 10 x86 Update 4, with everything installed.<br /> &lt;pre&gt;<br /> bash-3.00# cat /etc/release<br /> Solaris 10 8/07 s10x_u4wos_12b X86<br /> Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.<br /> Use is subject to license terms.<br /> Assembled 16 August 2007<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> ** Make sure you have a gcc compiler with objc support.<br /> *** gcc come with Solaris U4 doesn't have objective-C enabled.<br /> &lt;pre&gt;<br /> bash-3.00# /usr/sfw/bin/gcc -v<br /> Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs<br /> Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure <br /> --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as <br /> --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared<br /> Thread model: posix<br /> gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> <br /> ** TBA.<br /> <br /> == GNU Objective C Compiler and Runtime ==<br /> <br /> === What is the Objective C Runtime? ===<br /> <br /> The Objective C Runtime Library provides C functions and data structures required to execute an Objective C program.<br /> <br /> The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @&quot;&quot;-style string objects).<br /> <br /> It also has several differences over NeXT's implementation:<br /> <br /> * GNU's runtime provides &quot;selector-types&quot; along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).<br /> <br /> * Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.<br /> <br /> Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.<br /> <br /> <br /> === Where can I get a gcc compiler with Objective C support? ===<br /> *TBA.<br /> === How I can compile my own gcc compiler with objective-C support ? ===<br /> * TBA.<br /> === How I check if my gcc compiler has good objective C environment ? ===<br /> * TBA.<br /> <br /> == GNUstep Base Library ==<br /> <br /> === What is the GNUstep Base Library? ===<br /> <br /> The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops, and random number generators.<br /> <br /> It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).<br /> <br /> === What is its current state of development? ===<br /> <br /> GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.<br /> <br /> === What are the features of GNU Distributed Objects? ===<br /> <br /> GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.<br /> <br /> NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.<br /> Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU &quot;typed selector&quot; mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like. <br /> <br /> == GNUstep GUI Library ==<br /> <br /> === What is the GUI Library? ===<br /> <br /> The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many peripheral classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.<br /> <br /> It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.<br /> <br /> === Explain the organization of the front- and back-ends ===<br /> <br /> The GNUstep GUI Library is divided into a front- and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X Windows. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. Much work will be saved by this clean separation between front- and back-end, because it allows different platforms to share the large amount of front-end code.<br /> <br /> === What is the current state of development of the front-end? ===<br /> Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.<br /> <br /> === What is the current state of development of the back-ends? ===<br /> <br /> There are several backends currently available:<br /> <br /> * '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing. <br /> * '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality. It is currently the standard backend (as long as the required libraries are installed). <br /> * '''w32:''' This backend works on Windows and uses basic Windows drawing <br /> * '''cairo:''' An up-and-coming backend. It still relies on unpublished functions in the cairo library so using it is not for the beginner. <br /> <br /> == GNUstep DisplayGhostScript Server ==<br /> <br /> === What is the Display Ghostscript Server? ===<br /> <br /> It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.<br /> <br /> At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.<br /> <br /> === What is its current state of development? ===<br /> <br /> GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.<br /> <br /> Further development on DGS has been abandoned in favor of libraries such as Cairo and libart.<br /> <br /> === What is the relationship between the Display Ghostscript Server and X Windows? ===<br /> <br /> Display Ghostscript runs on top of X Windows.</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Developer_FAQ&diff=5335 2008-11-01T13:32:27Z

<p>Tjyang: /* Fedora 6 */</p> <hr /> <div>[[Category:FAQ]]<br /> <br /> Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.<br /> <br /> == Compatibility ==<br /> <br /> === Is it easy to port OPENSTEP programs to GNUstep? ===<br /> <br /> It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === How about porting between Cocoa and GNUstep? ===<br /> <br /> It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === Tools for porting ===<br /> <br /> While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.<br /> <br /> * '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).<br /> * '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.<br /> * '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.<br /> * '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.<br /> * '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.<br /> <br /> === Can I transfer archived data from GNUstep to Cocoa? ===<br /> <br /> Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.<br /> <br /> The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.<br /> <br /> === Does distributed objects work between GNUstep and Cocoa? ===<br /> <br /> See the answer to the previous question (on archive compatibility) for why this won't work either.<br /> <br /> === Is there an Interface Builder for GNUstep? ===<br /> <br /> There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].<br /> <br /> === Can I use my original NIB files? ===<br /> It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later. <br /> <br /> Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.<br /> <br /> === Can one use the hybrid &quot;Objective-C++&quot; ? ===<br /> <br /> Yes. As of release 4.1 the GNU C Compiler (GCC) supports &quot;Objective-C++&quot;.<br /> <br /> === Is there a plan to support the Java/YellowBox Bindings? ===<br /> <br /> Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects. <br /> <br /> === What if I compile GNUstep under OPENSTEP/MacOS X? ===<br /> <br /> GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.<br /> <br /> You can, however, use a GNUstep program with an X11 server running on MacOSX.<br /> <br /> === Is the Objective C API for GTK related? ===<br /> <br /> No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.<br /> <br /> The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks. <br /> <br /> === How about implementing parts of the Application Kit with GTK? ===<br /> <br /> Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.<br /> <br /> That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome. <br /> <br /> == Compiling and Developing ==<br /> <br /> === How can I get started programming? ===<br /> Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)<br /> <br /> === Why doesn't GDB support Objective-C? ===<br /> As of GDB 6.0, gdb supports debugging of Objective-C code.<br /> <br /> == How can I help with GNUstep? ==<br /> <br /> The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.<br /> <br /> Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep. <br /> <br /> Here are the next steps: <br /> * Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]<br /> * Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.<br /> * For a bigger challenge, finish off part of the [[Roadmap]]<br /> <br /> === How do I start writing applications? ===<br /> <br /> You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.<br /> <br /> Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.<br /> <br /> === Helping develop GNUstep === <br /> <br /> There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.<br /> <br /> Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].<br /> <br /> Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.<br /> <br /> Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.<br /> <br /> Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation. <br /> <br /> Specific tasks are noted in the developers section on the GNUstep website.<br /> <br /> === Helping document GNUstep ===<br /> <br /> All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.<br /> <br /> Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.<br /> <br /> More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!<br /> <br /> Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.<br /> <br /> GNUstep documentation should have copyright assigned to the Free Software Foundation.<br /> <br /> === How do I assign my contribution? ===<br /> <br /> Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).<br /> <br /> === How do I update the task list? ===<br /> <br /> The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).<br /> <br /> One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.<br /> <br /> Send any changes or additions to bug-gnustep@gnu.org.<br /> <br /> A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.<br /> <br /> If a class or method is<br /> <br /> * in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.<br /> * in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP<br /> * in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X<br /> <br /> There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.<br /> <br /> === How do I start writing tests? ===<br /> <br /> You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.<br /> <br /> To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.<br /> <br /> === How can I help with the GNUstep website? ===<br /> <br /> '''Please consider contributing to this Wiki as opposed to the website.'''<br /> Contact Adam Fedor fedor@gnu.org, the maintainer.<br /> <br /> The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.<br /> <br /> If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.<br /> <br /> If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.<br /> <br /> The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.<br /> <br /> === How can I take part with a GNUstep autobuilder for the testfarm? ===<br /> * General Procedure<br /> ** Make sure your build system have a gcc compiler with objc support.<br /> *** run &quot;gcc -v&quot; to see if obc is on the list of --enable-language option<br /> ** mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> ** tar xjf startup.current.tar.bz2<br /> ** tar xjf core.current.tar.bz2<br /> ** cd startup/scripts<br /> ** ./test-gnustep<br /> <br /> The results get posted to the gnustep-dev@gnu.org list and to http://ftp.gnustep.org/pub/testfarm/. <br /> The test script will automatically update using SVN if possible.<br /> ==== Fedora 9 ====<br /> An example on Fedora9 <br /> &lt;pre&gt;<br /> [test@fc9 ~]$ gcc -v<br /> Using built-in specs.<br /> Target: i386-redhat-linux<br /> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-cpu=generic --build=i386-redhat-linux<br /> Thread model: posix<br /> gcc version 4.3.0 20080428 (Red Hat 4.3.0-8) (GCC)<br /> [test@fc9 ~]$ mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> [test@fc9 gnustep-testfarm]$ wget http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> --2008-11-01 08:28:12-- http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> Resolving ftp.gnustep.org... 81.201.178.155<br /> Connecting to ftp.gnustep.org|81.201.178.155|:80... connected.<br /> HTTP request sent, awaiting response... 200 OK<br /> Length: 3832637 (3.7M) [application/x-bzip2]<br /> Saving to: `startup.current.tar.bz2'<br /> <br /> 100%[======================================&gt;] 3,832,637 394K/s in 8.5s<br /> <br /> 2008-11-01 08:28:22 (443 KB/s) - `startup.current.tar.bz2' saved [3832637/3832637]<br /> <br /> [test@fc9 gnustep-testfarm]$ wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> --2008-11-01 08:28:32-- http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> Resolving ftp.gnustep.org... 81.201.178.155<br /> Connecting to ftp.gnustep.org|81.201.178.155|:80... connected.<br /> HTTP request sent, awaiting response... 200 OK<br /> Length: 8481316 (8.1M) [application/x-bzip2]<br /> Saving to: `core.current.tar.bz2'<br /> <br /> 100%[======================================&gt;] 8,481,316 519K/s in 18s<br /> <br /> 2008-11-01 08:28:50 (466 KB/s) - `core.current.tar.bz2' saved [8481316/8481316]<br /> <br /> [test@fc9 gnustep-testfarm]$ tar xjf startup.current.tar.bz2 ;tar xjf core.current.tar.bz2<br /> [test@fc9 gnustep-testfarm]$ cd startup/scripts/<br /> [test@fc9 scripts]$<br /> &lt;/pre&gt;<br /> <br /> ==== Solaris ====<br /> ==== Solaris 10 x86 ====<br /> * Solaris 10 x86 Procedure<br /> ** OS info<br /> *** Solaris 10 x86 Update 4, with everything installed.<br /> &lt;pre&gt;<br /> bash-3.00# cat /etc/release<br /> Solaris 10 8/07 s10x_u4wos_12b X86<br /> Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.<br /> Use is subject to license terms.<br /> Assembled 16 August 2007<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> ** Make sure you have a gcc compiler with objc support.<br /> *** gcc come with Solaris U4 doesn't have objective-C enabled.<br /> &lt;pre&gt;<br /> bash-3.00# /usr/sfw/bin/gcc -v<br /> Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs<br /> Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure <br /> --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as <br /> --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared<br /> Thread model: posix<br /> gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> <br /> ** TBA.<br /> <br /> == GNU Objective C Compiler and Runtime ==<br /> <br /> === What is the Objective C Runtime? ===<br /> <br /> The Objective C Runtime Library provides C functions and data structures required to execute an Objective C program.<br /> <br /> The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @&quot;&quot;-style string objects).<br /> <br /> It also has several differences over NeXT's implementation:<br /> <br /> * GNU's runtime provides &quot;selector-types&quot; along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).<br /> <br /> * Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.<br /> <br /> Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.<br /> <br /> <br /> === Where can I get a gcc compiler with Objective C support? ===<br /> *TBA.<br /> === How I can compile my own gcc compiler with objective-C support ? ===<br /> * TBA.<br /> === How I check if my gcc compiler has good objective C environment ? ===<br /> * TBA.<br /> <br /> == GNUstep Base Library ==<br /> <br /> === What is the GNUstep Base Library? ===<br /> <br /> The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops, and random number generators.<br /> <br /> It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).<br /> <br /> === What is its current state of development? ===<br /> <br /> GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.<br /> <br /> === What are the features of GNU Distributed Objects? ===<br /> <br /> GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.<br /> <br /> NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.<br /> Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU &quot;typed selector&quot; mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like. <br /> <br /> == GNUstep GUI Library ==<br /> <br /> === What is the GUI Library? ===<br /> <br /> The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many peripheral classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.<br /> <br /> It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.<br /> <br /> === Explain the organization of the front- and back-ends ===<br /> <br /> The GNUstep GUI Library is divided into a front- and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X Windows. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. Much work will be saved by this clean separation between front- and back-end, because it allows different platforms to share the large amount of front-end code.<br /> <br /> === What is the current state of development of the front-end? ===<br /> Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.<br /> <br /> === What is the current state of development of the back-ends? ===<br /> <br /> There are several backends currently available:<br /> <br /> * '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing. <br /> * '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality. It is currently the standard backend (as long as the required libraries are installed). <br /> * '''w32:''' This backend works on Windows and uses basic Windows drawing <br /> * '''cairo:''' An up-and-coming backend. It still relies on unpublished functions in the cairo library so using it is not for the beginner. <br /> <br /> == GNUstep DisplayGhostScript Server ==<br /> <br /> === What is the Display Ghostscript Server? ===<br /> <br /> It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.<br /> <br /> At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.<br /> <br /> === What is its current state of development? ===<br /> <br /> GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.<br /> <br /> Further development on DGS has been abandoned in favor of libraries such as Cairo and libart.<br /> <br /> === What is the relationship between the Display Ghostscript Server and X Windows? ===<br /> <br /> Display Ghostscript runs on top of X Windows.</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=GNUstep_and_HPMS_HowTO&diff=5247 2008-05-31T10:32:16Z

<p>Tjyang: </p> <hr /> <div>* What is TWW HPMS ?<br /> * Why I want to use TWW HPMS ?<br /> * How do I compile GNUStep System using TWW HPMS ?</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=GNUstep_and_HPMS_HowTO&diff=5246 2008-05-31T10:31:36Z

<p>Tjyang: </p> <hr /> <div>* How do I compile GNUStep System using TWW HPMS ?</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=GNUStep_VirtualBox&diff=5184 2008-04-23T02:54:24Z

<p>Tjyang: /* [http://www.virtualbox.org/ VirtualBox] */</p> <hr /> <div>= Why ? =<br /> * To avoid the complex task of GNUStep compilation chain-reaction. Deploy and Develop !<br /> * Run one version of GNUStep on Windows, Linux, Solaris and Mac OS X.<br /> <br /> = [http://www.virtualbox.org/ VirtualBox] =<br /> Like VMWare player, it is also a free software, except it come with source code.<br /> <br /> You can download following version of virtualbox [https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_SMI-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=innotek-1.5.6-G-F@CDS-CDS_SMI here]<br /> * VirtualBox for Intel Mac<br /> * VirtualBox for Windows XP<br /> * Virtualbox for Linux<br /> * VirtualBox for OpenSolaris<br /> <br /> == Install GNUStep VirtualBox from GNUStep Live CD ==<br /> TBA</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=GNUStep_VirtualBox&diff=5183 2008-04-23T02:52:23Z

<p>Tjyang: /* Why ? */</p> <hr /> <div>= Why ? =<br /> * To avoid the complex task of GNUStep compilation chain-reaction. Deploy and Develop !<br /> * Run one version of GNUStep on Windows, Linux, Solaris and Mac OS X.<br /> <br /> = [http://www.virtualbox.org/ VirtualBox] =<br /> Like VMWare player, it is also a free software, except it come with source code.<br /> * VirtualBox for Intel Mac<br /> * VirtualBox for Windows XP<br /> * Virtualbox for Linux<br /> * VirtualBox for OpenSolaris<br /> <br /> == Install GNUStep VirtualBox from GNUStep Live CD ==<br /> TBA</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=GNUStep_VMWare&diff=5182 2008-04-23T02:51:29Z

<p>Tjyang: </p> <hr /> <div>= Why Creating a GNUStep VMWare appliance ? =<br /> * VMWare player is free, stable and back by commercial company VMWare Inc.<br /> * Deploy GNUStep without the painful compilation process.<br /> * Running one version of GNUStep on Windows and Linux.<br /> == Developer Version ==<br /> == End User Version ==</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=GNUStep_VirtualBox&diff=5181 2008-04-23T02:47:58Z

<p>Tjyang: </p> <hr /> <div>= Why ? =<br /> To avoid the complex task of GNUStep compilation chain-reaction. Deploy and Develop !<br /> <br /> = [http://www.virtualbox.org/ VirtualBox] =<br /> Like VMWare player, it is also a free software, except it come with source code.<br /> * VirtualBox for Intel Mac<br /> * VirtualBox for Windows XP<br /> * Virtualbox for Linux<br /> * VirtualBox for OpenSolaris<br /> <br /> == Install GNUStep VirtualBox from GNUStep Live CD ==<br /> TBA</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=GNUStep_VirtualBox&diff=5180 2008-04-23T02:45:23Z

<p>Tjyang: /* [http://www.virtualbox.org/ VirtualBox] */</p> <hr /> <div>= [http://www.virtualbox.org/ VirtualBox] =<br /> Like VMWare player, it is also a free software, except it come with source code.<br /> * VirtualBox for Intel Mac<br /> * VirtualBox for Windows XP<br /> * Virtualbox for Linux<br /> * VirtualBox for OpenSolaris<br /> <br /> == Install GNUStep VirtualBox from GNUStep Live CD ==<br /> TBA</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=GNUStep_VirtualBox&diff=5179 2008-04-23T02:44:27Z

<p>Tjyang: /* VirtualBox */</p> <hr /> <div>= [http://www.virtualbox.org/ VirtualBox] =<br /> <br /> * VirtualBox for Intel Mac<br /> * VirtualBox for Windows XP<br /> * Virtualbox for Linux<br /> * VirtualBox for OpenSolaris<br /> <br /> == Install GNUStep VirtualBox from GNUStep Live CD ==<br /> TBA</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=GNUStep_VirtualBox&diff=5178 2008-04-23T02:43:20Z

<p>Tjyang: /* VirtualBox */</p> <hr /> <div>= VirtualBox =<br /> <br /> * VirtualBox for Intel Mac<br /> * VirtualBox for Windows XP<br /> * Virtualbox for Linux<br /> * VirtualBox for OpenSolaris<br /> <br /> == Install GNUStep VirtualBox from GNUStep Live CD ==<br /> TBA</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=GNUStep_VirtualBox&diff=5177 2008-04-23T02:42:13Z

<p>Tjyang: /* VirtualBox */</p> <hr /> <div>= VirtualBox =<br /> <br /> * VirtualBox for Intel Mac<br /> * VirtualBox for Windows XP<br /> * Virtualbox for Linux<br /> * VirtualBox for OpenSolaris</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=GNUStep_VirtualBox&diff=5176 2008-04-23T02:41:25Z

<p>Tjyang: </p> <hr /> <div>= VirtualBox =<br /> * VirtualBox for Intel Mac<br /> * VirtualBox for Windows XP<br /> * Virtualbox for Linux<br /> * VirtualBox for OpenSolaris</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=GNUStep_VMWare&diff=5175 2008-04-23T02:39:25Z

<p>Tjyang: /* Creating a GNUStep VMWare appliance */</p> <hr /> <div>= Creating a GNUStep VMWare appliance =<br /> == Developer Version ==<br /> == End User Version ==</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=GNUStep_VMWare&diff=5174 2008-04-23T02:39:12Z

<p>Tjyang: </p> <hr /> <div>=Creating a GNUStep VMWare appliance =<br /> == Developer Version ==<br /> == End User Version ==</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Developer_FAQ&diff=4960 2007-12-12T23:42:13Z

<p>Tjyang: /* How can I take part with a GNUstep autobuilder for the testfarm? */</p> <hr /> <div>[[Category:FAQ]]<br /> <br /> Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.<br /> <br /> == Compatibility ==<br /> <br /> === Is it easy to port OPENSTEP programs to GNUstep? ===<br /> <br /> It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === How about porting between Cocoa and GNUstep? ===<br /> <br /> It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === Tools for porting ===<br /> <br /> While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.<br /> <br /> * '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).<br /> * '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.<br /> * '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.<br /> * '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.<br /> * '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.<br /> <br /> === Can I transfer archived data from GNUstep to Cocoa? ===<br /> <br /> Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.<br /> <br /> The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.<br /> <br /> === Does distributed objects work between GNUstep and Cocoa? ===<br /> <br /> See the answer to the previous question (on archive compatibility) for why this won't work either.<br /> <br /> === Is there an Interface Builder for GNUstep? ===<br /> <br /> There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].<br /> <br /> === Can I use my original NIB files? ===<br /> It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later. <br /> <br /> Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.<br /> <br /> === Can one use the hybrid &quot;Objective-C++&quot; ? ===<br /> <br /> Yes. As of release 4.1 the GNU C Compiler (GCC) supports &quot;Objective-C++&quot;.<br /> <br /> === Is there a plan to support the Java/YellowBox Bindings? ===<br /> <br /> Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects. <br /> <br /> === What if I compile GNUstep under OPENSTEP/MacOS X? ===<br /> <br /> GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.<br /> <br /> You can, however, use a GNUstep program with an X11 server running on MacOSX.<br /> <br /> === Is the Objective C API for GTK related? ===<br /> <br /> No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.<br /> <br /> The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks. <br /> <br /> === How about implementing parts of the Application Kit with GTK? ===<br /> <br /> Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.<br /> <br /> That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome. <br /> <br /> == Compiling and Developing ==<br /> <br /> === How can I get started programming? ===<br /> Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)<br /> <br /> === Why doesn't GDB support Objective-C? ===<br /> As of GDB 6.0, gdb supports debugging of Objective-C code.<br /> <br /> == How can I help with GNUstep? ==<br /> <br /> The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.<br /> <br /> Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep. <br /> <br /> Here are the next steps: <br /> * Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]<br /> * Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.<br /> * For a bigger challenge, finish off part of the [[Roadmap]]<br /> <br /> === How do I start writing applications? ===<br /> <br /> You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.<br /> <br /> Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.<br /> <br /> === Helping develop GNUstep === <br /> <br /> There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.<br /> <br /> Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].<br /> <br /> Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.<br /> <br /> Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.<br /> <br /> Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation. <br /> <br /> Specific tasks are noted in the developers section on the GNUstep website.<br /> <br /> === Helping document GNUstep ===<br /> <br /> All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.<br /> <br /> Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.<br /> <br /> More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!<br /> <br /> Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.<br /> <br /> GNUstep documentation should have copyright assigned to the Free Software Foundation.<br /> <br /> === How do I assign my contribution? ===<br /> <br /> Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).<br /> <br /> === How do I update the task list? ===<br /> <br /> The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).<br /> <br /> One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.<br /> <br /> Send any changes or additions to bug-gnustep@gnu.org.<br /> <br /> A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.<br /> <br /> If a class or method is<br /> <br /> * in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.<br /> * in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP<br /> * in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X<br /> <br /> There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.<br /> <br /> === How do I start writing tests? ===<br /> <br /> You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.<br /> <br /> To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.<br /> <br /> === How can I help with the GNUstep website? ===<br /> <br /> '''Please consider contributing to this Wiki as opposed to the website.'''<br /> Contact Adam Fedor fedor@gnu.org, the maintainer.<br /> <br /> The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.<br /> <br /> If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.<br /> <br /> If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.<br /> <br /> The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.<br /> <br /> === How can I take part with a GNUstep autobuilder for the testfarm? ===<br /> * General Procedure<br /> ** Make sure your build system have a gcc compiler with objc support.<br /> *** run &quot;gcc -v&quot; to see if obc is on the list of --enable-language option<br /> ** mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/startup.current.tar.bz2<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> ** tar xjf startup.current.tar.bz2<br /> ** tar xjf core.current.tar.bz2<br /> ** cd startup/scripts<br /> ** ./test-gnustep<br /> <br /> The results get posted to the gnustep-dev@gnu.org list and to http://ftp.gnustep.org/pub/testfarm/. <br /> The test script will automatically update using SVN if possible.<br /> ==== Fedora 6 ====<br /> ==== Solaris ====<br /> ==== Solaris 10 x86 ====<br /> * Solaris 10 x86 Procedure<br /> ** OS info<br /> *** Solaris 10 x86 Update 4, with everything installed.<br /> &lt;pre&gt;<br /> bash-3.00# cat /etc/release<br /> Solaris 10 8/07 s10x_u4wos_12b X86<br /> Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.<br /> Use is subject to license terms.<br /> Assembled 16 August 2007<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> ** Make sure you have a gcc compiler with objc support.<br /> *** gcc come with Solaris U4 doesn't have objective-C enabled.<br /> &lt;pre&gt;<br /> bash-3.00# /usr/sfw/bin/gcc -v<br /> Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs<br /> Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure <br /> --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as <br /> --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared<br /> Thread model: posix<br /> gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> <br /> ** TBA.<br /> <br /> == GNU Objective C Compiler and Runtime ==<br /> <br /> === What is the Objective C Runtime? ===<br /> <br /> The Objective C Runtime Library provides C functions and data structures required to execute an Objective C program.<br /> <br /> The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @&quot;&quot;-style string objects).<br /> <br /> It also has several differences over NeXT's implementation:<br /> <br /> * GNU's runtime provides &quot;selector-types&quot; along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).<br /> <br /> * Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.<br /> <br /> Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.<br /> <br /> <br /> === Where can I get a gcc compiler with Objective C support? ===<br /> *TBA.<br /> === How I can compile my own gcc compiler with objective-C support ? ===<br /> * TBA.<br /> === How I check if my gcc compiler has good objective C environment ? ===<br /> * TBA.<br /> <br /> == GNUstep Base Library ==<br /> <br /> === What is the GNUstep Base Library? ===<br /> <br /> The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops, and random number generators.<br /> <br /> It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).<br /> <br /> === What is its current state of development? ===<br /> <br /> GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.<br /> <br /> === What are the features of GNU Distributed Objects? ===<br /> <br /> GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.<br /> <br /> NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.<br /> Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU &quot;typed selector&quot; mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like. <br /> <br /> == GNUstep GUI Library ==<br /> <br /> === What is the GUI Library? ===<br /> <br /> The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many peripheral classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.<br /> <br /> It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.<br /> <br /> === Explain the organization of the front- and back-ends ===<br /> <br /> The GNUstep GUI Library is divided into a front- and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X Windows. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. Much work will be saved by this clean separation between front- and back-end, because it allows different platforms to share the large amount of front-end code.<br /> <br /> === What is the current state of development of the front-end? ===<br /> Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.<br /> <br /> === What is the current state of development of the back-ends? ===<br /> <br /> There are several backends currently available:<br /> <br /> * '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing. <br /> * '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality. It is currently the standard backend (as long as the required libraries are installed). <br /> * '''w32:''' This backend works on Windows and uses basic Windows drawing <br /> * '''cairo:''' An up-and-coming backend. It still relies on unpublished functions in the cairo library so using it is not for the beginner. <br /> <br /> == GNUstep DisplayGhostScript Server ==<br /> <br /> === What is the Display Ghostscript Server? ===<br /> <br /> It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.<br /> <br /> At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.<br /> <br /> === What is its current state of development? ===<br /> <br /> GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.<br /> <br /> === What is the relationship between the Display Ghostscript Server and X Windows? ===<br /> <br /> Display Ghostscript runs on top of X Windows.</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4940 2007-11-30T15:21:39Z

<p>Tjyang: /* Prepare your gnustep win32 development environment */</p> <hr /> <div>= GNUstep .exe installer using Nullsoft's [http://nsis.sourceforge.net/Main_Page NSIS] =<br /> Using the binary installer is the easiest way to get the GNUstep development libraries to your PC. Unfortunately the releases are very sporadic.<br /> <br /> == Install instructions ==<br /> * Download [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows gnustep installer] and run it.<br /> * select install binaries<br /> Now you have an MSYS environment (minimal GNU with shell and basic programs). You can start the shell via &quot;Start &amp;rarr; Programs &amp;rarr; GNUstep Development &amp;rarr; MSYS for GNUstep&quot; and begin programming.<br /> <br /> &lt;small&gt;To start you could download the gnustep examples package:<br /> svn co svn://svn.gna.org/svn/gnustep/modules/usr-apps/examples <br /> alternatively download the gnustep-example package from [ftp://ftp.gnustep.org/pub/gnustep/core/ here] and unpack with &lt;code&gt;tar zxf gnustep-examples-1.1.0.tar.gz&lt;/code&gt;. To compile/run an example type:<br /> cd examples/gui/GSTest<br /> make<br /> openapp ./GSTest.app<br /> &lt;/small&gt;<br /> Have much fun!<br /> <br /> = Install Windows GNUstep Manually =<br /> <br /> == Install MinGW ==<br /> Download [http://sourceforge.net/project/showfiles.php?group_id=2435&amp;package_id=82721 MinGW] (MinGW-5.1.3.exe or later) (cygwin works with a little tweaking; see talk page) from http://sourceforge.net/projects/mingw Install it into &lt;tt&gt;C:\''xxx''\msys\1.0\mingw&lt;/tt&gt;<br /> <br /> (where ''xxx'' is the top-level path you want to use, I use Nicola/GNUstep so I install it into &lt;tt&gt;C:\Nicola\GNUstep\msys\1.0\mingw&lt;/tt&gt;)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into &lt;tt&gt;C:\''xxx''\msys\1.0&lt;/tt&gt;<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into &lt;tt&gt;C:\''xxx''\msys\1.0&lt;/tt&gt;<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep ==<br /> === Via subversion ===<br /> If you have a copy of SVN (http://subversion.tigris.org/) installed on your system and want to have the most up-to-date version just being worked on, do the following.<br /> <br /> In windows, go to 'Start &amp;rarr; All Programs &amp;rarr; mingw &amp;rarr; MSYS &amp;rarr; Msys'.<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> svn co svn://svn.gna.org/svn/gnustep/modules/core<br /> <br /> This will download the core GNUstep libraries (make, base, gui and back).<br /> <br /> === Release tarball ===<br /> <br /> Otherwise download from the main site http://www.gnustep.org (or ftp://ftp.gnustep.org/pub/gnustep/core/) the file gnustep-startup-x.yy.z.tar.gz. It contains the core libraries. Put it somewhere in your MSYS home folder, i.e. under C:\xxx\msys\1.0\home\Nicola\install<br /> <br /> To unpack the file type the following into the MSYS window<br /> cd ~/install #or where you put it<br /> tar zxf gnustep-startup-0.16.1.tar.gz<br /> <br /> &lt;p style=&quot;color:red; background-color:yellow;&quot;&gt;After these steps you have the most recent installation instructions in the file 'core/make/Documentation/README.MinGW'&lt;/p&gt;<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --with-layout=fhs<br /> make<br /> make install<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> rm -Rf /mingw/lib/gcc/mingw32/3.4.2/include/objc<br /> rm -Rf /mingw/lib/libobjc.a<br /> rm -Rf /mingw/lib/libobjc.la<br /> <br /> Then get GNUstep's libobjc and install it.<br /> svn co svn://svn.gna.org/svn/gnustep/modules/dev-libs/libobjc<br /> cd libobjc <br /> make<br /> make install<br /> <br /> If you don't use SVN, download gnustep-libobjc from ftp://ftp.gnustep.org/pub/gnustep/libs/<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> Enter the core/make directory and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure --with-layout=fhs<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure<br /> <br /> A windows prompt may appear (several times) stating that conftest.exe has encountered a problem and needs to close. Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> ==== Precompiled library ====<br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> :libintl-0.11.5-2-bin.zip<br /> :libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> :libiconv-1.9.2-1-bin.zip <br /> :libiconv-1.9.2-1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> :zlib-1.2.2-bin.zip<br /> :zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into &lt;tt&gt;C:\''xxx''\msys\1.0\mingw&lt;/tt&gt;.<br /> <br /> == Install XML support ==<br /> Download the latest version of libxml from [ftp://xmlsoft.org/libxml2/].<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> &lt;p style=&quot;color:red; background-color:yellow;&quot;&gt;Do not install libxslt. It is broken on Windows.&lt;/p&gt;<br /> <br /> == Install GNUstep base ==<br /> <br /> Enter the gnustep-base directory, and type <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> :jpeg-6b-3-bin.zip<br /> :jpeg-6b-3-dep.zip<br /> :jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> :tiff-3.7.1-bin.zip<br /> :tiff-3.7.1-dep.zip<br /> :tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> :libpng-1.2.8-bin.zip<br /> :libpng-1.2.8-dep.zip<br /> :libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into &lt;tt&gt;C:''xxx''\msys\1.0\mingw&lt;/tt&gt;.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> cd to core/back and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> Some older makefiles may require that you type<br /> export GNUSTEP_MAKEFILES=/usr/local/share/GNUstep/Makefiles<br /> before compiling.<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =<br /> <br /> There are three sub packages <br /> * user : To minimize the footprint of gnustep system on Windows machines.<br /> * developer : include WiX,gcc and package sources.<br /> * gnustep applications : include a broad suite of GNUstep applications.<br /> == Install GNUstep MSI installer ==<br /> * Download the msi from here.<br /> * answer following questions.<br /> * Test the installation.<br /> == Prepare your Win32 gnustep WiX packaging environment ==<br /> === List of depended software ===<br /> * WiX Win32 MSI package creation tool.<br /> ** candle.exe <br /> &lt;pre&gt;<br /> C:\tmp&gt;candle<br /> Microsoft (R) Windows Installer Xml Compiler version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: candle.exe [-?] [-nologo] [-out outputFile] sourceFile [sourceFile ...]<br /> <br /> <br /> -d&lt;name&gt;=&lt;value&gt; define a parameter for the preprocessor<br /> -p&lt;file&gt; preprocess to a file (or stdout if no file supplied)<br /> -I&lt;dir&gt; add to include search path<br /> -nologo skip printing candle logo information<br /> -out specify output file (default: write to current directory)<br /> -pedantic:&lt;level&gt; pedantic checks (levels: easy, heroic, legendary)<br /> <br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> <br /> ** light.exe<br /> &lt;pre&gt;<br /> C:\tmp&gt;light<br /> Microsoft (R) Windows Installer Xml Linker version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: light.exe [-?] [-b basePath] [-nologo] [-out outputFile] objectFile [o<br /> jectFile ...]<br /> <br /> -ai allow identical rows, identical rows will be treated as a warning<br /> -au (experimental) allow unresolved references, will not create a val<br /> d output<br /> -b base path to locate all files (default: current directory)<br /> -cc path to cache built cabinets (will not be deleted after linking)<br /> <br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> * makefile for nmake.<br /> * gcc win32 compiler from MingW.<br /> <br /> === Checkout gnustep.wxs ===<br /> === overview of gnustep.wxs ===</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Developer_FAQ&diff=4895 2007-11-07T14:56:32Z

<p>Tjyang: /* How I check if my gcc compiler has good objective C environment ? */</p> <hr /> <div>[[Category:FAQ]]<br /> <br /> Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.<br /> <br /> == Compatibility ==<br /> <br /> === Is it easy to port OPENSTEP programs to GNUstep? ===<br /> <br /> It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === How about porting between Cocoa and GNUstep? ===<br /> <br /> It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === Tools for porting ===<br /> <br /> While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.<br /> <br /> * '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).<br /> * '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.<br /> * '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.<br /> * '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.<br /> * '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.<br /> <br /> === Can I transfer archived data from GNUstep to Cocoa? ===<br /> <br /> Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.<br /> <br /> The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.<br /> <br /> === Does distributed objects work between GNUstep and Cocoa? ===<br /> <br /> See the answer to the previous question (on archive compatibility) for why this won't work either.<br /> <br /> === Is there an Interface Builder for GNUstep? ===<br /> <br /> There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].<br /> <br /> === Can I use my original NIB files? ===<br /> It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later. <br /> <br /> Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.<br /> <br /> === Can one use the hybrid &quot;Objective-C++&quot; ? ===<br /> <br /> Yes. As of release 4.1 the GNU C Compiler (GCC) supports &quot;Objective-C++&quot;.<br /> <br /> === Is there a plan to support the Java/YellowBox Bindings? ===<br /> <br /> Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects. <br /> <br /> === What if I compile GNUstep under OPENSTEP/MacOS X? ===<br /> <br /> GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.<br /> <br /> You can, however, use a GNUstep program with an X11 server running on MacOSX.<br /> <br /> === Is the Objective C API for GTK related? ===<br /> <br /> No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.<br /> <br /> The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks. <br /> <br /> === How about implementing parts of the Application Kit with GTK? ===<br /> <br /> Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.<br /> <br /> That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome. <br /> <br /> == Compiling and Developing ==<br /> <br /> === How can I get started programming? ===<br /> Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)<br /> <br /> === Why doesn't GDB support Objective-C? ===<br /> As of GDB 6.0, gdb supports debugging of Objective-C code.<br /> <br /> == How can I help with GNUstep? ==<br /> <br /> The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.<br /> <br /> Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep. <br /> <br /> Here are the next steps: <br /> * Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]<br /> * Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.<br /> * For a bigger challenge, finish off part of the [[Roadmap]]<br /> <br /> === How do I start writing applications? ===<br /> <br /> You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.<br /> <br /> Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.<br /> <br /> === Helping develop GNUstep === <br /> <br /> There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.<br /> <br /> Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].<br /> <br /> Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.<br /> <br /> Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.<br /> <br /> Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation. <br /> <br /> Specific tasks are noted in the developers section on the GNUstep website.<br /> <br /> === Helping document GNUstep ===<br /> <br /> All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.<br /> <br /> Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.<br /> <br /> More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!<br /> <br /> Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.<br /> <br /> GNUstep documentation should have copyright assigned to the Free Software Foundation.<br /> <br /> === How do I assign my contribution? ===<br /> <br /> Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).<br /> <br /> === How do I update the task list? ===<br /> <br /> The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).<br /> <br /> One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.<br /> <br /> Send any changes or additions to bug-gnustep@gnu.org.<br /> <br /> A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.<br /> <br /> If a class or method is<br /> <br /> * in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.<br /> * in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP<br /> * in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X<br /> <br /> There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.<br /> <br /> === How do I start writing tests? ===<br /> <br /> You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.<br /> <br /> To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.<br /> <br /> === How can I help with the GNUstep website? ===<br /> <br /> '''Please consider contributing to this Wiki as opposed to the website.'''<br /> Contact Adam Fedor fedor@gnu.org, the maintainer.<br /> <br /> The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.<br /> <br /> If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.<br /> <br /> If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.<br /> <br /> The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.<br /> <br /> === How can I take part with a GNUstep autobuilder for the testfarm? ===<br /> * General Procedure<br /> ** Make sure your build system have a gcc compiler with objc support.<br /> *** run &quot;gcc -v&quot; to see if obc is on the list of --enable-language option<br /> ** mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/Startup.current.tar.bz2<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> ** tar xjf Startup.current.tar.bz2<br /> ** tar xjf core.current.tar.bz2<br /> ** cd Startup/scripts<br /> ** ./test-gnustep<br /> <br /> The results get posted to the gnustep-dev@gnu.org list and to http://ftp.gnustep.org/pub/testfarm/. The test script will automatically update using SVN if possible.<br /> <br /> * Solaris 10 x86 Procedure<br /> ** OS info<br /> *** Solaris 10 x86 Update 4, with everything installed.<br /> &lt;pre&gt;<br /> bash-3.00# cat /etc/release<br /> Solaris 10 8/07 s10x_u4wos_12b X86<br /> Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.<br /> Use is subject to license terms.<br /> Assembled 16 August 2007<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> ** Make sure you have a gcc compiler with objc support.<br /> *** gcc come with Solaris U4 doesn't have objective-C enabled.<br /> &lt;pre&gt;<br /> bash-3.00# /usr/sfw/bin/gcc -v<br /> Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs<br /> Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure <br /> --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as <br /> --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared<br /> Thread model: posix<br /> gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> <br /> ** TBA.<br /> <br /> == GNU Objective C Compiler and Runtime ==<br /> <br /> === What is the Objective C Runtime? ===<br /> <br /> The Objective C Runtime Library provides C functions and data structures required to execute an Objective C program.<br /> <br /> The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @&quot;&quot;-style string objects).<br /> <br /> It also has several differences over NeXT's implementation:<br /> <br /> * GNU's runtime provides &quot;selector-types&quot; along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).<br /> <br /> * Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.<br /> <br /> Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.<br /> <br /> <br /> === Where can I get a gcc compiler with Objective C support? ===<br /> *TBA.<br /> === How I can compile my own gcc compiler with objective-C support ? ===<br /> * TBA.<br /> === How I check if my gcc compiler has good objective C environment ? ===<br /> * TBA.<br /> <br /> == GNUstep Base Library ==<br /> <br /> === What is the GNUstep Base Library? ===<br /> <br /> The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops, and random number generators.<br /> <br /> It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).<br /> <br /> === What is its current state of development? ===<br /> <br /> GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.<br /> <br /> === What are the features of GNU Distributed Objects? ===<br /> <br /> GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.<br /> <br /> NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.<br /> Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU &quot;typed selector&quot; mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like. <br /> <br /> == GNUstep GUI Library ==<br /> <br /> === What is the GUI Library? ===<br /> <br /> The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many peripheral classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.<br /> <br /> It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.<br /> <br /> === Explain the organization of the front- and back-ends ===<br /> <br /> The GNUstep GUI Library is divided into a front- and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X Windows. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. Much work will be saved by this clean separation between front- and back-end, because it allows different platforms to share the large amount of front-end code.<br /> <br /> === What is the current state of development of the front-end? ===<br /> Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.<br /> <br /> === What is the current state of development of the back-ends? ===<br /> <br /> There are several backends currently available:<br /> <br /> * '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing. <br /> * '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality. It is currently the standard backend (as long as the required libraries are installed). <br /> * '''w32:''' This backend works on Windows and uses basic Windows drawing <br /> * '''cairo:''' An up-and-coming backend. It still relies on unpublished functions in the cairo library so using it is not for the beginner. <br /> <br /> == GNUstep DisplayGhostScript Server ==<br /> <br /> === What is the Display Ghostscript Server? ===<br /> <br /> It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.<br /> <br /> At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.<br /> <br /> === What is its current state of development? ===<br /> <br /> GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.<br /> <br /> === What is the relationship between the Display Ghostscript Server and X Windows? ===<br /> <br /> Display Ghostscript runs on top of X Windows.</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Developer_FAQ&diff=4894 2007-11-07T14:54:14Z

<p>Tjyang: /* GNU Objective C Compiler and Runtime */</p> <hr /> <div>[[Category:FAQ]]<br /> <br /> Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.<br /> <br /> == Compatibility ==<br /> <br /> === Is it easy to port OPENSTEP programs to GNUstep? ===<br /> <br /> It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === How about porting between Cocoa and GNUstep? ===<br /> <br /> It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === Tools for porting ===<br /> <br /> While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.<br /> <br /> * '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).<br /> * '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.<br /> * '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.<br /> * '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.<br /> * '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.<br /> <br /> === Can I transfer archived data from GNUstep to Cocoa? ===<br /> <br /> Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.<br /> <br /> The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.<br /> <br /> === Does distributed objects work between GNUstep and Cocoa? ===<br /> <br /> See the answer to the previous question (on archive compatibility) for why this won't work either.<br /> <br /> === Is there an Interface Builder for GNUstep? ===<br /> <br /> There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].<br /> <br /> === Can I use my original NIB files? ===<br /> It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later. <br /> <br /> Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.<br /> <br /> === Can one use the hybrid &quot;Objective-C++&quot; ? ===<br /> <br /> Yes. As of release 4.1 the GNU C Compiler (GCC) supports &quot;Objective-C++&quot;.<br /> <br /> === Is there a plan to support the Java/YellowBox Bindings? ===<br /> <br /> Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects. <br /> <br /> === What if I compile GNUstep under OPENSTEP/MacOS X? ===<br /> <br /> GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.<br /> <br /> You can, however, use a GNUstep program with an X11 server running on MacOSX.<br /> <br /> === Is the Objective C API for GTK related? ===<br /> <br /> No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.<br /> <br /> The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks. <br /> <br /> === How about implementing parts of the Application Kit with GTK? ===<br /> <br /> Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.<br /> <br /> That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome. <br /> <br /> == Compiling and Developing ==<br /> <br /> === How can I get started programming? ===<br /> Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)<br /> <br /> === Why doesn't GDB support Objective-C? ===<br /> As of GDB 6.0, gdb supports debugging of Objective-C code.<br /> <br /> == How can I help with GNUstep? ==<br /> <br /> The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.<br /> <br /> Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep. <br /> <br /> Here are the next steps: <br /> * Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]<br /> * Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.<br /> * For a bigger challenge, finish off part of the [[Roadmap]]<br /> <br /> === How do I start writing applications? ===<br /> <br /> You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.<br /> <br /> Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.<br /> <br /> === Helping develop GNUstep === <br /> <br /> There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.<br /> <br /> Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].<br /> <br /> Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.<br /> <br /> Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.<br /> <br /> Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation. <br /> <br /> Specific tasks are noted in the developers section on the GNUstep website.<br /> <br /> === Helping document GNUstep ===<br /> <br /> All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.<br /> <br /> Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.<br /> <br /> More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!<br /> <br /> Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.<br /> <br /> GNUstep documentation should have copyright assigned to the Free Software Foundation.<br /> <br /> === How do I assign my contribution? ===<br /> <br /> Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).<br /> <br /> === How do I update the task list? ===<br /> <br /> The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).<br /> <br /> One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.<br /> <br /> Send any changes or additions to bug-gnustep@gnu.org.<br /> <br /> A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.<br /> <br /> If a class or method is<br /> <br /> * in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.<br /> * in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP<br /> * in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X<br /> <br /> There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.<br /> <br /> === How do I start writing tests? ===<br /> <br /> You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.<br /> <br /> To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.<br /> <br /> === How can I help with the GNUstep website? ===<br /> <br /> '''Please consider contributing to this Wiki as opposed to the website.'''<br /> Contact Adam Fedor fedor@gnu.org, the maintainer.<br /> <br /> The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.<br /> <br /> If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.<br /> <br /> If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.<br /> <br /> The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.<br /> <br /> === How can I take part with a GNUstep autobuilder for the testfarm? ===<br /> * General Procedure<br /> ** Make sure your build system have a gcc compiler with objc support.<br /> *** run &quot;gcc -v&quot; to see if obc is on the list of --enable-language option<br /> ** mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/Startup.current.tar.bz2<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> ** tar xjf Startup.current.tar.bz2<br /> ** tar xjf core.current.tar.bz2<br /> ** cd Startup/scripts<br /> ** ./test-gnustep<br /> <br /> The results get posted to the gnustep-dev@gnu.org list and to http://ftp.gnustep.org/pub/testfarm/. The test script will automatically update using SVN if possible.<br /> <br /> * Solaris 10 x86 Procedure<br /> ** OS info<br /> *** Solaris 10 x86 Update 4, with everything installed.<br /> &lt;pre&gt;<br /> bash-3.00# cat /etc/release<br /> Solaris 10 8/07 s10x_u4wos_12b X86<br /> Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.<br /> Use is subject to license terms.<br /> Assembled 16 August 2007<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> ** Make sure you have a gcc compiler with objc support.<br /> *** gcc come with Solaris U4 doesn't have objective-C enabled.<br /> &lt;pre&gt;<br /> bash-3.00# /usr/sfw/bin/gcc -v<br /> Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs<br /> Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure <br /> --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as <br /> --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared<br /> Thread model: posix<br /> gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> <br /> ** TBA.<br /> <br /> == GNU Objective C Compiler and Runtime ==<br /> <br /> === What is the Objective C Runtime? ===<br /> <br /> The Objective C Runtime Library provides C functions and data structures required to execute an Objective C program.<br /> <br /> The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @&quot;&quot;-style string objects).<br /> <br /> It also has several differences over NeXT's implementation:<br /> <br /> * GNU's runtime provides &quot;selector-types&quot; along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).<br /> <br /> * Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.<br /> <br /> Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.<br /> <br /> <br /> === Where can I get a gcc compiler with Objective C support? ===<br /> *TBA.<br /> === How I check if my gcc compiler has good objective C environment ? ===<br /> *TBD.<br /> <br /> == GNUstep Base Library ==<br /> <br /> === What is the GNUstep Base Library? ===<br /> <br /> The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops, and random number generators.<br /> <br /> It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).<br /> <br /> === What is its current state of development? ===<br /> <br /> GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.<br /> <br /> === What are the features of GNU Distributed Objects? ===<br /> <br /> GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.<br /> <br /> NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.<br /> Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU &quot;typed selector&quot; mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like. <br /> <br /> == GNUstep GUI Library ==<br /> <br /> === What is the GUI Library? ===<br /> <br /> The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many peripheral classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.<br /> <br /> It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.<br /> <br /> === Explain the organization of the front- and back-ends ===<br /> <br /> The GNUstep GUI Library is divided into a front- and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X Windows. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. Much work will be saved by this clean separation between front- and back-end, because it allows different platforms to share the large amount of front-end code.<br /> <br /> === What is the current state of development of the front-end? ===<br /> Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.<br /> <br /> === What is the current state of development of the back-ends? ===<br /> <br /> There are several backends currently available:<br /> <br /> * '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing. <br /> * '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality. It is currently the standard backend (as long as the required libraries are installed). <br /> * '''w32:''' This backend works on Windows and uses basic Windows drawing <br /> * '''cairo:''' An up-and-coming backend. It still relies on unpublished functions in the cairo library so using it is not for the beginner. <br /> <br /> == GNUstep DisplayGhostScript Server ==<br /> <br /> === What is the Display Ghostscript Server? ===<br /> <br /> It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.<br /> <br /> At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.<br /> <br /> === What is its current state of development? ===<br /> <br /> GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.<br /> <br /> === What is the relationship between the Display Ghostscript Server and X Windows? ===<br /> <br /> Display Ghostscript runs on top of X Windows.</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Developer_FAQ&diff=4893 2007-11-07T14:33:00Z

<p>Tjyang: /* How can I take part with a GNUstep autobuilder for the testfarm? */</p> <hr /> <div>[[Category:FAQ]]<br /> <br /> Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.<br /> <br /> == Compatibility ==<br /> <br /> === Is it easy to port OPENSTEP programs to GNUstep? ===<br /> <br /> It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === How about porting between Cocoa and GNUstep? ===<br /> <br /> It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === Tools for porting ===<br /> <br /> While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.<br /> <br /> * '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).<br /> * '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.<br /> * '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.<br /> * '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.<br /> * '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.<br /> <br /> === Can I transfer archived data from GNUstep to Cocoa? ===<br /> <br /> Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.<br /> <br /> The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.<br /> <br /> === Does distributed objects work between GNUstep and Cocoa? ===<br /> <br /> See the answer to the previous question (on archive compatibility) for why this won't work either.<br /> <br /> === Is there an Interface Builder for GNUstep? ===<br /> <br /> There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].<br /> <br /> === Can I use my original NIB files? ===<br /> It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later. <br /> <br /> Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.<br /> <br /> === Can one use the hybrid &quot;Objective-C++&quot; ? ===<br /> <br /> Yes. As of release 4.1 the GNU C Compiler (GCC) supports &quot;Objective-C++&quot;.<br /> <br /> === Is there a plan to support the Java/YellowBox Bindings? ===<br /> <br /> Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects. <br /> <br /> === What if I compile GNUstep under OPENSTEP/MacOS X? ===<br /> <br /> GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.<br /> <br /> You can, however, use a GNUstep program with an X11 server running on MacOSX.<br /> <br /> === Is the Objective C API for GTK related? ===<br /> <br /> No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.<br /> <br /> The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks. <br /> <br /> === How about implementing parts of the Application Kit with GTK? ===<br /> <br /> Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.<br /> <br /> That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome. <br /> <br /> == Compiling and Developing ==<br /> <br /> === How can I get started programming? ===<br /> Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)<br /> <br /> === Why doesn't GDB support Objective-C? ===<br /> As of GDB 6.0, gdb supports debugging of Objective-C code.<br /> <br /> == How can I help with GNUstep? ==<br /> <br /> The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.<br /> <br /> Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep. <br /> <br /> Here are the next steps: <br /> * Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]<br /> * Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.<br /> * For a bigger challenge, finish off part of the [[Roadmap]]<br /> <br /> === How do I start writing applications? ===<br /> <br /> You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.<br /> <br /> Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.<br /> <br /> === Helping develop GNUstep === <br /> <br /> There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.<br /> <br /> Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].<br /> <br /> Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.<br /> <br /> Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.<br /> <br /> Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation. <br /> <br /> Specific tasks are noted in the developers section on the GNUstep website.<br /> <br /> === Helping document GNUstep ===<br /> <br /> All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.<br /> <br /> Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.<br /> <br /> More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!<br /> <br /> Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.<br /> <br /> GNUstep documentation should have copyright assigned to the Free Software Foundation.<br /> <br /> === How do I assign my contribution? ===<br /> <br /> Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).<br /> <br /> === How do I update the task list? ===<br /> <br /> The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).<br /> <br /> One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.<br /> <br /> Send any changes or additions to bug-gnustep@gnu.org.<br /> <br /> A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.<br /> <br /> If a class or method is<br /> <br /> * in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.<br /> * in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP<br /> * in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X<br /> <br /> There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.<br /> <br /> === How do I start writing tests? ===<br /> <br /> You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.<br /> <br /> To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.<br /> <br /> === How can I help with the GNUstep website? ===<br /> <br /> '''Please consider contributing to this Wiki as opposed to the website.'''<br /> Contact Adam Fedor fedor@gnu.org, the maintainer.<br /> <br /> The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.<br /> <br /> If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.<br /> <br /> If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.<br /> <br /> The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.<br /> <br /> === How can I take part with a GNUstep autobuilder for the testfarm? ===<br /> * General Procedure<br /> ** Make sure your build system have a gcc compiler with objc support.<br /> *** run &quot;gcc -v&quot; to see if obc is on the list of --enable-language option<br /> ** mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/Startup.current.tar.bz2<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> ** tar xjf Startup.current.tar.bz2<br /> ** tar xjf core.current.tar.bz2<br /> ** cd Startup/scripts<br /> ** ./test-gnustep<br /> <br /> The results get posted to the gnustep-dev@gnu.org list and to http://ftp.gnustep.org/pub/testfarm/. The test script will automatically update using SVN if possible.<br /> <br /> * Solaris 10 x86 Procedure<br /> ** OS info<br /> *** Solaris 10 x86 Update 4, with everything installed.<br /> &lt;pre&gt;<br /> bash-3.00# cat /etc/release<br /> Solaris 10 8/07 s10x_u4wos_12b X86<br /> Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.<br /> Use is subject to license terms.<br /> Assembled 16 August 2007<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> ** Make sure you have a gcc compiler with objc support.<br /> *** gcc come with Solaris U4 doesn't have objective-C enabled.<br /> &lt;pre&gt;<br /> bash-3.00# /usr/sfw/bin/gcc -v<br /> Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs<br /> Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure <br /> --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as <br /> --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared<br /> Thread model: posix<br /> gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> <br /> ** TBA.<br /> <br /> == GNU Objective C Compiler and Runtime ==<br /> <br /> === What is the Objective C Runtime? ===<br /> <br /> The Objective C Runtime Library provides C functions and data structures required to execute an Objective C program.<br /> <br /> The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @&quot;&quot;-style string objects).<br /> <br /> It also has several differences over NeXT's implementation:<br /> <br /> * GNU's runtime provides &quot;selector-types&quot; along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).<br /> <br /> * Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.<br /> <br /> Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.<br /> <br /> == GNUstep Base Library ==<br /> <br /> === What is the GNUstep Base Library? ===<br /> <br /> The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops, and random number generators.<br /> <br /> It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).<br /> <br /> === What is its current state of development? ===<br /> <br /> GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.<br /> <br /> === What are the features of GNU Distributed Objects? ===<br /> <br /> GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.<br /> <br /> NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.<br /> Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU &quot;typed selector&quot; mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like. <br /> <br /> == GNUstep GUI Library ==<br /> <br /> === What is the GUI Library? ===<br /> <br /> The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many peripheral classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.<br /> <br /> It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.<br /> <br /> === Explain the organization of the front- and back-ends ===<br /> <br /> The GNUstep GUI Library is divided into a front- and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X Windows. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. Much work will be saved by this clean separation between front- and back-end, because it allows different platforms to share the large amount of front-end code.<br /> <br /> === What is the current state of development of the front-end? ===<br /> Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.<br /> <br /> === What is the current state of development of the back-ends? ===<br /> <br /> There are several backends currently available:<br /> <br /> * '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing. <br /> * '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality. It is currently the standard backend (as long as the required libraries are installed). <br /> * '''w32:''' This backend works on Windows and uses basic Windows drawing <br /> * '''cairo:''' An up-and-coming backend. It still relies on unpublished functions in the cairo library so using it is not for the beginner. <br /> <br /> == GNUstep DisplayGhostScript Server ==<br /> <br /> === What is the Display Ghostscript Server? ===<br /> <br /> It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.<br /> <br /> At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.<br /> <br /> === What is its current state of development? ===<br /> <br /> GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.<br /> <br /> === What is the relationship between the Display Ghostscript Server and X Windows? ===<br /> <br /> Display Ghostscript runs on top of X Windows.</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Developer_FAQ&diff=4892 2007-11-07T14:29:42Z

<p>Tjyang: /* How can I take part with a GNUstep autobuilder for the testfarm? */</p> <hr /> <div>[[Category:FAQ]]<br /> <br /> Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.<br /> <br /> == Compatibility ==<br /> <br /> === Is it easy to port OPENSTEP programs to GNUstep? ===<br /> <br /> It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === How about porting between Cocoa and GNUstep? ===<br /> <br /> It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === Tools for porting ===<br /> <br /> While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.<br /> <br /> * '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).<br /> * '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.<br /> * '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.<br /> * '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.<br /> * '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.<br /> <br /> === Can I transfer archived data from GNUstep to Cocoa? ===<br /> <br /> Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.<br /> <br /> The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.<br /> <br /> === Does distributed objects work between GNUstep and Cocoa? ===<br /> <br /> See the answer to the previous question (on archive compatibility) for why this won't work either.<br /> <br /> === Is there an Interface Builder for GNUstep? ===<br /> <br /> There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].<br /> <br /> === Can I use my original NIB files? ===<br /> It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later. <br /> <br /> Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.<br /> <br /> === Can one use the hybrid &quot;Objective-C++&quot; ? ===<br /> <br /> Yes. As of release 4.1 the GNU C Compiler (GCC) supports &quot;Objective-C++&quot;.<br /> <br /> === Is there a plan to support the Java/YellowBox Bindings? ===<br /> <br /> Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects. <br /> <br /> === What if I compile GNUstep under OPENSTEP/MacOS X? ===<br /> <br /> GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.<br /> <br /> You can, however, use a GNUstep program with an X11 server running on MacOSX.<br /> <br /> === Is the Objective C API for GTK related? ===<br /> <br /> No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.<br /> <br /> The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks. <br /> <br /> === How about implementing parts of the Application Kit with GTK? ===<br /> <br /> Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.<br /> <br /> That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome. <br /> <br /> == Compiling and Developing ==<br /> <br /> === How can I get started programming? ===<br /> Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)<br /> <br /> === Why doesn't GDB support Objective-C? ===<br /> As of GDB 6.0, gdb supports debugging of Objective-C code.<br /> <br /> == How can I help with GNUstep? ==<br /> <br /> The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.<br /> <br /> Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep. <br /> <br /> Here are the next steps: <br /> * Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]<br /> * Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.<br /> * For a bigger challenge, finish off part of the [[Roadmap]]<br /> <br /> === How do I start writing applications? ===<br /> <br /> You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.<br /> <br /> Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.<br /> <br /> === Helping develop GNUstep === <br /> <br /> There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.<br /> <br /> Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].<br /> <br /> Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.<br /> <br /> Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.<br /> <br /> Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation. <br /> <br /> Specific tasks are noted in the developers section on the GNUstep website.<br /> <br /> === Helping document GNUstep ===<br /> <br /> All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.<br /> <br /> Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.<br /> <br /> More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!<br /> <br /> Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.<br /> <br /> GNUstep documentation should have copyright assigned to the Free Software Foundation.<br /> <br /> === How do I assign my contribution? ===<br /> <br /> Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).<br /> <br /> === How do I update the task list? ===<br /> <br /> The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).<br /> <br /> One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.<br /> <br /> Send any changes or additions to bug-gnustep@gnu.org.<br /> <br /> A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.<br /> <br /> If a class or method is<br /> <br /> * in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.<br /> * in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP<br /> * in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X<br /> <br /> There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.<br /> <br /> === How do I start writing tests? ===<br /> <br /> You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.<br /> <br /> To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.<br /> <br /> === How can I help with the GNUstep website? ===<br /> <br /> '''Please consider contributing to this Wiki as opposed to the website.'''<br /> Contact Adam Fedor fedor@gnu.org, the maintainer.<br /> <br /> The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.<br /> <br /> If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.<br /> <br /> If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.<br /> <br /> The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.<br /> <br /> === How can I take part with a GNUstep autobuilder for the testfarm? ===<br /> * General Procedure<br /> ** Make sure your build system have a gcc compiler with objc support.<br /> ** mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/Startup.current.tar.bz2<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> ** tar xjf Startup.current.tar.bz2<br /> ** tar xjf core.current.tar.bz2<br /> ** cd Startup/scripts<br /> ** ./test-gnustep<br /> <br /> The results get posted to the gnustep-dev@gnu.org list and to http://ftp.gnustep.org/pub/testfarm/. The test script will automatically update using SVN if possible.<br /> <br /> * Solaris 10 x86 Procedure<br /> ** OS info<br /> *** Solaris 10 x86 Update 4, with everything installed.<br /> &lt;pre&gt;<br /> bash-3.00# cat /etc/release<br /> Solaris 10 8/07 s10x_u4wos_12b X86<br /> Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.<br /> Use is subject to license terms.<br /> Assembled 16 August 2007<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> ** Make sure you have a gcc compiler with objc support.<br /> *** gcc come with Solaris U4 doesn't have objective-C enabled.<br /> &lt;pre&gt;<br /> bash-3.00# /usr/sfw/bin/gcc -v<br /> Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs<br /> Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure <br /> --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as <br /> --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared<br /> Thread model: posix<br /> gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> <br /> ** TBA.<br /> <br /> == GNU Objective C Compiler and Runtime ==<br /> <br /> === What is the Objective C Runtime? ===<br /> <br /> The Objective C Runtime Library provides C functions and data structures required to execute an Objective C program.<br /> <br /> The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @&quot;&quot;-style string objects).<br /> <br /> It also has several differences over NeXT's implementation:<br /> <br /> * GNU's runtime provides &quot;selector-types&quot; along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).<br /> <br /> * Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.<br /> <br /> Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.<br /> <br /> == GNUstep Base Library ==<br /> <br /> === What is the GNUstep Base Library? ===<br /> <br /> The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops, and random number generators.<br /> <br /> It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).<br /> <br /> === What is its current state of development? ===<br /> <br /> GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.<br /> <br /> === What are the features of GNU Distributed Objects? ===<br /> <br /> GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.<br /> <br /> NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.<br /> Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU &quot;typed selector&quot; mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like. <br /> <br /> == GNUstep GUI Library ==<br /> <br /> === What is the GUI Library? ===<br /> <br /> The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many peripheral classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.<br /> <br /> It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.<br /> <br /> === Explain the organization of the front- and back-ends ===<br /> <br /> The GNUstep GUI Library is divided into a front- and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X Windows. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. Much work will be saved by this clean separation between front- and back-end, because it allows different platforms to share the large amount of front-end code.<br /> <br /> === What is the current state of development of the front-end? ===<br /> Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.<br /> <br /> === What is the current state of development of the back-ends? ===<br /> <br /> There are several backends currently available:<br /> <br /> * '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing. <br /> * '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality. It is currently the standard backend (as long as the required libraries are installed). <br /> * '''w32:''' This backend works on Windows and uses basic Windows drawing <br /> * '''cairo:''' An up-and-coming backend. It still relies on unpublished functions in the cairo library so using it is not for the beginner. <br /> <br /> == GNUstep DisplayGhostScript Server ==<br /> <br /> === What is the Display Ghostscript Server? ===<br /> <br /> It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.<br /> <br /> At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.<br /> <br /> === What is its current state of development? ===<br /> <br /> GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.<br /> <br /> === What is the relationship between the Display Ghostscript Server and X Windows? ===<br /> <br /> Display Ghostscript runs on top of X Windows.</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Developer_FAQ&diff=4891 2007-11-07T14:27:05Z

<p>Tjyang: /* How can I take part with a GNUstep autobuilder for the testfarm? */</p> <hr /> <div>[[Category:FAQ]]<br /> <br /> Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.<br /> <br /> == Compatibility ==<br /> <br /> === Is it easy to port OPENSTEP programs to GNUstep? ===<br /> <br /> It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === How about porting between Cocoa and GNUstep? ===<br /> <br /> It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === Tools for porting ===<br /> <br /> While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.<br /> <br /> * '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).<br /> * '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.<br /> * '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.<br /> * '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.<br /> * '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.<br /> <br /> === Can I transfer archived data from GNUstep to Cocoa? ===<br /> <br /> Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.<br /> <br /> The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.<br /> <br /> === Does distributed objects work between GNUstep and Cocoa? ===<br /> <br /> See the answer to the previous question (on archive compatibility) for why this won't work either.<br /> <br /> === Is there an Interface Builder for GNUstep? ===<br /> <br /> There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].<br /> <br /> === Can I use my original NIB files? ===<br /> It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later. <br /> <br /> Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.<br /> <br /> === Can one use the hybrid &quot;Objective-C++&quot; ? ===<br /> <br /> Yes. As of release 4.1 the GNU C Compiler (GCC) supports &quot;Objective-C++&quot;.<br /> <br /> === Is there a plan to support the Java/YellowBox Bindings? ===<br /> <br /> Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects. <br /> <br /> === What if I compile GNUstep under OPENSTEP/MacOS X? ===<br /> <br /> GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.<br /> <br /> You can, however, use a GNUstep program with an X11 server running on MacOSX.<br /> <br /> === Is the Objective C API for GTK related? ===<br /> <br /> No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.<br /> <br /> The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks. <br /> <br /> === How about implementing parts of the Application Kit with GTK? ===<br /> <br /> Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.<br /> <br /> That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome. <br /> <br /> == Compiling and Developing ==<br /> <br /> === How can I get started programming? ===<br /> Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)<br /> <br /> === Why doesn't GDB support Objective-C? ===<br /> As of GDB 6.0, gdb supports debugging of Objective-C code.<br /> <br /> == How can I help with GNUstep? ==<br /> <br /> The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.<br /> <br /> Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep. <br /> <br /> Here are the next steps: <br /> * Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]<br /> * Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.<br /> * For a bigger challenge, finish off part of the [[Roadmap]]<br /> <br /> === How do I start writing applications? ===<br /> <br /> You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.<br /> <br /> Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.<br /> <br /> === Helping develop GNUstep === <br /> <br /> There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.<br /> <br /> Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].<br /> <br /> Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.<br /> <br /> Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.<br /> <br /> Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation. <br /> <br /> Specific tasks are noted in the developers section on the GNUstep website.<br /> <br /> === Helping document GNUstep ===<br /> <br /> All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.<br /> <br /> Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.<br /> <br /> More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!<br /> <br /> Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.<br /> <br /> GNUstep documentation should have copyright assigned to the Free Software Foundation.<br /> <br /> === How do I assign my contribution? ===<br /> <br /> Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).<br /> <br /> === How do I update the task list? ===<br /> <br /> The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).<br /> <br /> One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.<br /> <br /> Send any changes or additions to bug-gnustep@gnu.org.<br /> <br /> A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.<br /> <br /> If a class or method is<br /> <br /> * in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.<br /> * in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP<br /> * in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X<br /> <br /> There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.<br /> <br /> === How do I start writing tests? ===<br /> <br /> You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.<br /> <br /> To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.<br /> <br /> === How can I help with the GNUstep website? ===<br /> <br /> '''Please consider contributing to this Wiki as opposed to the website.'''<br /> Contact Adam Fedor fedor@gnu.org, the maintainer.<br /> <br /> The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.<br /> <br /> If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.<br /> <br /> If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.<br /> <br /> The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.<br /> <br /> === How can I take part with a GNUstep autobuilder for the testfarm? ===<br /> * General Procedure<br /> ** Make sure your build system have a gcc compiler with objc support.<br /> ** mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/Startup.current.tar.bz2<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> ** tar xjf Startup.current.tar.bz2<br /> ** tar xjf core.current.tar.bz2<br /> ** cd Startup/scripts<br /> ** ./test-gnustep<br /> <br /> The results get posted to the gnustep-dev@gnu.org list and to http://ftp.gnustep.org/pub/testfarm/. The test script will automatically update using SVN if possible.<br /> <br /> * Solaris 10 x86 Procedure<br /> ** OS info<br /> *** Solaris 10 x86 Update 4, with everything installed.<br /> &lt;pre&gt;<br /> bash-3.00# cat /etc/release<br /> Solaris 10 8/07 s10x_u4wos_12b X86<br /> Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.<br /> Use is subject to license terms.<br /> Assembled 16 August 2007<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> ** Make sure you have a gcc compiler with objc support.<br /> *** gcc come with Solaris U4 doesn't have objective-C enabled.<br /> &lt;pre&gt;<br /> bash-3.00# /usr/sfw/bin/gcc -v<br /> Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs<br /> Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure <br /> --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as <br /> --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared<br /> Thread model: posix<br /> gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)<br /> bash-3.00#<br /> &lt;/pre&gt;<br /> <br /> ** TBA.<br /> <br /> == GNU Objective C Compiler and Runtime ==<br /> <br /> === What is the Objective C Runtime? ===<br /> <br /> The Objective C Runtime Library provides C functions and data structures required to execute an Objective C program.<br /> <br /> The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @&quot;&quot;-style string objects).<br /> <br /> It also has several differences over NeXT's implementation:<br /> <br /> * GNU's runtime provides &quot;selector-types&quot; along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).<br /> <br /> * Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.<br /> <br /> Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.<br /> <br /> == GNUstep Base Library ==<br /> <br /> === What is the GNUstep Base Library? ===<br /> <br /> The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops, and random number generators.<br /> <br /> It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).<br /> <br /> === What is its current state of development? ===<br /> <br /> GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.<br /> <br /> === What are the features of GNU Distributed Objects? ===<br /> <br /> GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.<br /> <br /> NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.<br /> Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU &quot;typed selector&quot; mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like. <br /> <br /> == GNUstep GUI Library ==<br /> <br /> === What is the GUI Library? ===<br /> <br /> The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many peripheral classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.<br /> <br /> It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.<br /> <br /> === Explain the organization of the front- and back-ends ===<br /> <br /> The GNUstep GUI Library is divided into a front- and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X Windows. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. Much work will be saved by this clean separation between front- and back-end, because it allows different platforms to share the large amount of front-end code.<br /> <br /> === What is the current state of development of the front-end? ===<br /> Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.<br /> <br /> === What is the current state of development of the back-ends? ===<br /> <br /> There are several backends currently available:<br /> <br /> * '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing. <br /> * '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality. It is currently the standard backend (as long as the required libraries are installed). <br /> * '''w32:''' This backend works on Windows and uses basic Windows drawing <br /> * '''cairo:''' An up-and-coming backend. It still relies on unpublished functions in the cairo library so using it is not for the beginner. <br /> <br /> == GNUstep DisplayGhostScript Server ==<br /> <br /> === What is the Display Ghostscript Server? ===<br /> <br /> It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.<br /> <br /> At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.<br /> <br /> === What is its current state of development? ===<br /> <br /> GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.<br /> <br /> === What is the relationship between the Display Ghostscript Server and X Windows? ===<br /> <br /> Display Ghostscript runs on top of X Windows.</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Developer_FAQ&diff=4890 2007-11-07T14:25:05Z

<p>Tjyang: /* How can I take part with a GNUstep autobuilder for the testfarm? */</p> <hr /> <div>[[Category:FAQ]]<br /> <br /> Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.<br /> <br /> == Compatibility ==<br /> <br /> === Is it easy to port OPENSTEP programs to GNUstep? ===<br /> <br /> It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === How about porting between Cocoa and GNUstep? ===<br /> <br /> It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === Tools for porting ===<br /> <br /> While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.<br /> <br /> * '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).<br /> * '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.<br /> * '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.<br /> * '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.<br /> * '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.<br /> <br /> === Can I transfer archived data from GNUstep to Cocoa? ===<br /> <br /> Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.<br /> <br /> The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.<br /> <br /> === Does distributed objects work between GNUstep and Cocoa? ===<br /> <br /> See the answer to the previous question (on archive compatibility) for why this won't work either.<br /> <br /> === Is there an Interface Builder for GNUstep? ===<br /> <br /> There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].<br /> <br /> === Can I use my original NIB files? ===<br /> It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later. <br /> <br /> Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.<br /> <br /> === Can one use the hybrid &quot;Objective-C++&quot; ? ===<br /> <br /> Yes. As of release 4.1 the GNU C Compiler (GCC) supports &quot;Objective-C++&quot;.<br /> <br /> === Is there a plan to support the Java/YellowBox Bindings? ===<br /> <br /> Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects. <br /> <br /> === What if I compile GNUstep under OPENSTEP/MacOS X? ===<br /> <br /> GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.<br /> <br /> You can, however, use a GNUstep program with an X11 server running on MacOSX.<br /> <br /> === Is the Objective C API for GTK related? ===<br /> <br /> No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.<br /> <br /> The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks. <br /> <br /> === How about implementing parts of the Application Kit with GTK? ===<br /> <br /> Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.<br /> <br /> That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome. <br /> <br /> == Compiling and Developing ==<br /> <br /> === How can I get started programming? ===<br /> Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)<br /> <br /> === Why doesn't GDB support Objective-C? ===<br /> As of GDB 6.0, gdb supports debugging of Objective-C code.<br /> <br /> == How can I help with GNUstep? ==<br /> <br /> The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.<br /> <br /> Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep. <br /> <br /> Here are the next steps: <br /> * Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]<br /> * Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.<br /> * For a bigger challenge, finish off part of the [[Roadmap]]<br /> <br /> === How do I start writing applications? ===<br /> <br /> You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.<br /> <br /> Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.<br /> <br /> === Helping develop GNUstep === <br /> <br /> There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.<br /> <br /> Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].<br /> <br /> Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.<br /> <br /> Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.<br /> <br /> Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation. <br /> <br /> Specific tasks are noted in the developers section on the GNUstep website.<br /> <br /> === Helping document GNUstep ===<br /> <br /> All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.<br /> <br /> Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.<br /> <br /> More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!<br /> <br /> Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.<br /> <br /> GNUstep documentation should have copyright assigned to the Free Software Foundation.<br /> <br /> === How do I assign my contribution? ===<br /> <br /> Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).<br /> <br /> === How do I update the task list? ===<br /> <br /> The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).<br /> <br /> One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.<br /> <br /> Send any changes or additions to bug-gnustep@gnu.org.<br /> <br /> A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.<br /> <br /> If a class or method is<br /> <br /> * in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.<br /> * in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP<br /> * in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X<br /> <br /> There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.<br /> <br /> === How do I start writing tests? ===<br /> <br /> You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.<br /> <br /> To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.<br /> <br /> === How can I help with the GNUstep website? ===<br /> <br /> '''Please consider contributing to this Wiki as opposed to the website.'''<br /> Contact Adam Fedor fedor@gnu.org, the maintainer.<br /> <br /> The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.<br /> <br /> If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.<br /> <br /> If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.<br /> <br /> The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.<br /> <br /> === How can I take part with a GNUstep autobuilder for the testfarm? ===<br /> * General Procedure<br /> ** Make sure your build system have a gcc compiler with objc support.<br /> ** mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/Startup.current.tar.bz2<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> ** tar xjf Startup.current.tar.bz2<br /> ** tar xjf core.current.tar.bz2<br /> ** cd Startup/scripts<br /> ** ./test-gnustep<br /> <br /> The results get posted to the gnustep-dev@gnu.org list and to http://ftp.gnustep.org/pub/testfarm/. The test script will automatically update using SVN if possible.<br /> <br /> * Solaris 10 x86 Procedure<br /> ** OS info<br /> *** Solaris 10 x86 Update 4, with everything installed.<br /> &lt;pre&gt;<br /> bash-3.00# cat /etc/release<br /> Solaris 10 8/07 s10x_u4wos_12b X86<br /> Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.<br /> Use is subject to license terms.<br /> Assembled 16 August 2007<br /> bash-3.00#<br /> <br /> &lt;/pre&gt;<br /> ** Make sure you have a gcc compiler with objc support.<br /> *** gcc come with Solaris U4 doesn't have objective-C enabled.<br /> &lt;pre&gt;<br /> bash-3.00# /usr/sfw/bin/gcc -v<br /> Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs<br /> Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared<br /> Thread model: posix<br /> gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)<br /> bash-3.00#<br /> <br /> &lt;/pre&gt;<br /> ** TBA.<br /> <br /> == GNU Objective C Compiler and Runtime ==<br /> <br /> === What is the Objective C Runtime? ===<br /> <br /> The Objective C Runtime Library provides C functions and data structures required to execute an Objective C program.<br /> <br /> The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @&quot;&quot;-style string objects).<br /> <br /> It also has several differences over NeXT's implementation:<br /> <br /> * GNU's runtime provides &quot;selector-types&quot; along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).<br /> <br /> * Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.<br /> <br /> Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.<br /> <br /> == GNUstep Base Library ==<br /> <br /> === What is the GNUstep Base Library? ===<br /> <br /> The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops, and random number generators.<br /> <br /> It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).<br /> <br /> === What is its current state of development? ===<br /> <br /> GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.<br /> <br /> === What are the features of GNU Distributed Objects? ===<br /> <br /> GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.<br /> <br /> NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.<br /> Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU &quot;typed selector&quot; mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like. <br /> <br /> == GNUstep GUI Library ==<br /> <br /> === What is the GUI Library? ===<br /> <br /> The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many peripheral classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.<br /> <br /> It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.<br /> <br /> === Explain the organization of the front- and back-ends ===<br /> <br /> The GNUstep GUI Library is divided into a front- and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X Windows. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. Much work will be saved by this clean separation between front- and back-end, because it allows different platforms to share the large amount of front-end code.<br /> <br /> === What is the current state of development of the front-end? ===<br /> Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.<br /> <br /> === What is the current state of development of the back-ends? ===<br /> <br /> There are several backends currently available:<br /> <br /> * '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing. <br /> * '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality. It is currently the standard backend (as long as the required libraries are installed). <br /> * '''w32:''' This backend works on Windows and uses basic Windows drawing <br /> * '''cairo:''' An up-and-coming backend. It still relies on unpublished functions in the cairo library so using it is not for the beginner. <br /> <br /> == GNUstep DisplayGhostScript Server ==<br /> <br /> === What is the Display Ghostscript Server? ===<br /> <br /> It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.<br /> <br /> At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.<br /> <br /> === What is its current state of development? ===<br /> <br /> GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.<br /> <br /> === What is the relationship between the Display Ghostscript Server and X Windows? ===<br /> <br /> Display Ghostscript runs on top of X Windows.</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Developer_FAQ&diff=4889 2007-11-07T14:23:55Z

<p>Tjyang: /* How can I take part with a GNUstep autobuilder for the testfarm? */</p> <hr /> <div>[[Category:FAQ]]<br /> <br /> Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.<br /> <br /> == Compatibility ==<br /> <br /> === Is it easy to port OPENSTEP programs to GNUstep? ===<br /> <br /> It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === How about porting between Cocoa and GNUstep? ===<br /> <br /> It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === Tools for porting ===<br /> <br /> While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.<br /> <br /> * '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).<br /> * '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.<br /> * '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.<br /> * '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.<br /> * '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.<br /> <br /> === Can I transfer archived data from GNUstep to Cocoa? ===<br /> <br /> Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.<br /> <br /> The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.<br /> <br /> === Does distributed objects work between GNUstep and Cocoa? ===<br /> <br /> See the answer to the previous question (on archive compatibility) for why this won't work either.<br /> <br /> === Is there an Interface Builder for GNUstep? ===<br /> <br /> There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].<br /> <br /> === Can I use my original NIB files? ===<br /> It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later. <br /> <br /> Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.<br /> <br /> === Can one use the hybrid &quot;Objective-C++&quot; ? ===<br /> <br /> Yes. As of release 4.1 the GNU C Compiler (GCC) supports &quot;Objective-C++&quot;.<br /> <br /> === Is there a plan to support the Java/YellowBox Bindings? ===<br /> <br /> Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects. <br /> <br /> === What if I compile GNUstep under OPENSTEP/MacOS X? ===<br /> <br /> GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.<br /> <br /> You can, however, use a GNUstep program with an X11 server running on MacOSX.<br /> <br /> === Is the Objective C API for GTK related? ===<br /> <br /> No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.<br /> <br /> The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks. <br /> <br /> === How about implementing parts of the Application Kit with GTK? ===<br /> <br /> Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.<br /> <br /> That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome. <br /> <br /> == Compiling and Developing ==<br /> <br /> === How can I get started programming? ===<br /> Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)<br /> <br /> === Why doesn't GDB support Objective-C? ===<br /> As of GDB 6.0, gdb supports debugging of Objective-C code.<br /> <br /> == How can I help with GNUstep? ==<br /> <br /> The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.<br /> <br /> Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep. <br /> <br /> Here are the next steps: <br /> * Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]<br /> * Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.<br /> * For a bigger challenge, finish off part of the [[Roadmap]]<br /> <br /> === How do I start writing applications? ===<br /> <br /> You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.<br /> <br /> Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.<br /> <br /> === Helping develop GNUstep === <br /> <br /> There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.<br /> <br /> Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].<br /> <br /> Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.<br /> <br /> Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.<br /> <br /> Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation. <br /> <br /> Specific tasks are noted in the developers section on the GNUstep website.<br /> <br /> === Helping document GNUstep ===<br /> <br /> All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.<br /> <br /> Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.<br /> <br /> More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!<br /> <br /> Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.<br /> <br /> GNUstep documentation should have copyright assigned to the Free Software Foundation.<br /> <br /> === How do I assign my contribution? ===<br /> <br /> Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).<br /> <br /> === How do I update the task list? ===<br /> <br /> The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).<br /> <br /> One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.<br /> <br /> Send any changes or additions to bug-gnustep@gnu.org.<br /> <br /> A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.<br /> <br /> If a class or method is<br /> <br /> * in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.<br /> * in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP<br /> * in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X<br /> <br /> There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.<br /> <br /> === How do I start writing tests? ===<br /> <br /> You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.<br /> <br /> To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.<br /> <br /> === How can I help with the GNUstep website? ===<br /> <br /> '''Please consider contributing to this Wiki as opposed to the website.'''<br /> Contact Adam Fedor fedor@gnu.org, the maintainer.<br /> <br /> The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.<br /> <br /> If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.<br /> <br /> If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.<br /> <br /> The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.<br /> <br /> === How can I take part with a GNUstep autobuilder for the testfarm? ===<br /> * General Procedure<br /> ** Make sure you have a gcc compiler with objc support.<br /> ** mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/Startup.current.tar.bz2<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> ** tar xjf Startup.current.tar.bz2<br /> ** tar xjf core.current.tar.bz2<br /> ** cd Startup/scripts<br /> ** ./test-gnustep<br /> <br /> The results get posted to the gnustep-dev@gnu.org list and to http://ftp.gnustep.org/pub/testfarm/. The test script will automatically update using SVN if possible.<br /> <br /> * Solaris 10 x86 Procedure<br /> ** OS info<br /> *** Solaris 10 x86 Update 4, with everything installed.<br /> &lt;pre&gt;<br /> bash-3.00# cat /etc/release<br /> Solaris 10 8/07 s10x_u4wos_12b X86<br /> Copyright 2007 Sun Microsystems, Inc. All Rights Reserved.<br /> Use is subject to license terms.<br /> Assembled 16 August 2007<br /> bash-3.00#<br /> <br /> &lt;/pre&gt;<br /> ** Make sure you have a gcc compiler with objc support.<br /> *** gcc come with Solaris U4 doesn't have objective-C enabled.<br /> &lt;pre&gt;<br /> bash-3.00# /usr/sfw/bin/gcc -v<br /> Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.10/3.4.3/specs<br /> Configured with: /builds/sfw10-gate/usr/src/cmd/gcc/gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++ --enable-shared<br /> Thread model: posix<br /> gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath)<br /> bash-3.00#<br /> <br /> &lt;/pre&gt;<br /> ** TBA.<br /> <br /> == GNU Objective C Compiler and Runtime ==<br /> <br /> === What is the Objective C Runtime? ===<br /> <br /> The Objective C Runtime Library provides C functions and data structures required to execute an Objective C program.<br /> <br /> The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @&quot;&quot;-style string objects).<br /> <br /> It also has several differences over NeXT's implementation:<br /> <br /> * GNU's runtime provides &quot;selector-types&quot; along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).<br /> <br /> * Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.<br /> <br /> Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.<br /> <br /> == GNUstep Base Library ==<br /> <br /> === What is the GNUstep Base Library? ===<br /> <br /> The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops, and random number generators.<br /> <br /> It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).<br /> <br /> === What is its current state of development? ===<br /> <br /> GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.<br /> <br /> === What are the features of GNU Distributed Objects? ===<br /> <br /> GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.<br /> <br /> NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.<br /> Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU &quot;typed selector&quot; mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like. <br /> <br /> == GNUstep GUI Library ==<br /> <br /> === What is the GUI Library? ===<br /> <br /> The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many peripheral classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.<br /> <br /> It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.<br /> <br /> === Explain the organization of the front- and back-ends ===<br /> <br /> The GNUstep GUI Library is divided into a front- and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X Windows. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. Much work will be saved by this clean separation between front- and back-end, because it allows different platforms to share the large amount of front-end code.<br /> <br /> === What is the current state of development of the front-end? ===<br /> Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.<br /> <br /> === What is the current state of development of the back-ends? ===<br /> <br /> There are several backends currently available:<br /> <br /> * '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing. <br /> * '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality. It is currently the standard backend (as long as the required libraries are installed). <br /> * '''w32:''' This backend works on Windows and uses basic Windows drawing <br /> * '''cairo:''' An up-and-coming backend. It still relies on unpublished functions in the cairo library so using it is not for the beginner. <br /> <br /> == GNUstep DisplayGhostScript Server ==<br /> <br /> === What is the Display Ghostscript Server? ===<br /> <br /> It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.<br /> <br /> At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.<br /> <br /> === What is its current state of development? ===<br /> <br /> GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.<br /> <br /> === What is the relationship between the Display Ghostscript Server and X Windows? ===<br /> <br /> Display Ghostscript runs on top of X Windows.</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Developer_FAQ&diff=4888 2007-11-07T14:18:34Z

<p>Tjyang: improve the procedure</p> <hr /> <div>[[Category:FAQ]]<br /> <br /> Please send corrections to gnustep-maintainer@gnu.org. Also look at the [[User FAQ]] for more user oriented questions.<br /> <br /> == Compatibility ==<br /> <br /> === Is it easy to port OPENSTEP programs to GNUstep? ===<br /> <br /> It is probably easy for simple programs. There are some portability tools to make this easier, or rewrite the Makefiles yourself. You will also have to translate the NIB files (if there are any) to GNUstep model files using the nib2gmodel program. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === How about porting between Cocoa and GNUstep? ===<br /> <br /> It's easier from GNUstep to Cocoa than Cocoa to GNUstep. Cocoa is constantly changing, much faster than GNUstep could hope to keep up. They have added extensions and new classes that aren't available in GNUstep yet. Plus there are some other issues. See the [[Writing portable code#Porting_from_Cocoa_or_OPENSTEP_.28NS.2A.29_to_GNUstep|portability]] page for details.<br /> <br /> === Tools for porting ===<br /> <br /> While the programming interface should be almost transparent between systems (expect for the unimplemented parts, of course), there are a variety of other files and tools that are necessary for porting programs.<br /> <br /> * '''nib2gmodel:''' This program coverts nib files from any system, such as Cocoa or OPENSTEP to a gmodel format file. Gmodel can be read directly by GNUstep or you can convert this to a more GNUstep-native gorm format (using the Gorm interface modeller).<br /> * '''Renaissance:''' GNUstep Renaissance allows you to describe your user interfaces (that is, the windows in your application, and the buttons, boxes, textfields, etc in the windows) in simple and intuitive XML files, using an open, standard format describing the logic of the interface. It has a number of advantages over the proprietary nib format: portability, open standard, easy localization, themeability, and intelligent autolayout.<br /> * '''[[Gorm]]:''' The equivalent of the Interface Builder in GNUstep. As of version 1.1.0 Gorm allows reading and writing of Mac OS 10.2 or later Cocoa NIB files. Please see http://lists.gnu.org/archive/html/discuss-gnustep/2006-09/msg00008.html.<br /> * '''OpenStep2GNUConverter and nfmake:''' Two programs that allow you to convert PB files to GNUstep makefiles or compile a program on GNUstep directly from PB files. They probably work only for OPENSTEP systems and are a little out-of-date.<br /> * '''StepTalk:''' A portable scripting environment that lets your do scripting in almost any language you like.<br /> <br /> === Can I transfer archived data from GNUstep to Cocoa? ===<br /> <br /> Apple's archiving format is proprietary and not documented, so this poses a problem for anyone wanting to implement compatibility with it. However, even if we reverse engineered the format, there are enough differences between the class and ivar layouts to make this sort of compatibility difficult. Not to mention the fact that we would constantly have to keep up with the changes Apple made. Also Apple's archiving format, as far as we know, would not be compatible between different machines because of endiness issues, although GNUstep doesn't have this problem.<br /> <br /> The new keyed archiving using XML file formats is much more portable, and GNUstep is trying to maintain compatibility with Apple for this type of archiving.<br /> <br /> === Does distributed objects work between GNUstep and Cocoa? ===<br /> <br /> See the answer to the previous question (on archive compatibility) for why this won't work either.<br /> <br /> === Is there an Interface Builder for GNUstep? ===<br /> <br /> There is an Interface Builder for GNUstep called [[Gorm]]. A lot of work has been put into it and it works very well. The project manager [[ProjectCenter]] is also available. There is also [[ProjectManager]].<br /> <br /> === Can I use my original NIB files? ===<br /> It is currently possible to use newer keyed archiving files which were created on Mac OS 10.2 or later. <br /> <br /> Older nibs, such as those from Mac OS 10.1 or from OPENSTEP which don't use keyed archiving aren't readable since Apple/NeXT never documented their nib format. These nibs must be translated into keyed nibs for use with GNUstep, if you have Mac OS 10.2 or later this is a simple matter of loading them into IB and saving them as keyed nibs. Alternatively, if you only have OPENSTEP you can use nib2gmodel to translate them into gmodel format.<br /> <br /> === Can one use the hybrid &quot;Objective-C++&quot; ? ===<br /> <br /> Yes. As of release 4.1 the GNU C Compiler (GCC) supports &quot;Objective-C++&quot;.<br /> <br /> === Is there a plan to support the Java/YellowBox Bindings? ===<br /> <br /> Yes. The GNustep Java library/bridge called JIGS is available now. JIGS is a free (LGPL) Java Interface for GNUstep; it can automatically wrap Objective-C libraries based on GNUstep, making them accessible directly to the Java programmer as if they were Java libraries. As a side effect, it is also possible to use the whole engine in the reverse way: JIGS provides a high level API to allow Objective-C programmers to start java virtual machines inside GNUstep Objective-C code and access java objects in the java virtual machine transparently, as if they were objective-C objects. <br /> <br /> === What if I compile GNUstep under OPENSTEP/MacOS X? ===<br /> <br /> GNUstep uses the X-windows display postscript extension. The interface to that is not the same as the interface to the OPENSTEP/MacOS-X windows server. While someone could write a backend library to provide the interface, nobody has bothered to date.<br /> <br /> You can, however, use a GNUstep program with an X11 server running on MacOSX.<br /> <br /> === Is the Objective C API for GTK related? ===<br /> <br /> No. GNUstep applications provide their GUI via the OpenStep API, which provides fully object-oriented access to GUI manipulation.<br /> <br /> The object-oriented nature of the libraries and language make it much easier for new users to create their own subclasses rather than simply using the supplied widgets as in other frameworks. <br /> <br /> === How about implementing parts of the Application Kit with GTK? ===<br /> <br /> Yes and No - The GNUstep architecture provides a single, platform-independent, API for handling all aspects of GUI interaction (implemented in the gstep-gui library), with a backend architecture that permits you to have different display models (display postscript, X-windows, win32, berlin ...) while letting you use the same code for printing as for displaying. Use of GTK in the frontend gui library would remove some of those advantages without adding any.<br /> <br /> That being said, a backend library could be implemented using gtk if anyone wanted to do so. Since the frontend library handles most of the work involved in implementing the OpenStep API, the backend is a relatively thin layer and the advantages of GTK over direct xlib or win32 calls is likely to be minimal. If/when GTK is ported to more systems, a backend written using it could be a valuable asset - volunteers are, as always, welcome. <br /> <br /> == Compiling and Developing ==<br /> <br /> === How can I get started programming? ===<br /> Good question. Please refer to the tutorials for some suggestions. Also look at Apple's documentation (pointers in the Resources section on the GNUstep web site.)<br /> <br /> === Why doesn't GDB support Objective-C? ===<br /> As of GDB 6.0, gdb supports debugging of Objective-C code.<br /> <br /> == How can I help with GNUstep? ==<br /> <br /> The first task is probably just to get familiar with it, then there's a lot you can do. Write library code or applications to get a feel for it. See the [[GNUstepWiki:Community_Portal|community portal]] for an overview of what a GNUstep developer should know.<br /> <br /> Another simple way to get familiar with GNUstep is to help write documentation. A lot of documentation is written in the source code itself, and autogenerated. You could also improve on several of the manuals that explain the overall usage of GNUstep. <br /> <br /> Here are the next steps: <br /> * Start off by fixing [http://savannah.gnu.org/bugs/?group_id=99 bugs]<br /> * Look at the [[#How_do_I_update_the_task_list.3F|list of tasks]] for longer term work and check [[Ideas]] for other ideas.<br /> * For a bigger challenge, finish off part of the [[Roadmap]]<br /> <br /> === How do I start writing applications? ===<br /> <br /> You can either look at the links on the GNUstep website for applications that have been started, and email their owners to volunteer to help, or you can start your own project.<br /> <br /> Let people know what you are doing. Break your project up into the smallest units you can. Feed back frequent updates to the maintainers. Ask questions in the discussion mailing list.<br /> <br /> === Helping develop GNUstep === <br /> <br /> There is plenty of unimplemented stuff in the gui library and backend libraries that volunteers can work on, just browse through the code and see if it conforms to the documentation.<br /> <br /> Do remember that any changes beyond a few lines of code (or documentation) require a disclaimer or copyright assignment to the Free Software Foundation before they can be incorporated into the project. [[#How_do_I_assign_my_contribution.3F|See below]].<br /> <br /> Don't start with large-scale reorganization of anything -- instead, get a general idea in mind of what you want to do, and proceed as much as possible with incremental changes that don't break anything - that way you can make those incremental changes available to the rest of the community at frequent intervals.<br /> <br /> Don't be afraid to give up - there is no shame in finding out that you have take on too large/complex a project. It's much better to 'resign' and take on a smaller job than to just stop without telling anyone.<br /> <br /> Please document the code you add or change (using autogsdoc comments that begin with a slash and two asterices) and maybe write a testcase for it. But PLEASE, do not copy from the Apple documentation or any other copyrighted documentation. <br /> <br /> Specific tasks are noted in the developers section on the GNUstep website.<br /> <br /> === Helping document GNUstep ===<br /> <br /> All class documentation is written directly in the source code itself and translated using the autogsdoc program. See the source code and documentation for autogsdoc for information on documenting the classes.<br /> <br /> Newcomers could write documentation for individual classes by comparing the OpenStep specification, the MacOS-X documentation, and the GNUstep source. Documentation should clearly note where individual methods are specific to OpenStep, MacOS-X or are GNustep extensions.<br /> <br /> More experienced people could write documentation on general programming topics, and tutorials for new users. Contributors to the wiki are welcome!<br /> <br /> Anyone willing to write documentation, either tutorials for using GNUstep, or reference documentation for individual classes, should either write it in gsdoc or as plain ascii text for someone else to format into gsdoc.<br /> <br /> GNUstep documentation should have copyright assigned to the Free Software Foundation.<br /> <br /> === How do I assign my contribution? ===<br /> <br /> Everyone who contributes more than 20 lines of code or so needs to sign a copyright assignment so that the FSF can have legal control of the copyright. This makes it easier to defend against any copyright infringement suits. Contact the GNUstep maintainer for instructions on how to do this or download and fill out the form http://www.gnustep.org/resources/request-assign.future (instructions are included).<br /> <br /> === How do I update the task list? ===<br /> <br /> The [http://savannah.gnu.org/pm/?group_id=99 task list] is supposed to tell people what jobs are waiting to be done. Feel free to add to it or update the tasks that are there (you need to create a login for yourself first).<br /> <br /> One job of major importance that pretty much anyone can do is to look for jobs to add to the task list. In the case of methods from the OpenStep specification or the MacOS-X documentation not being present in the GNUstep libraries, it is also helpful to add the method prototypes to the library header files.<br /> <br /> Send any changes or additions to bug-gnustep@gnu.org.<br /> <br /> A beginner can look through the MacOS-X documentation, the OpenStep specification and the GNUstep source and contribute task items.<br /> <br /> If a class or method is<br /> <br /> * in MacOS-X and OpenStep but is not in GNUstep, it's a high priority TODO and should at least be added to the GNUstep headers and a dummy version added to the source with a FIXME comment.<br /> * in MacOS-X but not OpenStep or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_OPENSTEP<br /> * in OpenStep but not in MacOS-X or GNUstep, it's a low priority TODO. It should be added to the GNUstep headers bracketed in #ifndef STRICT_MACOS_X<br /> <br /> There are a couple of people working on this already, so it's a good idea to get in touch with Adam or Richard to coordinate efforts.<br /> <br /> === How do I start writing tests? ===<br /> <br /> You can write testcases - where the libraries fail tests, you could either fix the problem, or add it to the task list.<br /> <br /> To write testcases, you need to use svn to install the latest GNUstep sourcecode you can find. Then checkout the 'gnustep/tools/testsuite' module from svn.<br /> <br /> === How can I help with the GNUstep website? ===<br /> <br /> '''Please consider contributing to this Wiki as opposed to the website.'''<br /> Contact Adam Fedor fedor@gnu.org, the maintainer.<br /> <br /> The GNUstep website is kept as a CVS module, but the largest portions of it (the FAQ and the Documentation) are actually generated from files in the individual GNUstep packages.<br /> <br /> If you want to update the FAQ or documentation - grab the latest snapshot of the GNUstep core you can find, update it from the svn repository, and work with the contents of the appropriate documentation directory.<br /> <br /> If you want to work on other parts of the website, you can grab a copy of the website via anonymous CVS. See http://savannah.gnu.org/cvs/?group_id=99 for instructions on how to do that.<br /> <br /> The main task with the website is to figure out which bits are out-of-date (or wrong) and update/mark-as-outdated as required.<br /> <br /> === How can I take part with a GNUstep autobuilder for the testfarm? ===<br /> * General Procedure<br /> ** Make sure you have a gcc compiler with objc support.<br /> ** mkdir gnustep-testfarm &amp;&amp; cd gnustep-testfarm<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/Startup.current.tar.bz2<br /> ** wget http://ftp.gnustep.org/pub/daily-snapshots/core.current.tar.bz2<br /> ** tar xjf Startup.current.tar.bz2<br /> ** tar xjf core.current.tar.bz2<br /> ** cd Startup/scripts<br /> ** ./test-gnustep<br /> <br /> The results get posted to the gnustep-dev@gnu.org list and to http://ftp.gnustep.org/pub/testfarm/. The test script will automatically update using SVN if possible.<br /> <br /> * Solaris 10 x86 Procedure<br /> ** Make sure you have a gcc compiler with objc support.<br /> ** TBA.<br /> <br /> == GNU Objective C Compiler and Runtime ==<br /> <br /> === What is the Objective C Runtime? ===<br /> <br /> The Objective C Runtime Library provides C functions and data structures required to execute an Objective C program.<br /> <br /> The GNU Objective C Runtime Library offers everything NeXT's runtime does, including Categories, Protocols, `+poseAs:', thread-safety, class initialization on demand, delayed loading of classes, and initialization of static instances (such as @&quot;&quot;-style string objects).<br /> <br /> It also has several differences over NeXT's implementation:<br /> <br /> * GNU's runtime provides &quot;selector-types&quot; along with each selector; NeXT's does not. A selector-type is a string that describes the C variable types for the method's return and argument values. Among other uses, selector-types is extremely helpful for fast distributed objects implementations, (see GNUstep Base Library Section, below).<br /> <br /> * Many of the GNU functions have different names than their corresponding NeXT functions; the GNU names conform to the GNU coding standards. The GNUstep base library contains a compatibility header that works with both runtimes. You should use functions there or use OpenStep Foundation methods/functions instead of the basic runtime functions so that you code can run with either system.<br /> <br /> Apple has recently added new functionality to their runtime, including built-in exception handling, etc. Hopefully these will be ported to the GNU runtime in the future.<br /> <br /> == GNUstep Base Library ==<br /> <br /> === What is the GNUstep Base Library? ===<br /> <br /> The GNUstep Base Library is a library of general-purpose, non-graphical Objective C objects. For example, it includes classes for strings, object collections, byte streams, typed coders, invocations, notifications, notification dispatchers, moments in time, network ports, remote object messaging support (distributed objects), event loops, and random number generators.<br /> <br /> It provides functionality that aims to implement the non-graphical portion of the OpenStep standard (the Foundation library).<br /> <br /> === What is its current state of development? ===<br /> <br /> GNUstep base is currently stable and, to the best of our knowledge, implements all of the OpenStep functionality (except for a few classes that we feel are not useful). It also implements most all of the new Cocoa classes. However we do some things, like scripting, differently, so we don't implement all the Cocoa classes.<br /> <br /> === What are the features of GNU Distributed Objects? ===<br /> <br /> GNU Distributed Objects has many of the features of other distributed objects implementations, but, since it is free software, it can be ported to platforms for which other distributed objects implementations are not available.<br /> <br /> NOTE: The GNU distributed object facilities have the same ease-of-use as Apple's; be warned, however, that they are not compatible with each other. They have different class hierarchies, different instance variables, different method names, different implementation strategies and different network message formats. You cannot communicate with a Apple NSConnection using a GNU NSConnection.<br /> Here are some differences between GNU distributed objects and Apple's distributed objects: Apple NSDistantObject asks it's remote target for the method encoding types and caches the results; GNU NSDistantObject gets the types directly from the local GNU &quot;typed selector&quot; mechanism if the information is known locally and only queries the remote target or caching encoding types when using a method that is not known to the local process. The NSProxy for the remote root object always has name and, once set, you cannot change the root object of a NSConnection; the GNU Proxy for the remote root object has a target address value just like all other Proxy's, and you can change the root object as many times as you like. <br /> <br /> == GNUstep GUI Library ==<br /> <br /> === What is the GUI Library? ===<br /> <br /> The GNUstep GUI Library is a library of objects useful for writing graphical applications. For example, it includes classes for drawing and manipulating graphics objects on the screen: windows, menus, buttons, sliders, text fields, and events. There are also many peripheral classes that offer operating-system-independent interfaces to images, cursors, colors, fonts, pasteboards, printing. There are also workspace support classes such as data links, open/save panels, context-dependent help, spell checking.<br /> <br /> It provides functionality that aims to implement the `AppKit' portion of the OpenStep standard. However the implementation has been written to take advantage of GNUstep enhancements wherever possible.<br /> <br /> === Explain the organization of the front- and back-ends ===<br /> <br /> The GNUstep GUI Library is divided into a front- and back-end. The front-end contains the majority of implementation, but leaves out the low-level drawing and event code. A back-end can override whatever methods necessary in order to implement low-level drawing event receiving. Different back-ends will make GNUstep available on various platforms. The default GNU back-end will run on top of X Windows. Other back-ends could allow GNUstep to run on OpenGL and WIN32 graphics/event platforms. Much work will be saved by this clean separation between front- and back-end, because it allows different platforms to share the large amount of front-end code.<br /> <br /> === What is the current state of development of the front-end? ===<br /> Many of the classes are well implemented, if not thoroughly tested. See the GNUstep web sites and read status information contained in the distribution for the most up-to-date information.<br /> <br /> === What is the current state of development of the back-ends? ===<br /> <br /> There are several backends currently available:<br /> <br /> * '''xlib:''' This backend runs on X11 and uses standard xlib calls for implementing drawing. It works well, but is limited in many areas due to the limitations of xlib drawing. <br /> * '''art:''' This is a very good backend that draws using the libart package and freetype with near PostScript quality and functionality. It is currently the standard backend (as long as the required libraries are installed). <br /> * '''w32:''' This backend works on Windows and uses basic Windows drawing <br /> * '''cairo:''' An up-and-coming backend. It still relies on unpublished functions in the cairo library so using it is not for the beginner. <br /> <br /> == GNUstep DisplayGhostScript Server ==<br /> <br /> === What is the Display Ghostscript Server? ===<br /> <br /> It is a free implementation of a Display PostScript server based on the GNU Ghostscript program developed by Aladdin Enterprises and now owned by artofcode LLC.<br /> <br /> At one point, GNUstep was using this for display purposes. However the development of DGS has stopped as it is too difficult to maintain and no one wanted to work on it. Now we are using other means of drawing.<br /> <br /> === What is its current state of development? ===<br /> <br /> GNU contracted with Aladdin Enterprises to add some key features to GNU Ghostscript so it could be used as a DPS server. This work has mostly been done, although Aladdin did not completely finish the work that they were contracted for. (Because the work took longer than specified and was not completed, Aladdin agreed to waive approximately $10,000 in promised fees for the work that was actually done and delivered.) DGS works fairly well with a single context. Alpha channel and compositing doesn't work.<br /> <br /> === What is the relationship between the Display Ghostscript Server and X Windows? ===<br /> <br /> Display Ghostscript runs on top of X Windows.</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Platform_compatibility&diff=4239 2007-01-14T01:35:14Z

<p>Tjyang: /* GNUstep Solaris 10 U3 vmware appliance */</p> <hr /> <div>{{stub}}<br /> Following are procedures for installing GNUstep on different Operating Systems.<br /> * You may also want to take a look at the [[dependencies]].<br /> <br /> <br /> = BSD-based systems =<br /> To keep this list as brief as possible, information about these systems can [[Platform:BSD|be found here]].<br /> <br /> <br /> <br /> <br /> = HP/UX =<br /> * GNUstep-core-1.0, please see http://en.wikibooks.org/wiki/CPAM_with_TWW/References_Manual#GNUstep_and_CPAM. look for the gnustep-core-1.0.sb and gnustep-core-1.0.pb file for building and packaging information.<br /> <br /> <br /> = Linux-based systems =<br /> To keep this list as brief as possible, information about these systems can [[Platform:Linux|be found here]].<br /> <br /> <br /> = Solaris =<br /> === Intel ===<br /> <br /> Move over to http://www.blastwave.org/ or http://www.sunfreeware.com/ to download and install all required [[dependencies]]. (Personally, I recommend the packages from BlastWave which usually are quite up-to-date. Interestingly, they already offer GNUstep-make as a package.)<br /> <br /> If you follow the installation instructions for GNUstep, you should not run into any problems.<br /> <br /> However, if you want to select Window Maker from the X login, you need to do some additional editing. Check out http://www.gunfleet.com/solaris/winman.htm for that.<br /> The information about Window Maker found there basically also applies if you plan on using Azalea from [http://www.etoile-project.org/etoile/mediawiki/index.php?title=Main Étoilé].<br /> <br /> === Sparc ===<br /> <br /> * http://www.linuks.mine.nu/gnustep/solaris is one of package sources to create solaris packages for GNUstep.<br /> * GNUstep-core-1.0, please see http://en.wikibooks.org/wiki/CPAM_with_TWW#GNUstep_and_TWW_HPMS. look for the gnustep-core-1.0.sb and gnustep-core-1.0.pb file for building and packaging information.<br /> <br /> === GNUstep Solaris 10 U2 vmware appliance ===<br /> <br /> * [http://developers.sun.com/solaris/downloads/solaris_apps/index.jsp Download sol u2 image], you need to have a Sun site account.<br /> * You can run this image in VMware server or vmware player 1.0.3.<br /> * Install Sun Studio 11 with latest patches.<br /> * Objective Compiler<br /> ** compile your own<br /> ** get it from blastwave using pkg-get.<br /> * download all the gnustep tar balls and follow build instruction.<br /> <br /> = OpenSolaris =<br /> <br /> This will be an add-on packages to OpenSolaris distributions using TWW tools to create sparc/intel packages in SVR4 formats. &quot;pkg-inst gnustep-user-1.0 gnustep-developer-1.0 gnustep-apps-1.0&quot; will install GNUstep user,developer and gnustep native applications. pkg-rm will perform the reverse of installation.<br /> <br /> It will have a nice name like GNUstep O.S. (OpenSolaris).<br /> <br /> = Windows =<br /> <br /> There are many Unix Environment solutions for windows. Currently GNUstep is using [http://www.mingw.org/ MingW] as its unix environment foundation for Windows.<br /> <br /> === MingW ===<br /> <br /> See [[Installation on Windows]] for details on MingW setup. Also look at precompiled binary installer, available from [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/ GNUstep's ftp site].<br /> <br /> = Others =<br /> To keep this list as brief as possible, information about these systems can [[Platform:Other|be found here]].<br /> <br /> <br /> [[Category:Development]]</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Platform_compatibility&diff=4238 2007-01-14T01:07:07Z

<p>Tjyang: /* Solaris */</p> <hr /> <div>{{stub}}<br /> Following are procedures for installing GNUstep on different Operating Systems.<br /> * You may also want to take a look at the [[dependencies]].<br /> <br /> <br /> = BSD-based systems =<br /> To keep this list as brief as possible, information about these systems can [[Platform:BSD|be found here]].<br /> <br /> <br /> <br /> <br /> = HP/UX =<br /> * GNUstep-core-1.0, please see http://en.wikibooks.org/wiki/CPAM_with_TWW/References_Manual#GNUstep_and_CPAM. look for the gnustep-core-1.0.sb and gnustep-core-1.0.pb file for building and packaging information.<br /> <br /> <br /> = Linux-based systems =<br /> To keep this list as brief as possible, information about these systems can [[Platform:Linux|be found here]].<br /> <br /> <br /> = Solaris =<br /> === Intel ===<br /> <br /> Move over to http://www.blastwave.org/ or http://www.sunfreeware.com/ to download and install all required [[dependencies]]. (Personally, I recommend the packages from BlastWave which usually are quite up-to-date. Interestingly, they already offer GNUstep-make as a package.)<br /> <br /> If you follow the installation instructions for GNUstep, you should not run into any problems.<br /> <br /> However, if you want to select Window Maker from the X login, you need to do some additional editing. Check out http://www.gunfleet.com/solaris/winman.htm for that.<br /> The information about Window Maker found there basically also applies if you plan on using Azalea from [http://www.etoile-project.org/etoile/mediawiki/index.php?title=Main Étoilé].<br /> <br /> === Sparc ===<br /> <br /> * http://www.linuks.mine.nu/gnustep/solaris is one of package sources to create solaris packages for GNUstep.<br /> * GNUstep-core-1.0, please see http://en.wikibooks.org/wiki/CPAM_with_TWW#GNUstep_and_TWW_HPMS. look for the gnustep-core-1.0.sb and gnustep-core-1.0.pb file for building and packaging information.<br /> <br /> === GNUstep Solaris 10 U3 vmware appliance ===<br /> <br /> = OpenSolaris =<br /> <br /> This will be an add-on packages to OpenSolaris distributions using TWW tools to create sparc/intel packages in SVR4 formats. &quot;pkg-inst gnustep-user-1.0 gnustep-developer-1.0 gnustep-apps-1.0&quot; will install GNUstep user,developer and gnustep native applications. pkg-rm will perform the reverse of installation.<br /> <br /> It will have a nice name like GNUstep O.S. (OpenSolaris).<br /> <br /> = Windows =<br /> <br /> There are many Unix Environment solutions for windows. Currently GNUstep is using [http://www.mingw.org/ MingW] as its unix environment foundation for Windows.<br /> <br /> === MingW ===<br /> <br /> See [[Installation on Windows]] for details on MingW setup. Also look at precompiled binary installer, available from [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/ GNUstep's ftp site].<br /> <br /> = Others =<br /> To keep this list as brief as possible, information about these systems can [[Platform:Other|be found here]].<br /> <br /> <br /> [[Category:Development]]</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4176 2006-12-30T00:48:45Z

<p>Tjyang: /* List of depended software */</p> <hr /> <div>= Install Windows GNUstep Manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = GNUstep .exe installer using Nullsoft's [http://nsis.sourceforge.net/Main_Page NSIS] =<br /> <br /> == install instruction ==<br /> There are three versions of exe installer for gnustep.<br /> <br /> * Download [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows gnustep NSIS installer ].<br /> ** select copy the binaries.<br /> <br /> <br /> * Download and compile gnustep examples tar ball.<br /> <br /> * &quot;openapp GSTest.app&quot; will bring up a screen with GNUstep interface.<br /> <br /> = GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =<br /> <br /> There are three sub packages <br /> * user : To minimize the footprint of gnustep system on Windows machines.<br /> * developer : include WiX,gcc and package sources.<br /> * gnustep applications : include a broad suite of GNUstep applications.<br /> == Install GNUstep MSI installer ==<br /> * Download the msi from here.<br /> * answer following questions.<br /> * Test the installation.<br /> == Prepare your gnustep win32 development environment ==<br /> === List of depended software ===<br /> * WiX Win32 MSI package creation tool.<br /> ** candle.exe <br /> &lt;pre&gt;<br /> C:\tmp&gt;candle<br /> Microsoft (R) Windows Installer Xml Compiler version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: candle.exe [-?] [-nologo] [-out outputFile] sourceFile [sourceFile ...]<br /> <br /> <br /> -d&lt;name&gt;=&lt;value&gt; define a parameter for the preprocessor<br /> -p&lt;file&gt; preprocess to a file (or stdout if no file supplied)<br /> -I&lt;dir&gt; add to include search path<br /> -nologo skip printing candle logo information<br /> -out specify output file (default: write to current directory)<br /> -pedantic:&lt;level&gt; pedantic checks (levels: easy, heroic, legendary)<br /> <br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> <br /> ** light.exe<br /> &lt;pre&gt;<br /> C:\tmp&gt;light<br /> Microsoft (R) Windows Installer Xml Linker version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: light.exe [-?] [-b basePath] [-nologo] [-out outputFile] objectFile [o<br /> jectFile ...]<br /> <br /> -ai allow identical rows, identical rows will be treated as a warning<br /> -au (experimental) allow unresolved references, will not create a val<br /> d output<br /> -b base path to locate all files (default: current directory)<br /> -cc path to cache built cabinets (will not be deleted after linking)<br /> <br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> * makefile for nmake.<br /> * gcc win32 compiler from MingW.<br /> <br /> === Checkout gnustep.wxs ===<br /> === overview of gnustep.wxs ===</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4175 2006-12-30T00:47:41Z

<p>Tjyang: /* GNUstep .exe installer created by Nullsoft's [http://nsis.sourceforge.net/Main_Page NSIS] */</p> <hr /> <div>= Install Windows GNUstep Manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = GNUstep .exe installer using Nullsoft's [http://nsis.sourceforge.net/Main_Page NSIS] =<br /> <br /> == install instruction ==<br /> There are three versions of exe installer for gnustep.<br /> <br /> * Download [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows gnustep NSIS installer ].<br /> ** select copy the binaries.<br /> <br /> <br /> * Download and compile gnustep examples tar ball.<br /> <br /> * &quot;openapp GSTest.app&quot; will bring up a screen with GNUstep interface.<br /> <br /> = GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =<br /> <br /> There are three sub packages <br /> * user : To minimize the footprint of gnustep system on Windows machines.<br /> * developer : include WiX,gcc and package sources.<br /> * gnustep applications : include a broad suite of GNUstep applications.<br /> == Install GNUstep MSI installer ==<br /> * Download the msi from here.<br /> * answer following questions.<br /> * Test the installation.<br /> == Prepare your gnustep win32 development environment ==<br /> === List of depended software ===<br /> * WiX Win32 PMS.<br /> ** candle.exe <br /> &lt;pre&gt;<br /> C:\tmp&gt;candle<br /> Microsoft (R) Windows Installer Xml Compiler version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: candle.exe [-?] [-nologo] [-out outputFile] sourceFile [sourceFile ...]<br /> <br /> <br /> -d&lt;name&gt;=&lt;value&gt; define a parameter for the preprocessor<br /> -p&lt;file&gt; preprocess to a file (or stdout if no file supplied)<br /> -I&lt;dir&gt; add to include search path<br /> -nologo skip printing candle logo information<br /> -out specify output file (default: write to current directory)<br /> -pedantic:&lt;level&gt; pedantic checks (levels: easy, heroic, legendary)<br /> <br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> <br /> ** light.exe<br /> &lt;pre&gt;<br /> C:\tmp&gt;light<br /> Microsoft (R) Windows Installer Xml Linker version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: light.exe [-?] [-b basePath] [-nologo] [-out outputFile] objectFile [o<br /> jectFile ...]<br /> <br /> -ai allow identical rows, identical rows will be treated as a warning<br /> -au (experimental) allow unresolved references, will not create a val<br /> d output<br /> -b base path to locate all files (default: current directory)<br /> -cc path to cache built cabinets (will not be deleted after linking)<br /> <br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> * makefile for nmake.<br /> * gcc win32 compiler from MingW.<br /> <br /> === Checkout gnustep.wxs ===<br /> === overview of gnustep.wxs ===</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4174 2006-12-30T00:40:40Z

<p>Tjyang: </p> <hr /> <div>= Install Windows GNUstep Manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = GNUstep .exe installer created by Nullsoft's [http://nsis.sourceforge.net/Main_Page NSIS] =<br /> <br /> == install instruction ==<br /> There are three versions of exe installer for gnustep.<br /> <br /> * Download [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows gnustep NSIS installer ].<br /> ** select copy the binaries.<br /> <br /> <br /> * Download and compile gnustep examples tar ball.<br /> <br /> * &quot;openapp GSTest.app&quot; will bring up a screen with GNUstep interface.<br /> <br /> = GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =<br /> <br /> There are three sub packages <br /> * user : To minimize the footprint of gnustep system on Windows machines.<br /> * developer : include WiX,gcc and package sources.<br /> * gnustep applications : include a broad suite of GNUstep applications.<br /> == Install GNUstep MSI installer ==<br /> * Download the msi from here.<br /> * answer following questions.<br /> * Test the installation.<br /> == Prepare your gnustep win32 development environment ==<br /> === List of depended software ===<br /> * WiX Win32 PMS.<br /> ** candle.exe <br /> &lt;pre&gt;<br /> C:\tmp&gt;candle<br /> Microsoft (R) Windows Installer Xml Compiler version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: candle.exe [-?] [-nologo] [-out outputFile] sourceFile [sourceFile ...]<br /> <br /> <br /> -d&lt;name&gt;=&lt;value&gt; define a parameter for the preprocessor<br /> -p&lt;file&gt; preprocess to a file (or stdout if no file supplied)<br /> -I&lt;dir&gt; add to include search path<br /> -nologo skip printing candle logo information<br /> -out specify output file (default: write to current directory)<br /> -pedantic:&lt;level&gt; pedantic checks (levels: easy, heroic, legendary)<br /> <br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> <br /> ** light.exe<br /> &lt;pre&gt;<br /> C:\tmp&gt;light<br /> Microsoft (R) Windows Installer Xml Linker version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: light.exe [-?] [-b basePath] [-nologo] [-out outputFile] objectFile [o<br /> jectFile ...]<br /> <br /> -ai allow identical rows, identical rows will be treated as a warning<br /> -au (experimental) allow unresolved references, will not create a val<br /> d output<br /> -b base path to locate all files (default: current directory)<br /> -cc path to cache built cabinets (will not be deleted after linking)<br /> <br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> * makefile for nmake.<br /> * gcc win32 compiler from MingW.<br /> <br /> === Checkout gnustep.wxs ===<br /> === overview of gnustep.wxs ===</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4171 2006-12-29T13:24:15Z

<p>Tjyang: /* Prepare your gnustep win32 development environment */</p> <hr /> <div>= Install Windows GNUstep manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = GNUstep .exe installer created by Nullsoft's [http://nsis.sourceforge.net/Main_Page NSIS] =<br /> <br /> == install instruction ==<br /> There are three versions of exe installer for gnustep.<br /> <br /> * Download [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows gnustep NSIS installer ].<br /> ** select copy the binaries.<br /> <br /> <br /> * Download and compile gnustep examples tar ball.<br /> <br /> * &quot;openapp GSTest.app&quot; will bring up a screen with GNUstep interface.<br /> <br /> = GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =<br /> <br /> There are three sub packages <br /> * user : To minimize the footprint of gnustep system on Windows machines.<br /> * developer : include WiX,gcc and package sources.<br /> * gnustep applications : include a broad suite of GNUstep applications.<br /> == Install GNUstep MSI installer ==<br /> * Download the msi from here.<br /> * answer following questions.<br /> * Test the installation.<br /> == Prepare your gnustep win32 development environment ==<br /> === List of depended software ===<br /> * WiX Win32 PMS.<br /> ** candle.exe <br /> &lt;pre&gt;<br /> C:\tmp&gt;candle<br /> Microsoft (R) Windows Installer Xml Compiler version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: candle.exe [-?] [-nologo] [-out outputFile] sourceFile [sourceFile ...]<br /> <br /> <br /> -d&lt;name&gt;=&lt;value&gt; define a parameter for the preprocessor<br /> -p&lt;file&gt; preprocess to a file (or stdout if no file supplied)<br /> -I&lt;dir&gt; add to include search path<br /> -nologo skip printing candle logo information<br /> -out specify output file (default: write to current directory)<br /> -pedantic:&lt;level&gt; pedantic checks (levels: easy, heroic, legendary)<br /> <br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> <br /> ** light.exe<br /> &lt;pre&gt;<br /> C:\tmp&gt;light<br /> Microsoft (R) Windows Installer Xml Linker version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: light.exe [-?] [-b basePath] [-nologo] [-out outputFile] objectFile [o<br /> jectFile ...]<br /> <br /> -ai allow identical rows, identical rows will be treated as a warning<br /> -au (experimental) allow unresolved references, will not create a val<br /> d output<br /> -b base path to locate all files (default: current directory)<br /> -cc path to cache built cabinets (will not be deleted after linking)<br /> <br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> * makefile for nmake.<br /> * gcc win32 compiler from MingW.<br /> <br /> === Checkout gnustep.wxs ===<br /> === overview of gnustep.wxs ===</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4170 2006-12-29T13:23:17Z

<p>Tjyang: /* List of depended software */</p> <hr /> <div>= Install Windows GNUstep manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = GNUstep .exe installer created by Nullsoft's [http://nsis.sourceforge.net/Main_Page NSIS] =<br /> <br /> == install instruction ==<br /> There are three versions of exe installer for gnustep.<br /> <br /> * Download [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows gnustep NSIS installer ].<br /> ** select copy the binaries.<br /> <br /> <br /> * Download and compile gnustep examples tar ball.<br /> <br /> * &quot;openapp GSTest.app&quot; will bring up a screen with GNUstep interface.<br /> <br /> = GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =<br /> <br /> There are three sub packages <br /> * user : To minimize the footprint of gnustep system on Windows machines.<br /> * developer : include WiX,gcc and package sources.<br /> * gnustep applications : include a broad suite of GNUstep applications.<br /> == Install GNUstep MSI installer ==<br /> * Download the msi from here.<br /> * answer following questions.<br /> * Test the installation.<br /> == Prepare your gnustep win32 development environment ==<br /> === List of depended software ===<br /> * WiX Win32 PMS.<br /> ** candle.exe <br /> &lt;pre&gt;<br /> C:\tmp&gt;candle<br /> Microsoft (R) Windows Installer Xml Compiler version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: candle.exe [-?] [-nologo] [-out outputFile] sourceFile [sourceFile ...]<br /> <br /> <br /> -d&lt;name&gt;=&lt;value&gt; define a parameter for the preprocessor<br /> -p&lt;file&gt; preprocess to a file (or stdout if no file supplied)<br /> -I&lt;dir&gt; add to include search path<br /> -nologo skip printing candle logo information<br /> -out specify output file (default: write to current directory)<br /> -pedantic:&lt;level&gt; pedantic checks (levels: easy, heroic, legendary)<br /> <br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> <br /> ** light.exe<br /> &lt;pre&gt;<br /> C:\tmp&gt;light<br /> Microsoft (R) Windows Installer Xml Linker version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: light.exe [-?] [-b basePath] [-nologo] [-out outputFile] objectFile [o<br /> jectFile ...]<br /> <br /> -ai allow identical rows, identical rows will be treated as a warning<br /> -au (experimental) allow unresolved references, will not create a val<br /> d output<br /> -b base path to locate all files (default: current directory)<br /> -cc path to cache built cabinets (will not be deleted after linking)<br /> <br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> * gcc win32 compiler from MingW.<br /> <br /> === Checkout gnustep.wxs ===<br /> === overview of gnustep.wxs ===</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4169 2006-12-29T13:22:59Z

<p>Tjyang: /* List of depended software */</p> <hr /> <div>= Install Windows GNUstep manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = GNUstep .exe installer created by Nullsoft's [http://nsis.sourceforge.net/Main_Page NSIS] =<br /> <br /> == install instruction ==<br /> There are three versions of exe installer for gnustep.<br /> <br /> * Download [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows gnustep NSIS installer ].<br /> ** select copy the binaries.<br /> <br /> <br /> * Download and compile gnustep examples tar ball.<br /> <br /> * &quot;openapp GSTest.app&quot; will bring up a screen with GNUstep interface.<br /> <br /> = GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =<br /> <br /> There are three sub packages <br /> * user : To minimize the footprint of gnustep system on Windows machines.<br /> * developer : include WiX,gcc and package sources.<br /> * gnustep applications : include a broad suite of GNUstep applications.<br /> == Install GNUstep MSI installer ==<br /> * Download the msi from here.<br /> * answer following questions.<br /> * Test the installation.<br /> == Prepare your gnustep win32 development environment ==<br /> === List of depended software ===<br /> * WiX Win32 PMS.<br /> ** candle.exe <br /> &lt;pre&gt;<br /> C:\tmp&gt;candle<br /> Microsoft (R) Windows Installer Xml Compiler version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: candle.exe [-?] [-nologo] [-out outputFile] sourceFile [sourceFile ...]<br /> <br /> <br /> -d&lt;name&gt;=&lt;value&gt; define a parameter for the preprocessor<br /> -p&lt;file&gt; preprocess to a file (or stdout if no file supplied)<br /> -I&lt;dir&gt; add to include search path<br /> -nologo skip printing candle logo information<br /> -out specify output file (default: write to current directory)<br /> -pedantic:&lt;level&gt; pedantic checks (levels: easy, heroic, legendary)<br /> <br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> ** light.exe<br /> &lt;pre&gt;<br /> C:\tmp&gt;light<br /> Microsoft (R) Windows Installer Xml Linker version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: light.exe [-?] [-b basePath] [-nologo] [-out outputFile] objectFile [o<br /> jectFile ...]<br /> <br /> -ai allow identical rows, identical rows will be treated as a warning<br /> -au (experimental) allow unresolved references, will not create a val<br /> d output<br /> -b base path to locate all files (default: current directory)<br /> -cc path to cache built cabinets (will not be deleted after linking)<br /> <br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> * gcc win32 compiler from MingW.<br /> <br /> === Checkout gnustep.wxs ===<br /> === overview of gnustep.wxs ===</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4168 2006-12-29T13:21:40Z

<p>Tjyang: /* GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] */</p> <hr /> <div>= Install Windows GNUstep manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = GNUstep .exe installer created by Nullsoft's [http://nsis.sourceforge.net/Main_Page NSIS] =<br /> <br /> == install instruction ==<br /> There are three versions of exe installer for gnustep.<br /> <br /> * Download [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows gnustep NSIS installer ].<br /> ** select copy the binaries.<br /> <br /> <br /> * Download and compile gnustep examples tar ball.<br /> <br /> * &quot;openapp GSTest.app&quot; will bring up a screen with GNUstep interface.<br /> <br /> = GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =<br /> <br /> There are three sub packages <br /> * user : To minimize the footprint of gnustep system on Windows machines.<br /> * developer : include WiX,gcc and package sources.<br /> * gnustep applications : include a broad suite of GNUstep applications.<br /> == Install GNUstep MSI installer ==<br /> * Download the msi from here.<br /> * answer following questions.<br /> * Test the installation.<br /> == Prepare your gnustep win32 development environment ==<br /> === List of depended software ===<br /> * WiX Win32 PMS.<br /> ** candle.exe <br /> &lt;pre&gt;<br /> C:\tmp&gt;candle<br /> Microsoft (R) Windows Installer Xml Compiler version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: candle.exe [-?] [-nologo] [-out outputFile] sourceFile [sourceFile ...]<br /> <br /> <br /> -d&lt;name&gt;=&lt;value&gt; define a parameter for the preprocessor<br /> -p&lt;file&gt; preprocess to a file (or stdout if no file supplied)<br /> -I&lt;dir&gt; add to include search path<br /> -nologo skip printing candle logo information<br /> -out specify output file (default: write to current directory)<br /> -pedantic:&lt;level&gt; pedantic checks (levels: easy, heroic, legendary)<br /> -ss suppress schema validation of documents (performance boost)<br /> -ust use small table definitions (for backwards compatiblity)<br /> -trace show source trace for errors, warnings, and verbose messages<br /> -ext extension (class, assembly), should extend CompilerExtension<br /> -zs only do validation of documents (no output)<br /> -wx treat warnings as errors<br /> -w&lt;N&gt; set the warning level (0: show all, 3: show none)<br /> -sw suppress all warnings (same as -w3)<br /> -sw&lt;N&gt; suppress warning with specific message ID<br /> -v verbose output (same as -v2)<br /> -v&lt;N&gt; sets the level of verbose output (0: most output, 3: none)<br /> -? this help information<br /> <br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> ** light.exe<br /> &lt;pre&gt;<br /> C:\tmp&gt;light<br /> Microsoft (R) Windows Installer Xml Linker version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: light.exe [-?] [-b basePath] [-nologo] [-out outputFile] objectFile [o<br /> jectFile ...]<br /> <br /> -ai allow identical rows, identical rows will be treated as a warning<br /> -au (experimental) allow unresolved references, will not create a val<br /> d output<br /> -b base path to locate all files (default: current directory)<br /> -cc path to cache built cabinets (will not be deleted after linking)<br /> -ext extension (class, assembly), should extend SchemaExtension or Bin<br /> erExtension<br /> -fv add a 'fileVersion' entry to the MsiAssemblyName table (rarely ne<br /> ded)<br /> -i specify the base output path for uncompressed images (default: -o<br /> t parameter)<br /> -loc read localization string sfrom .wxl file<br /> -nologo skip printing light logo information<br /> -notidy do not delete temporary files (useful for debugging)<br /> -reusecab reuse cabinets from cabinet cache<br /> -out specify output file (default: write to current directory)<br /> -xo output xml instead of MSI format<br /> -pedantic:&lt;level&gt; pedantic checks (levels: easy, heroic, legendary)<br /> -reusecab reuse cabinets from cabinet cache<br /> -sa suppress assemblies: do not get assembly name information for ass<br /> mblies<br /> -sacl suppress resetting ACLs (useful when laying out image to a networ<br /> share)<br /> -sadmin suppress default admin sequence actions<br /> -sadv suppress default adv sequence actions<br /> -sa suppress assemblys: do not get assembly name information for asse<br /> blies<br /> -sf suppress files: do not get any file information (equivalent to -s<br /> and -sh)<br /> -sh suppress file info: do not get hash, version, language, etc<br /> -sl suppress layout<br /> -ss suppress schema validation of documents (performance boost)<br /> -sui suppress default UI sequence actions<br /> -sv suppress intermediate file version mismatch checking<br /> -ts tag sectionId attribute on tuples (ignored if not used with -xo)<br /> -ust use small table definitions (for backwards compatiblity)<br /> -wx treat warnings as errors<br /> -w&lt;N&gt; set the warning level (0: show all, 3: show none)<br /> -sw suppress all warnings (same as -w3)<br /> -sw&lt;N&gt; suppress warning with specific message ID<br /> -v verbose output (same as -v2)<br /> -v&lt;N&gt; sets the level of verbose output (0: most output, 3: none)<br /> -? this help information<br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> * gcc win32 compiler from MingW.<br /> <br /> === Checkout gnustep.wxs ===<br /> === overview of gnustep.wxs ===</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4167 2006-12-29T13:19:57Z

<p>Tjyang: /* List of depended software */</p> <hr /> <div>= Install Windows GNUstep manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = GNUstep .exe installer created by Nullsoft's [http://nsis.sourceforge.net/Main_Page NSIS] =<br /> <br /> == install instruction ==<br /> There are three versions of exe installer for gnustep.<br /> <br /> * Download [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows gnustep NSIS installer ].<br /> ** select copy the binaries.<br /> <br /> <br /> * Download and compile gnustep examples tar ball.<br /> <br /> * &quot;openapp GSTest.app&quot; will bring up a screen with GNUstep interface.<br /> <br /> = GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =<br /> <br /> There are three sub packages <br /> * user : To minimize the footprint of gnustep system on Windows machines.<br /> * developer : include WiX,gcc and package sources.<br /> * gnustep applications : include a broad suite of GNUstep applications.<br /> <br /> == Prepare your gnustep win32 development environment ==<br /> === List of depended software ===<br /> * WiX Win32 PMS.<br /> ** candle.exe <br /> &lt;pre&gt;<br /> C:\tmp&gt;candle<br /> Microsoft (R) Windows Installer Xml Compiler version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: candle.exe [-?] [-nologo] [-out outputFile] sourceFile [sourceFile ...]<br /> <br /> <br /> -d&lt;name&gt;=&lt;value&gt; define a parameter for the preprocessor<br /> -p&lt;file&gt; preprocess to a file (or stdout if no file supplied)<br /> -I&lt;dir&gt; add to include search path<br /> -nologo skip printing candle logo information<br /> -out specify output file (default: write to current directory)<br /> -pedantic:&lt;level&gt; pedantic checks (levels: easy, heroic, legendary)<br /> -ss suppress schema validation of documents (performance boost)<br /> -ust use small table definitions (for backwards compatiblity)<br /> -trace show source trace for errors, warnings, and verbose messages<br /> -ext extension (class, assembly), should extend CompilerExtension<br /> -zs only do validation of documents (no output)<br /> -wx treat warnings as errors<br /> -w&lt;N&gt; set the warning level (0: show all, 3: show none)<br /> -sw suppress all warnings (same as -w3)<br /> -sw&lt;N&gt; suppress warning with specific message ID<br /> -v verbose output (same as -v2)<br /> -v&lt;N&gt; sets the level of verbose output (0: most output, 3: none)<br /> -? this help information<br /> <br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> ** light.exe<br /> &lt;pre&gt;<br /> C:\tmp&gt;light<br /> Microsoft (R) Windows Installer Xml Linker version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: light.exe [-?] [-b basePath] [-nologo] [-out outputFile] objectFile [o<br /> jectFile ...]<br /> <br /> -ai allow identical rows, identical rows will be treated as a warning<br /> -au (experimental) allow unresolved references, will not create a val<br /> d output<br /> -b base path to locate all files (default: current directory)<br /> -cc path to cache built cabinets (will not be deleted after linking)<br /> -ext extension (class, assembly), should extend SchemaExtension or Bin<br /> erExtension<br /> -fv add a 'fileVersion' entry to the MsiAssemblyName table (rarely ne<br /> ded)<br /> -i specify the base output path for uncompressed images (default: -o<br /> t parameter)<br /> -loc read localization string sfrom .wxl file<br /> -nologo skip printing light logo information<br /> -notidy do not delete temporary files (useful for debugging)<br /> -reusecab reuse cabinets from cabinet cache<br /> -out specify output file (default: write to current directory)<br /> -xo output xml instead of MSI format<br /> -pedantic:&lt;level&gt; pedantic checks (levels: easy, heroic, legendary)<br /> -reusecab reuse cabinets from cabinet cache<br /> -sa suppress assemblies: do not get assembly name information for ass<br /> mblies<br /> -sacl suppress resetting ACLs (useful when laying out image to a networ<br /> share)<br /> -sadmin suppress default admin sequence actions<br /> -sadv suppress default adv sequence actions<br /> -sa suppress assemblys: do not get assembly name information for asse<br /> blies<br /> -sf suppress files: do not get any file information (equivalent to -s<br /> and -sh)<br /> -sh suppress file info: do not get hash, version, language, etc<br /> -sl suppress layout<br /> -ss suppress schema validation of documents (performance boost)<br /> -sui suppress default UI sequence actions<br /> -sv suppress intermediate file version mismatch checking<br /> -ts tag sectionId attribute on tuples (ignored if not used with -xo)<br /> -ust use small table definitions (for backwards compatiblity)<br /> -wx treat warnings as errors<br /> -w&lt;N&gt; set the warning level (0: show all, 3: show none)<br /> -sw suppress all warnings (same as -w3)<br /> -sw&lt;N&gt; suppress warning with specific message ID<br /> -v verbose output (same as -v2)<br /> -v&lt;N&gt; sets the level of verbose output (0: most output, 3: none)<br /> -? this help information<br /> &lt;snip&gt;<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> * gcc win32 compiler from MingW.<br /> <br /> === Checkout gnustep.wxs ===<br /> === overview of gnustep.wxs ===</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4166 2006-12-29T13:18:57Z

<p>Tjyang: /* = List of depended software */</p> <hr /> <div>= Install Windows GNUstep manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = GNUstep .exe installer created by Nullsoft's [http://nsis.sourceforge.net/Main_Page NSIS] =<br /> <br /> == install instruction ==<br /> There are three versions of exe installer for gnustep.<br /> <br /> * Download [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows gnustep NSIS installer ].<br /> ** select copy the binaries.<br /> <br /> <br /> * Download and compile gnustep examples tar ball.<br /> <br /> * &quot;openapp GSTest.app&quot; will bring up a screen with GNUstep interface.<br /> <br /> = GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =<br /> <br /> There are three sub packages <br /> * user : To minimize the footprint of gnustep system on Windows machines.<br /> * developer : include WiX,gcc and package sources.<br /> * gnustep applications : include a broad suite of GNUstep applications.<br /> <br /> == Prepare your gnustep win32 development environment ==<br /> === List of depended software ===<br /> * WiX Win32 PMS.<br /> ** candle.exe <br /> &lt;pre&gt;<br /> C:\tmp&gt;candle<br /> Microsoft (R) Windows Installer Xml Compiler version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: candle.exe [-?] [-nologo] [-out outputFile] sourceFile [sourceFile ...]<br /> <br /> <br /> -d&lt;name&gt;=&lt;value&gt; define a parameter for the preprocessor<br /> -p&lt;file&gt; preprocess to a file (or stdout if no file supplied)<br /> -I&lt;dir&gt; add to include search path<br /> -nologo skip printing candle logo information<br /> -out specify output file (default: write to current directory)<br /> -pedantic:&lt;level&gt; pedantic checks (levels: easy, heroic, legendary)<br /> -ss suppress schema validation of documents (performance boost)<br /> -ust use small table definitions (for backwards compatiblity)<br /> -trace show source trace for errors, warnings, and verbose messages<br /> -ext extension (class, assembly), should extend CompilerExtension<br /> -zs only do validation of documents (no output)<br /> -wx treat warnings as errors<br /> -w&lt;N&gt; set the warning level (0: show all, 3: show none)<br /> -sw suppress all warnings (same as -w3)<br /> -sw&lt;N&gt; suppress warning with specific message ID<br /> -v verbose output (same as -v2)<br /> -v&lt;N&gt; sets the level of verbose output (0: most output, 3: none)<br /> -? this help information<br /> <br /> Common extensions:<br /> .wxs - Windows installer Xml Source file<br /> .wxi - Windows installer Xml Include file<br /> .wxl - Windows installer Xml Localization file<br /> .wixobj - Windows installer Xml Object file (in XML format)<br /> .wixlib - Windows installer Xml Library file (in XML format)<br /> .wixout - Windows installer Xml Output file (in XML format)<br /> <br /> .msm - Windows installer Merge Module<br /> .msi - Windows installer Product Database<br /> .mst - Windows installer Transform<br /> .pcp - Windows installer Patch Creation Package<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> ** light.exe<br /> &lt;pre&gt;<br /> C:\tmp&gt;light<br /> Microsoft (R) Windows Installer Xml Linker version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: light.exe [-?] [-b basePath] [-nologo] [-out outputFile] objectFile [o<br /> jectFile ...]<br /> <br /> -ai allow identical rows, identical rows will be treated as a warning<br /> -au (experimental) allow unresolved references, will not create a val<br /> d output<br /> -b base path to locate all files (default: current directory)<br /> -cc path to cache built cabinets (will not be deleted after linking)<br /> -ext extension (class, assembly), should extend SchemaExtension or Bin<br /> erExtension<br /> -fv add a 'fileVersion' entry to the MsiAssemblyName table (rarely ne<br /> ded)<br /> -i specify the base output path for uncompressed images (default: -o<br /> t parameter)<br /> -loc read localization string sfrom .wxl file<br /> -nologo skip printing light logo information<br /> -notidy do not delete temporary files (useful for debugging)<br /> -reusecab reuse cabinets from cabinet cache<br /> -out specify output file (default: write to current directory)<br /> -xo output xml instead of MSI format<br /> -pedantic:&lt;level&gt; pedantic checks (levels: easy, heroic, legendary)<br /> -reusecab reuse cabinets from cabinet cache<br /> -sa suppress assemblies: do not get assembly name information for ass<br /> mblies<br /> -sacl suppress resetting ACLs (useful when laying out image to a networ<br /> share)<br /> -sadmin suppress default admin sequence actions<br /> -sadv suppress default adv sequence actions<br /> -sa suppress assemblys: do not get assembly name information for asse<br /> blies<br /> -sf suppress files: do not get any file information (equivalent to -s<br /> and -sh)<br /> -sh suppress file info: do not get hash, version, language, etc<br /> -sl suppress layout<br /> -ss suppress schema validation of documents (performance boost)<br /> -sui suppress default UI sequence actions<br /> -sv suppress intermediate file version mismatch checking<br /> -ts tag sectionId attribute on tuples (ignored if not used with -xo)<br /> -ust use small table definitions (for backwards compatiblity)<br /> -wx treat warnings as errors<br /> -w&lt;N&gt; set the warning level (0: show all, 3: show none)<br /> -sw suppress all warnings (same as -w3)<br /> -sw&lt;N&gt; suppress warning with specific message ID<br /> -v verbose output (same as -v2)<br /> -v&lt;N&gt; sets the level of verbose output (0: most output, 3: none)<br /> -? this help information<br /> <br /> Environment variables:<br /> WIX_TEMP overrides the temporary directory used for cab creation, msm expl<br /> ding, ...<br /> <br /> Common extensions:<br /> .wxs - Windows installer Xml Source file<br /> .wxi - Windows installer Xml Include file<br /> .wxl - Windows installer Xml Localization file<br /> .wixobj - Windows installer Xml Object file (in XML format)<br /> .wixlib - Windows installer Xml Library file (in XML format)<br /> .wixout - Windows installer Xml Output file (in XML format)<br /> <br /> .msm - Windows installer Merge Module<br /> .msi - Windows installer Product Database<br /> .mst - Windows installer Transform<br /> .pcp - Windows installer Patch Creation Package<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> * gcc win32 compiler from MingW.<br /> <br /> === Checkout gnustep.wxs ===<br /> === overview of gnustep.wxs ===</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4165 2006-12-29T13:18:41Z

<p>Tjyang: /* Overview of gnustep WiX package Source */</p> <hr /> <div>= Install Windows GNUstep manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = GNUstep .exe installer created by Nullsoft's [http://nsis.sourceforge.net/Main_Page NSIS] =<br /> <br /> == install instruction ==<br /> There are three versions of exe installer for gnustep.<br /> <br /> * Download [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows gnustep NSIS installer ].<br /> ** select copy the binaries.<br /> <br /> <br /> * Download and compile gnustep examples tar ball.<br /> <br /> * &quot;openapp GSTest.app&quot; will bring up a screen with GNUstep interface.<br /> <br /> = GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =<br /> <br /> There are three sub packages <br /> * user : To minimize the footprint of gnustep system on Windows machines.<br /> * developer : include WiX,gcc and package sources.<br /> * gnustep applications : include a broad suite of GNUstep applications.<br /> <br /> == Prepare your gnustep win32 development environment ==<br /> === List of depended software ==<br /> * WiX Win32 PMS.<br /> ** candle.exe <br /> &lt;pre&gt;<br /> C:\tmp&gt;candle<br /> Microsoft (R) Windows Installer Xml Compiler version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: candle.exe [-?] [-nologo] [-out outputFile] sourceFile [sourceFile ...]<br /> <br /> <br /> -d&lt;name&gt;=&lt;value&gt; define a parameter for the preprocessor<br /> -p&lt;file&gt; preprocess to a file (or stdout if no file supplied)<br /> -I&lt;dir&gt; add to include search path<br /> -nologo skip printing candle logo information<br /> -out specify output file (default: write to current directory)<br /> -pedantic:&lt;level&gt; pedantic checks (levels: easy, heroic, legendary)<br /> -ss suppress schema validation of documents (performance boost)<br /> -ust use small table definitions (for backwards compatiblity)<br /> -trace show source trace for errors, warnings, and verbose messages<br /> -ext extension (class, assembly), should extend CompilerExtension<br /> -zs only do validation of documents (no output)<br /> -wx treat warnings as errors<br /> -w&lt;N&gt; set the warning level (0: show all, 3: show none)<br /> -sw suppress all warnings (same as -w3)<br /> -sw&lt;N&gt; suppress warning with specific message ID<br /> -v verbose output (same as -v2)<br /> -v&lt;N&gt; sets the level of verbose output (0: most output, 3: none)<br /> -? this help information<br /> <br /> Common extensions:<br /> .wxs - Windows installer Xml Source file<br /> .wxi - Windows installer Xml Include file<br /> .wxl - Windows installer Xml Localization file<br /> .wixobj - Windows installer Xml Object file (in XML format)<br /> .wixlib - Windows installer Xml Library file (in XML format)<br /> .wixout - Windows installer Xml Output file (in XML format)<br /> <br /> .msm - Windows installer Merge Module<br /> .msi - Windows installer Product Database<br /> .mst - Windows installer Transform<br /> .pcp - Windows installer Patch Creation Package<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> ** light.exe<br /> &lt;pre&gt;<br /> C:\tmp&gt;light<br /> Microsoft (R) Windows Installer Xml Linker version 2.0.4221.0<br /> Copyright (C) Microsoft Corporation 2003. All rights reserved.<br /> <br /> usage: light.exe [-?] [-b basePath] [-nologo] [-out outputFile] objectFile [o<br /> jectFile ...]<br /> <br /> -ai allow identical rows, identical rows will be treated as a warning<br /> -au (experimental) allow unresolved references, will not create a val<br /> d output<br /> -b base path to locate all files (default: current directory)<br /> -cc path to cache built cabinets (will not be deleted after linking)<br /> -ext extension (class, assembly), should extend SchemaExtension or Bin<br /> erExtension<br /> -fv add a 'fileVersion' entry to the MsiAssemblyName table (rarely ne<br /> ded)<br /> -i specify the base output path for uncompressed images (default: -o<br /> t parameter)<br /> -loc read localization string sfrom .wxl file<br /> -nologo skip printing light logo information<br /> -notidy do not delete temporary files (useful for debugging)<br /> -reusecab reuse cabinets from cabinet cache<br /> -out specify output file (default: write to current directory)<br /> -xo output xml instead of MSI format<br /> -pedantic:&lt;level&gt; pedantic checks (levels: easy, heroic, legendary)<br /> -reusecab reuse cabinets from cabinet cache<br /> -sa suppress assemblies: do not get assembly name information for ass<br /> mblies<br /> -sacl suppress resetting ACLs (useful when laying out image to a networ<br /> share)<br /> -sadmin suppress default admin sequence actions<br /> -sadv suppress default adv sequence actions<br /> -sa suppress assemblys: do not get assembly name information for asse<br /> blies<br /> -sf suppress files: do not get any file information (equivalent to -s<br /> and -sh)<br /> -sh suppress file info: do not get hash, version, language, etc<br /> -sl suppress layout<br /> -ss suppress schema validation of documents (performance boost)<br /> -sui suppress default UI sequence actions<br /> -sv suppress intermediate file version mismatch checking<br /> -ts tag sectionId attribute on tuples (ignored if not used with -xo)<br /> -ust use small table definitions (for backwards compatiblity)<br /> -wx treat warnings as errors<br /> -w&lt;N&gt; set the warning level (0: show all, 3: show none)<br /> -sw suppress all warnings (same as -w3)<br /> -sw&lt;N&gt; suppress warning with specific message ID<br /> -v verbose output (same as -v2)<br /> -v&lt;N&gt; sets the level of verbose output (0: most output, 3: none)<br /> -? this help information<br /> <br /> Environment variables:<br /> WIX_TEMP overrides the temporary directory used for cab creation, msm expl<br /> ding, ...<br /> <br /> Common extensions:<br /> .wxs - Windows installer Xml Source file<br /> .wxi - Windows installer Xml Include file<br /> .wxl - Windows installer Xml Localization file<br /> .wixobj - Windows installer Xml Object file (in XML format)<br /> .wixlib - Windows installer Xml Library file (in XML format)<br /> .wixout - Windows installer Xml Output file (in XML format)<br /> <br /> .msm - Windows installer Merge Module<br /> .msi - Windows installer Product Database<br /> .mst - Windows installer Transform<br /> .pcp - Windows installer Patch Creation Package<br /> <br /> For more information see: http://wix.sourceforge.net<br /> <br /> C:\tmp&gt;<br /> &lt;/pre&gt;<br /> * gcc win32 compiler from MingW.<br /> <br /> === Checkout gnustep.wxs ===<br /> === overview of gnustep.wxs ===</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4164 2006-12-29T13:04:54Z

<p>Tjyang: /* GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] */</p> <hr /> <div>= Install Windows GNUstep manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = GNUstep .exe installer created by Nullsoft's [http://nsis.sourceforge.net/Main_Page NSIS] =<br /> <br /> == install instruction ==<br /> There are three versions of exe installer for gnustep.<br /> <br /> * Download [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows gnustep NSIS installer ].<br /> ** select copy the binaries.<br /> <br /> <br /> * Download and compile gnustep examples tar ball.<br /> <br /> * &quot;openapp GSTest.app&quot; will bring up a screen with GNUstep interface.<br /> <br /> = GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =<br /> <br /> There are three sub packages <br /> * user : To minimize the footprint of gnustep system on Windows machines.<br /> * developer : include WiX,gcc and package sources.<br /> * gnustep applications : include a broad suite of GNUstep applications.<br /> <br /> == Overview of gnustep WiX package Source ==<br /> <br /> <br /> === gnustep.wxs ===</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4163 2006-12-29T13:00:54Z

<p>Tjyang: /* install instruction */</p> <hr /> <div>= Install Windows GNUstep manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = GNUstep .exe installer created by Nullsoft's [http://nsis.sourceforge.net/Main_Page NSIS] =<br /> <br /> == install instruction ==<br /> There are three versions of exe installer for gnustep.<br /> <br /> * Download [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows gnustep NSIS installer ].<br /> ** select copy the binaries.<br /> <br /> <br /> * Download and compile gnustep examples tar ball.<br /> <br /> * &quot;openapp GSTest.app&quot; will bring up a screen with GNUstep interface.<br /> <br /> = GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =<br /> == Overview of gnustep WiX package Source ==<br /> <br /> <br /> === gnustep.wxs ===</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4162 2006-12-29T12:57:50Z

<p>Tjyang: /* install instruction */</p> <hr /> <div>= Install Windows GNUstep manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = GNUstep .exe installer created by Nullsoft's [http://nsis.sourceforge.net/Main_Page NSIS] =<br /> <br /> == install instruction ==<br /> <br /> * Download [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows gnustep NSIS installer ].<br /> ** select copy the binaries.<br /> <br /> = GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =<br /> == Overview of gnustep WiX package Source ==<br /> <br /> <br /> === gnustep.wxs ===</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4161 2006-12-29T12:52:14Z

<p>Tjyang: /* Install Windows GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] */</p> <hr /> <div>= Install Windows GNUstep manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = GNUstep .exe installer created by Nullsoft's [http://nsis.sourceforge.net/Main_Page NSIS] =<br /> <br /> == install instruction ==<br /> <br /> * Download [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows gnustep NSIS installer ].<br /> <br /> = GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =<br /> == Overview of gnustep WiX package Source ==<br /> <br /> <br /> === gnustep.wxs ===</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4160 2006-12-29T12:51:43Z

<p>Tjyang: /* Install Windows GNUstep .exe installer created by Nullsoft's NSIS */</p> <hr /> <div>= Install Windows GNUstep manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = GNUstep .exe installer created by Nullsoft's [http://nsis.sourceforge.net/Main_Page NSIS] =<br /> <br /> == install instruction ==<br /> <br /> * Download [ftp://ftp.gnustep.org/pub/gnustep/binaries/windows gnustep NSIS installer ].<br /> <br /> = Install Windows GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =<br /> == Overview of gnustep WiX package Source ==<br /> <br /> <br /> === gnustep.wxs ===</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4159 2006-12-29T12:45:32Z

<p>Tjyang: /* Install Windows GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] */</p> <hr /> <div>= Install Windows GNUstep manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = Install Windows GNUstep .exe installer created by Nullsoft's NSIS =<br /> <br /> = Install Windows GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =<br /> == Overview of gnustep WiX package Source ==<br /> <br /> <br /> === gnustep.wxs ===</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4158 2006-12-29T12:41:16Z

<p>Tjyang: </p> <hr /> <div>= Install Windows GNUstep manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = Install Windows GNUstep .exe installer created by Nullsoft's NSIS =<br /> <br /> = Install Windows GNUstep MSI installer created by [http://wix.sourceforge.net/ WiX] =</div>

Tjyang https://mediawiki.gnustep.org/index.php?title=Installation_on_Windows&diff=4157 2006-12-29T12:40:17Z

<p>Tjyang: </p> <hr /> <div>= Install Windows GNUstep manually =<br /> <br /> == Install MinGW ==<br /> Download MinGW-3.2.0-rc-3 or later from http://sourceforge.net/projects/mingw Install it into<br /> <br /> C:/xxx/msys/1.0/mingw<br /> <br /> (where /xxx/ is the top-level path you want to use, I use Nicola/GNUstep so I install it into C:/Nicola/GNUstep/msys/1.0/mingw) (earlier versions of MinGW won't work)<br /> <br /> == Install msys ==<br /> <br /> Download MSYS-1.0.10 or later from the same site. Install it into C:/xxx/msys/1.0<br /> The postinstall script should ask you for the mingw location, then detect it and be happy that it's there and all is setup properly.<br /> <br /> == Install msys developer toolkit ==<br /> <br /> Download msysDTK-1.0.1 or later from the same site. Install it into<br /> <br /> C:/xxx/msys/1.0<br /> <br /> Now your MSYS/MinGW system should be setup! Go around and make sure you know how to use the Unix-like shell. Log into it and work in it.<br /> <br /> == Download gnustep using cvs ==<br /> <br /> In windows, go to <br /> Start -&gt; All Programs -&gt; mingw -&gt; MSYS -&gt;Msys<br /> The MINGW32 window appears.<br /> <br /> Type the following:<br /> mkdir install<br /> cd install<br /> export CVS_RSH=&quot;ssh&quot;<br /> cvs -z3 -d:ext:anoncvs@savanah.gnu.org:/cvsroot/gnustep co gnustep<br /> <br /> The following message appears:<br /> The authenticity of host 'savanah.gnu.org (199.232.41.3)' can't be established.<br /> RSA key fingerprint is 80:5a:b0:0c:ec:93:66:29:49:7e:04:2b:fd:ba:2c:d5.<br /> Are you sure you want to continue connecting (yes/no)? <br /> <br /> Type the following:<br /> yes<br /> <br /> The latest and greatest gnustep library will download into your home directory/installs/gnustep.<br /> It took about 10 minutes with a cable modem connection.<br /> <br /> == Install GNUstep make ==<br /> <br /> cd gnustep/core/make<br /> ./configure --prefix=/C/xxx/GNUstep<br /> make<br /> make install<br /> <br /> == Setup your GNUstep environment ==<br /> <br /> (you will need to do the same every time you start up your MSYS shell to do development)<br /> <br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> Also, set HOMEPATH, HOMEDRIVE and HOME ... add the following lines to your ~/.profile:<br /> <br /> export HOMEDRIVE=C:<br /> export HOMEPATH=/home/Nicola<br /> export HOME=/C/xxx/msys/1.0/home/Nicola<br /> . /C/xxx/GNUstep/System/Library/Makefiles/GNUstep.sh<br /> <br /> (obviously replacing 'Nicola' with your Login name) (not sure if this setting of HOMEDRIVE etc is really required, will investigate)<br /> <br /> == Install the ObjC runtime ==<br /> <br /> Actually, recent versions of gcc (3.2+) have a working libobjc on Windows. Nevertheless this step is necessary (at least on Windows 2000) unless you want some strange errors concerning NSAutoreleasePool etc.<br /> <br /> First make sure to delete the old libobjc files<br /> <br /> find /C/xxx/GNUstep/ -iname &quot;libobjc*&quot; -exec rm -i {} \;<br /> <br /> Then cd to dev-libs/libobjc in your cvs checkout directory and install it. <br /> cd ~/install/gnustep/dev-libs/libobjc <br /> make<br /> make install<br /> <br /> == Reinstall GNUstep make (with ObjC this time) ==<br /> <br /> go in core/make and reconfigure/recompile again so that gnustep-objc is detected:<br /> cd ~/install/gnustep/core/make<br /> make distclean<br /> ./configure<br /> make <br /> make install<br /> <br /> gnustep-make should have detected your custom libobjc.<br /> <br /> == Install ffcall ==<br /> <br /> Download ffcall from the GNUstep website into c:/xxx/msys/1.0/home/Nicola/install<br /> or from here: ftp://ftp.santafe.edu/pub/gnu/ffcall-1.10.tar.gz,<br /> and type:<br /> <br /> cd ~/install<br /> tar -zxvf ffcall-1.10.tar.gz<br /> cd ffcall-1.10<br /> ./configure --prefix=$GNUSTEP_SYSTEM_ROOT<br /> A windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A second windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> A third windows prompt will appear stating that conftest.exe has encountered a problem and needs to close.<br /> <br /> Click the [Don't Send] button.<br /> <br /> After much output, the following will be displayed:<br /> <br /> configure: creating ./config.status<br /> config.status: creating Makefile<br /> config.status: creating config.h<br /> <br /> Type the following:<br /> <br /> make<br /> make install<br /> <br /> Note: The configure script of ffcall-1.10 is broken for Windows 2000. You have to apply a patch: http://lists.gnu.org/archive/html/discuss-gnustep/2005-03/msg00258.html<br /> <br /> <br /> Alternatively, a zip containing a precompiled copy of ffcall-1.9 is availabe here: ftp://ftp.gnustep.org/pub/gnustep/binaries/windows/mingw-libs/ffcall-1.9-gnustep.zip<br /> <br /> Unzip it into $GNUSTEP_SYSTEM_ROOT/Library.<br /> <br /> == Install additional libs ==<br /> <br /> Download the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=73290 Download libintl]<br /> <br /> libintl-0.11.5-2-bin.zip<br /> libintl-0.11.5-2-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=17090 Download libiconv]<br /> <br /> libiconv-1.8.1-bin.zip <br /> libiconv-1.8.1-lib.zip <br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16861 Download zlib]<br /> <br /> zlib-1.2.2-bin.zip<br /> zlib-1.2.2-lib.zip<br /> <br /> from http://gnuwin32.sourceforge.net, and install them. To install them, simply unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install XML support ==<br /> <br /> You will have to make some changes to libiconv for libxml to work properly.<br /> <br /> cd /mingw/lib<br /> mkdir backup-libiconv<br /> mv libiconv.la backup-libiconv<br /> mv libiconv.lib backup-libiconv<br /> dlltool -D libiconv-2.dll -C -l libiconvlib --export-all-symbols -A ../bin/libiconv-2.dll<br /> <br /> If there are no errors:<br /> <br /> rm -r backup-libiconv<br /> <br /> I had to compile libiconv from source for this to work (the binaries didn't work with my computer for some reason, and I'm not sure if it normally works.)<br /> <br /> Download the latest version of libxml from [[ftp://xmlsoft.org/libxml2/]].<br /> <br /> cd libxml2-...<br /> vim include/libxml/xmlexports.h<br /> <br /> There is a chunk of code in this file you will have to change.<br /> <br /> Search for:<br /> <br /> Windows platform with GNU compiler<br /> <br /> in the code. Replace the code below it up to the comment about Cygwin:<br /> <br /> #if defined(_WIN32) &amp;&amp; defined(__MINGW32__)<br /> #undef XMLPUBFUN<br /> #undef XMLPUBVAR<br /> #undef XMLCALL<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBFUN __declspec(dllexport)<br /> #define XMLPUBVAR __declspec(dllexport) extern<br /> #else<br /> #define XMLPUBFUN<br /> #if !defined(LIBXML_STATIC)<br /> #define XMLPUBVAR __declspec(dllimport) extern<br /> #else<br /> #define XMLPUBVAR extern<br /> #endif<br /> #endif<br /> #define XMLCALL __cdecl<br /> #if !defined _REENTRANT<br /> #define _REENTRANT<br /> #endif<br /> #endif<br /> <br /> Save the file, then quit. Then compile normally.<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> I never installed to the end with this method (halfway through I just decided to use the installer) but it worked well for me.<br /> <br /> == Install GNUstep base ==<br /> <br /> go in gnustep-base, and type <br /> <br /> cd ~/install/gnustep/core/base<br /> ./configure<br /> make<br /> make install<br /> <br /> If you didn't install libxml,<br /> <br /> ./configure --disable-xml<br /> make<br /> make install<br /> <br /> == Install additional GUI libs ==<br /> <br /> for the gui, download and install the following packages:<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16348&amp;release_id=218220 Download jpeg]<br /> <br /> jpeg-6b-3-bin.zip<br /> jpeg-6b-3-dep.zip<br /> jpeg-6b-3-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16351 Download tiff]<br /> <br /> tiff-3.7.1-bin.zip<br /> tiff-3.7.1-dep.zip<br /> tiff-3.7.1-lib.zip<br /> <br /> [http://sourceforge.net/project/showfiles.php?group_id=23617&amp;package_id=16183 Download libpng]<br /> <br /> libpng-1.2.8-bin.zip<br /> libpng-1.2.8-dep.zip<br /> libpng-1.2.8-lib.zip<br /> <br /> The process is always the same: download the zip file from the gnuwin32 website, then unzip them into<br /> <br /> /C/xxx/msys/1.0/mingw.<br /> <br /> == Install GNUstep gui ==<br /> <br /> Type the following:<br /> cd ~/install/gnustep/core/gui<br /> ./configure<br /> make<br /> make install<br /> <br /> == Install GNUstep back ==<br /> <br /> go in back, and type:<br /> <br /> ./configure<br /> make<br /> make install<br /> <br /> == Check the installation ==<br /> <br /> go in a simple gui application (examples/gui a very good starting point), compile and run it. :-)<br /> <br /> ''based on a mail from Nicola Pero''<br /> <br /> = Install Windows GNUstep installer created by Nullsoft's NSIS =<br /> <br /> = Install Windows GNUstep installer created by [http://wix.sourceforge.net/ WiX] =</div>

Tjyang