Re: [Gimp-developer] Raphael's edits, was Re: test this howto now
Hi Carol, Carol Spears [EMAIL PROTECTED] writes: but while all of these different shell commands are being added to the how-to, maybe we should make a how to compile the gimp tar-ball for people who are having problems with their distributions GIMP or supporting libraries. ack. The Compile The GIMP from CVS HOWTO should refer to the Compile The GIMP from source HOWTO and focus on the possible pitfalls that compiling from CVS adds (cvs, aclocal, autoconf, automake). Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Raphael's edits, was Re: test this howto now
A good Compiling the GIMP from a Tarball HOW-TO seems like a really good idea. I think this outline covers the main points, but certainly could use some rearranging. I hereby offer it up for tweaks and adjustments. How to Compile GIMP from a Tarball: a tentative outline 1. Introduction 1.1 What's a Tarball? 1.2 Why do I want to compile GIMP? 2. Getting the Tarball 2.1 Where's the briar patch? (Where to put the gimp-x.y.tgz file) 2.2 Saving the source (source directory tree) 3. Do I have the right libraries? 3.1 List of required stuff here (with how to get it). This is starting to look recursive, no? 4. ./configure and what it means. 4.1 What's this --prefix= that they keep yammering about? 4.2 Differences between /usr and /usr/local, and why some stuff goes in one place and some stuff goes in the other. 5. Why a new GIMP won't play well with an old GIMP and what to do about it. 5.1 Library version conflicts 5.2 Include paths 5.3 Library paths 5.4 ldconfig, LD_LIBRARY_PATH, and other arcana 5.5 Removing an old version of GIMP - how do I do this? 6. Compiling on various systems: /* Maybe this should come much earlier */ 6.1 Linux and its flavors 6.1.1 Red Hat 6.1.2 Debian 6.1.3 Mandrake 6.1.4 Slackware 6.1.5 etc, etc, ad lib. 6.2 Solaris 6.3 HP-UX 6.4 Other Unices 6.5 Windows 6.6 Mac? 7. Problems and troubleshooting We need to collect at least the most common problems here and provide solutions. Comments welcome, -- --Jeff Jeff Trefftzs [EMAIL PROTECTED] http://www.tcsn.net/trefftzsHome Page http://gug.sunsite.dk/gallery.php?artist=68 Gimp Gallery http://trefftzs.topcities.com/home.html Photo galleries ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Raphael's edits, was Re: test this howto now
On Mon, Jan 21, 2002 at 12:16:44PM -0800, Jeff Trefftzs wrote: A good Compiling the GIMP from a Tarball HOW-TO seems like a really good idea. I think this outline covers the main points, but certainly could use some rearranging. I hereby offer it up for tweaks and adjustments. This may be useful, but is meant as a followup to the posts about documenting building from CVS. In the gimp-print source, there is a file `doc/README.maintaining' that describes how to use the autotools to build from CVS. It covers how to set up a checked-out CVS (or tarball) tree, and use configure (but that's documented fully in README). It also goes into how all the autotools work together, and how to set up the build scripts manually, or with autogen.sh automatically. Additionally, it describes briefly how to hack configure.in and Makefile.am's. I lost the message about documenting building from CVS, but you might find parts of this useful (there's little point in writing the same thing twice). Some parts are specific to gimp-print, but you can eaily cut them out or modify them. I spotted a couple of typos just now, and I also have an updated copy for autoconf 2.52 and automake 1.5. See: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/gimp-print/print/doc/README.maintaining?rev=1.8content-type=text/vnd.viewcvs-markup or the source. Regards, Roger -- Roger Leigh ** Registration Number: 151826, http://counter.li.org ** Need Epson Stylus Utilities? http://gimp-print.sourceforge.net/ GPG Public Key: 0x25BFB848 available on public keyservers msg01799/pgp0.pgp Description: PGP signature
Re: [Gimp-developer] Raphael's edits, was Re: test this howto now
On Mon, Jan 21, 2002 at 10:12:55PM +0100, Sven Neumann wrote: Hi, Roger Leigh [EMAIL PROTECTED] writes: In the gimp-print source, there is a file `doc/README.maintaining' that describes how to use the autotools to build from CVS. It covers how to set up a checked-out CVS (or tarball) tree, and use configure (but that's documented fully in README). It also goes into how all the autotools work together, and how to set up the build scripts manually, or with autogen.sh automatically. Additionally, it describes briefly how to hack configure.in and Makefile.am's. this file is traditionally called HACKING. Is this documented anywhere? I can't see anything about this in the GNU Coding Standards. Thanks, Roger -- Roger Leigh ** Registration Number: 151826, http://counter.li.org ** Need Epson Stylus Utilities? http://gimp-print.sourceforge.net/ GPG Public Key: 0x25BFB848 available on public keyservers msg01803/pgp0.pgp Description: PGP signature
