Re: [Gimp-developer] dependancies
I just wrote up a page listing the packages I installed to build various versions of the gimp on my Redhat and Debian machines (in addition to whatever I previously had installed). It's mostly a set of notes to myself to make it easier in case I want to build on other machines, but I thought making it public might make life easier for other people who were getting started building the gimp. http://shallowsky.com/gimpbuild.html Of course, this doesn't address the issue of where Phil should get these packages for Solaris, but maybe having a list of package names will make it a little easier to do searches for the packages. The list for the CVS tip is the list of what got me through configure. I'm hitting the same anon cvs problems that others have mentioned, resulting in build errors because I don't have the most current versions of some files (for instance, gimpunits.c seems to be out of date, and gimplist.[ch] are each one rev behind where they should be). Fortunately the 1.3.7 tarball builds fine, so the CVS problem isn't a big problem for me. Phil, have you tried building a tarball rather than CVS? You might have an easier time of it. ...Akkana ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
RE: [Gimp-developer] Your message to Gimp-announce awaits moderatorapproval
Hi, I received an email about my message being held for the moderator, I did not know I sent one. If you could please forward it back to me, maybe I can determine how you got it. I'm running a Mandrake Linux box with Evolution 1.0.2 as my mail client. I want to determine if it is mailing things on it's own. Here is your messages header: Return-path: <[EMAIL PROTECTED]> Envelope-to: [EMAIL PROTECTED] Delivery-date: Fri, 07 Jun 2002 13:18:32 -0600 Received: from lists.xcf.berkeley.edu ([128.32.247.242]) by mail.trygve.com with esmtp (Exim 3.34 #1) id 17GPFo-0004VY-00 for [EMAIL PROTECTED]; Fri, 07 Jun 2002 13:18:32 -0600 Received: from lists.XCF.Berkeley.EDU (lists.XCF.Berkeley.EDU [127.0.0.1]) by lists.XCF.Berkeley.EDU (Postfix) with ESMTP id 233D71F127; Fri, 7 Jun 2002 12:18:14 -0700 (PDT) Delivered-To: [EMAIL PROTECTED] Received: from scam.xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.247.241]) by lists.XCF.Berkeley.EDU (Postfix) with ESMTP id 2FE621F04D for <[EMAIL PROTECTED]>; Fri, 7 Jun 2002 12:17:03 -0700 (PDT) Received: by scam.xcf.berkeley.edu (Postfix) id F1BA43BC67; Fri, 7 Jun 2002 11:16:27 -0700 (PDT) Delivered-To: [EMAIL PROTECTED] Received: from lists.XCF.Berkeley.EDU (lists.XCF.Berkeley.EDU [128.32.247.242]) by scam.xcf.berkeley.edu (Postfix) with ESMTP id E6EBE3BC64 for <[EMAIL PROTECTED]>; Fri, 7 Jun 2002 11:16:27 -0700 (PDT) Received: from lists.XCF.Berkeley.EDU (lists.XCF.Berkeley.EDU [127.0.0.1]) by lists.XCF.Berkeley.EDU (Postfix) with ESMTP id CB2D81F122 for <[EMAIL PROTECTED]>; Fri, 7 Jun 2002 12:17:02 -0700 (PDT) Thanks, Art Hughes ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies
On Fri, 7 Jun 2002, Tor Lillqvist wrote: > Philip Brown writes: > > You did not mention, however, why pkgconfig was suddenly added to > > gimp1.3.7, when it was not neccessary for gimp1.2.x > > Because it's there (even on Win32), it would be stupid not to use it. It also is required for gtk 2.0. > >> However, using pkg-config makes the configure.in files *less* complex.) > > really? > Yes. Before pkg-config, lots of different libraries had scripts that did the exact same thing (and most of the time shared about 99% of the code in common.) The purpose of these scripts was just to tell autoconf which arguments were needed to use a library (locations, etc.) It made sense to combine all of these foo-configs into one unified program. Before that, compiling a big program like gimp was a nightmare if you had libraries installed in any location other than /usr/lib. Autoconf only looks for libraries in a couple of locations and then gives up, unless you explicitly tell it where the libraries are. So you would have to do something horrible like: ./configure --with-libfoo=/home/notroot/lib --with-libbar=/home/notroot/lib --with-libbaz=/home/notroot/lib a tiresome, annoying, and error-prone process, especially if many libraries were involved. But the same thing with pkg-config (asumming all of the libraries are pkg-configized) is just PKG_CONFIG_PATH=/home/notroot/pkgconfig ./configure much much much better. We have tried very hard to make gimp easy to compile for people in somewhat unusual conditions, and pkg-config helps this immensely. Rockwalrus ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Using "cout" to write to a file --- help neededurgently
On Fri, 7 Jun 2002, Sugandhi wrote: > Hi, > > My project is to develop an artificial neural network to classify satellite > images. And, this "classifier" is to be a plugin to gimp. But, to "cout" to > a file on the disk --- I am not able to do this, unless I run gimp from the > console. > > Any suggestions are welcome, and are really needed. Don't use cout. ;) Use an ofstream or an ANSI C style fopen, fprintf, etc. Rockwalrus ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Your message to Gimp-announce awaits moderator approval
Your mail to 'Gimp-announce' with the subject All rights reserved. Is being held until the list moderator can review it for approval. The reason it is being held: Message body is too big: 125812 bytes but there's a limit of 40 KB Either the message will get posted to the list, or you will receive notification of the moderator's decision. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Your message to Gimp-user awaits moderator approval
Your mail to 'Gimp-user' with the subject All rights reserved. Is being held until the list moderator can review it for approval. The reason it is being held: Message body is too big: 125894 bytes but there's a limit of 40 KB Either the message will get posted to the list, or you will receive notification of the moderator's decision. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Thin lines
Hi, Henning Makholm <[EMAIL PROTECTED]> writes: > Hm, seems the bleeding-edge cvs source doesn't compile right now. > After lots of trouble because I have automake 1.6 instead of automake > 1.4 (separate bug report filed) I ended up at > > ... > -g -O2 -Wall -c gimpunits.c > gimpunits.c: In function `gimp_unitrc_load': > gimpunits.c:100: too few arguments to function `gimp_scanner_new' > make[3]: *** [gimpunits.o] Error 1 > make[3]: Leaving directory `/scratch/foogimp/gimp-1.3.cvs/app/core' > ... that's the anoncvs problem reported here earlier. The tree you got from anoncvs is inconsistent. This sucks :-( Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Thin lines
Scripsit Sven Neumann <[EMAIL PROTECTED]> > one place. Patches should preferably be generated against the CVS tree Hm, seems the bleeding-edge cvs source doesn't compile right now. After lots of trouble because I have automake 1.6 instead of automake 1.4 (separate bug report filed) I ended up at ... -g -O2 -Wall -c gimpunits.c gimpunits.c: In function `gimp_unitrc_load': gimpunits.c:100: too few arguments to function `gimp_scanner_new' make[3]: *** [gimpunits.o] Error 1 make[3]: Leaving directory `/scratch/foogimp/gimp-1.3.cvs/app/core' ... > but the latest tarball should also do fine. I'll work from there, and see if the cvs tree happens to be consistent when I'm done. -- Henning Makholm "Slip den panserraket og læg dig på jorden med ansigtet nedad!" ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Using "cout" to write to a file --- help needed urgently
Hi, My project is to develop an artificial neural network to classify satellite images. And, this "classifier" is to be a plugin to gimp. But, to "cout" to a file on the disk --- I am not able to do this, unless I run gimp from the console. Any suggestions are welcome, and are really needed. Thank you all _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] bug reports
Hi, could you please stop posting bug-reports to this mailing-list and use Bugzilla instead. And please, try to describe your problems better than you did here since I've had a hard time trying to understand you. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] numeric ENTER
GIMP 1.2 ignores a numeric ENTER (the bottomleftmost key on the keyboard). Clock ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] missing vertical line
I have made an image 4050x3186 and selected with rect select 162x3186 flushed to the right. The zoom was at 1600%. The left vertical line was missing. When I made border selection 1 on this, both vertical lines were missing. The horizontal lines were present and animating. GIMP 1.2 Clock ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Missing both vertical ines
I did "border selection" with parameter of 1 in the rect select with missing vertical line and got a rect select with bot vertical lines missing. Bucket filling with both white and black worked. GIMP 1.2 Clock ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Missing rect select line
I have created an image 4050x3186 pixels and selected a rectangle 162x3186 touching the left edge. The image was RGB and uniform white. The right vertical line of the rect select was missing. Bot the bottom a top lines were present and animating. The view was 1600% when I was performing the selection. GIMP 1.2 Clock ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Race conditions
I moved a layer in a big image with 10 layers and during redrawing of the image, I saved it to the disk. Result: 8 layers of the 10 disappeared. It is obvious GIMP absolutely ignores consistency - you can for example run two different filters or scripts simultaneously and the image becomes a total garbage then when they fight over the data. This should be fixed. Clock ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] [Fwd: Bug#148412: gimp1.2: Gimp is not consistently licensed]
Hi, RaphaXl Quinet <[EMAIL PROTECTED]> writes: > > > ./gimp-1.2.1.in (Spencer Kimball, Peter Mattis) > > > ./gimptool-1.2.1.in (Owen Taylor, Manish Singh) > > > > This is gibberish. Someone bolted on some boiler plate which claims that > > the whole of the GIMP is covered by an obnoxious advertising clause. > > Most likely this happened because they copied an existing manual page > > source from another project. > > AFAIK, that license refers to the manual pages, not to the whole > program. It was certainly added there by mistake, considering who the > authors of these manual pages are. So in that case it is probably safe > to fix the license immediately. ack. I'll leave this up to Yosh since he's one of the authors and may change these lines. > Note that Ben was not the one complaining. He simply forwarded the > Debian bug report from Anthony DeRobertis. And the license is wrong > anyway, regardless of who wrote the manual pages. > > > > ./plug-ins/common/gif.c (David Koblas) > > > ./plug-ins/common/tiff.c(Patrick J. Naughton) > > > > We already knew about at least these and I was told (on #gimp I think) > > that it was not a problem. > > Whoever told you that was wrong. The text of both licenses includes: > "provided that the above copyright notice appear in all copies and that > both that copyright notice and this permission notice appear in > supporting documentation." This is the advertising clause that is not > compatible with the GPL. As a result, these files cannot be distributed > with the GIMP as they are now. I don't see the problem. The code has the copyright notice as is required by the original license. We explicitely state the original authors. Where the heck is the problem?? Same applies for gimp-remote and the webbrowser plug-in. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] i18n
Hi, Karel Kulhavy <[EMAIL PROTECTED]> writes: > When I set up Czech keyboard in ISO 8859-2 encoding in X (I can write > czech letters in xterm) and run GIMP, make new image, text tool, filter > fonts to get only the 8859-2 ones and try to write Czech chars into the > text line, they are ignored. > > If I don't filter it, it works. some more details like the version of GIMP you are using would help a lot. This looks like it has already been reported as http://bugzilla.gnome.org/show_bug.cgi?id=23226 or even http://bugzilla.gnome.org/show_bug.cgi?id=79754 Could you please check if your problem fits into one of those bug-reports and probably add some comments to them. Or file a new bug-report if none of the existing bug-reports fit. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Ignored font switches
I was trying to choose a suitable font and GIMP suddenly stopped responding to font changes. I could write and delete the text, but switching between all the fonts did not yield anything. I have suspision this happened after I struck a font, at which the GIMP stopped responding for several minutes (I have seen this behaviour at X server). THe installation is some nearly default Redhat, the GIMP 1.2 CLock ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
Hi, "Adam D. Moss" <[EMAIL PROTECTED]> writes: > Sven Neumann wrote: > > You expect the HEAD branch to compile if you can't get the stable > > version to build??? > > I expect nothing. But it was worth a try??? > > > looks like glibconfig.h hasn't been generated properly. > > Good one, a 1.2 header was being picked up instead of > the 2.0 one. Things are going smoother now. your glib-1.2 installation is pretty old then. Glib has been changed to install headers into versioned directories ages ago. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] i18n
When I set up Czech keyboard in ISO 8859-2 encoding in X (I can write czech letters in xterm) and run GIMP, make new image, text tool, filter fonts to get only the 8859-2 ones and try to write Czech chars into the text line, they are ignored. If I don't filter it, it works. Clock ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
Sven Neumann wrote: > You expect the HEAD branch to compile if you can't get the stable > version to build??? I expect nothing. But it was worth a try??? > looks like glibconfig.h hasn't been generated properly. Good one, a 1.2 header was being picked up instead of the 2.0 one. Things are going smoother now. Thanks, --Adam ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
Hi, "Adam D. Moss" <[EMAIL PROTECTED]> writes: > Thanks! Got fontconfig now. > The reason I was trying pango HEAD was that pango-1-0 > does not compile for me. However, the same problem (below) > occurs for me on HEAD too. D'oh. You expect the HEAD branch to compile if you can't get the stable version to build??? > gcc -DHAVE_CONFIG_H -I. -I. -I../.. -DPANGO_ENABLE_ENGINE > -DSYSCONFDIR=\"/usr/local/etc\" -DLIBDIR=\"/usr/local/lib\ > " -DG_DISABLE_DEPRECATED -I/usr/local/include > -I/usr/local/include/freetype2 -I/usr/X11R6/include -I../.. -g -O2 -Wa > ll -D_REENTRANT -I/usr/local/include/glib-2.0 > -I/usr/local/lib/glib-2.0/include -Wp,-MD,.deps/pango-ot-info.pp -c pa > ngo-ot-info.c -fPIC -DPIC -o pango-ot-info.o > In file included from /usr/local/include/glib-2.0/gobject/gboxed.h:26, > from /usr/local/include/glib-2.0/glib-object.h:25, > from pango-ot-private.h:27, > from pango-ot-info.c:22: > /usr/local/include/glib-2.0/gobject/gtype.h:92: syntax error before > `typedef' > @@gtype.h:91:#if GLIB_SIZEOF_LONG == GLIB_SIZEOF_SIZE_T > @@gtype.h:92:typedef gulong GType; looks like glibconfig.h hasn't been generated properly. Are you sure you didn't overlook and errors when configuring glib? Perhaps take a look at /usr/local/lib/glib-2.0/include/glibconfig.h. It should have lines that say something like this: #define GLIB_SIZEOF_VOID_P 4 #define GLIB_SIZEOF_LONG 4 #define GLIB_SIZEOF_SIZE_T 4 Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] new xinput device: no movement when button down
Michael Natterer wrote: > > This is as good a point to ask as any; in following the > > latest incarnation of the crazy dep-chain I ran into a > > dead-end finding the mysterious 'fontconfig' (fontconfig > > is needed by pango is needed by gtk2 is needed by gimp). > > Anyone know where I can find such a thing? I thought > > that it sounded like it was probably part of pkgconfig > > (pkgconfig is needed by... etc) but it doesn't seem to > > be. > > Hi Adam, > > It's just the HEAD version of pango which requires fontconfig, you > probably wanted to checkout the "pango-1-0" branch. > > The branches are glib-2-0, pango-1-0, atk HEAD, gtk-2-0. Thanks! Got fontconfig now. The reason I was trying pango HEAD was that pango-1-0 does not compile for me. However, the same problem (below) occurs for me on HEAD too. D'oh. gcc -DHAVE_CONFIG_H -I. -I. -I../.. -DPANGO_ENABLE_ENGINE -DSYSCONFDIR=\"/usr/local/etc\" -DLIBDIR=\"/usr/local/lib\ " -DG_DISABLE_DEPRECATED -I/usr/local/include -I/usr/local/include/freetype2 -I/usr/X11R6/include -I../.. -g -O2 -Wa ll -D_REENTRANT -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -Wp,-MD,.deps/pango-ot-info.pp -c pa ngo-ot-info.c -fPIC -DPIC -o pango-ot-info.o In file included from /usr/local/include/glib-2.0/gobject/gboxed.h:26, from /usr/local/include/glib-2.0/glib-object.h:25, from pango-ot-private.h:27, from pango-ot-info.c:22: /usr/local/include/glib-2.0/gobject/gtype.h:92: syntax error before `typedef' @@gtype.h:91:#if GLIB_SIZEOF_LONG == GLIB_SIZEOF_SIZE_T @@gtype.h:92:typedef gulong GType; /usr/local/include/glib-2.0/gobject/gtype.h:167: syntax error before `gchar' @@gtype.h:167:G_CONST_RETURN gchar* g_type_name (GType type); /usr/local/include/glib-2.0/gobject/gtype.h:335: syntax error before `gchar' /usr/local/include/glib-2.0/gobject/gtype.h:336: syntax error before `gchar' In file included from /usr/local/include/glib-2.0/glib-object.h:25, from pango-ot-private.h:27, from pango-ot-info.c:22: /usr/local/include/glib-2.0/gobject/gboxed.h:28: parse error before `G_BEGIN_DECLS' /usr/local/include/glib-2.0/gobject/gboxed.h:36: syntax error before `typedef' In file included from /usr/local/include/glib-2.0/glib-object.h:26, from pango-ot-private.h:27, from pango-ot-info.c:22: /usr/local/include/glib-2.0/gobject/genums.h:28: parse error before `G_BEGIN_DECLS' /usr/local/include/glib-2.0/gobject/genums.h:46: syntax error before `typedef' In file included from /usr/local/include/glib-2.0/gobject/gobject.h:27, from /usr/local/include/glib-2.0/glib-object.h:27, from pango-ot-private.h:27, [cut -- lots more like this] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Thin lines
Hi, Henning Makholm <[EMAIL PROTECTED]> writes: > I hereby offer my programming skills to the task. great. You have the job. > In greater detail: I understand that the Gimp draws lines by stamping > the brush image at equidistant places along the line. The problem with > thin lines is that those equidistant places are computed in floating > point without any particular attention to pixel boundaries. This gives > ugly lines when the brush is only one or a few pixels across, no > matter (but in different ways) whether the pixel stamps are > anti-aliased or not. right. > As long as we're only drawing straight lines with an 1x1 brush and > spacing 1.0, the solution is clear: just adjust the positions of the > brush centers along the abstract line such that they all have > integral-plus-one-half x coordinates if the slope is horizontalish, > and integral-plus-one-half y coordinates if the slope is verticalish. > > The challenge is to let this scale to (a) larger spacing, bigger > brushes, and (b) stroking of cubic spline paths. > > Regarding (b), the "obvious" idea is to divide the spline into > segments according to the octant of tangent. However, it becomes > difficult to find a simple way to make two segments with different > orientations always meet seamlessly in case of a 1x1 brush with > antialiasing. Instead I propose another solution: compute all points > along the spline where *either* the x coordinate *or* the y coordinate > has fractional part equal to 1/2 - then select a suitable subset of > these points to draw, according to the brush spacing (see below). > > These "extra" brush positions will be invisible if all points are > painted with a 1x1 brush - if the paint from neighbouring brush > positions is combined by "maximum" rather than "addition", the "extra" > brush stamps will always have lower intensity than their "ordinary" > neighbours combined. This holds for the pencil as well as for the > brush, as long as the spline is locally approximated by a line. But > the admission of "extra" positions means that there will be no > discontinuity when the spline's tangent passes from one octant to > another. > > Brush spacing now becomes a matter of choosing among the candidate > points (defined as those where one or both coordinates is n+1/2) > such that the (euclidean) distance between successive actiual painting > operations is at least . > > > So, do you think this is worth wasting time on? If so, what is the > protocol for "outsider"s contributing to the Gimp - does one just post > patches to this list, or must I find a sponsor with commit priveleges, > or what? line drawing is definitely worth to improve. We would like to see this development take place in the 1.3 tree. The prefered protocol for contributions is to use Bugzilla (http://bugzilla.gnome.org/). You open a bug-report (marked as enhancement probably) and attach your patches to it. This way the patch isn't lost even if none of the core developers finds the time to apply it immidiately. Bugzilla also allows us to comment on the patches and keeps everything together in one place. Patches should preferably be generated against the CVS tree but the latest tarball should also do fine. You can also get CVS write access but we prefer to see a couple of patches first. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies
Hi, Tor Lillqvist <[EMAIL PROTECTED]> writes: > Your comparisons of configure.in sizes between GIMP 1.2.3 and 1.3.7 is > unfair, because there are obviously lots of other changes in there, > too. the difference in size is mostly due to the fact that we the configure script in the 1.2 tarballs was generated using autoconf-2.13 while the latest gimp-1.3 tarballs include a configure script generated from autoconf-2.52. The slightly larger configure.in in the 1.3 tree is mostly caused by the fact that I've lately added a lot of comments to improve its readability. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies
Hi, Philip Brown <[EMAIL PROTECTED]> writes: > I'm trying to encourage the developers, to make it easy for future users. > That should be the goal of good software development: to make it easier for > users, rather than easier for the programmers. > > That is to say, making things easier for the programmers is great, as long > as it doesnt come at the EXPENSE of the users. your plan of encouraging people is doomed to fail unless you change your attitude. We put a lot of effort into maintaining our tree and making compilation as easy as possible. We have spent a lot of our free time to make GIMP compile on platforms we not even have access too. This has been possible because people that use such platforms sent detailed descriptions of their problems and suggestion on how to improve them. Some even sent patches which is even more appreciated. You on the other hand show up and without deeper knowledge state that we are doing things all wrong because it doesn't work for you. You question the use of pkg-config as if we have a choice whether to use it or not to use it. You didn't even read it's man-page to inform yourself about it's purpose. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies
Hi, Philip Brown <[EMAIL PROTECTED]> writes: > On Thu, Jun 06, 2002 at 11:08:36AM +0200, Sven Neumann wrote: > > > > you obviously didn't understand what pkg-config does since it does a > > completely different thing than autoconf and in no way intents to > > replace it. > > >From the pkgconfig README: > > "pkg-config is a script to make putting together all the build > flags when compiling/linking a lot easier. " > > Sounds a whole like like autoconf to me. > Or at most, autoconf plus libtool. Which you guys already use. > So pkg-config is redundant. > > To put the same thing another way: > autoconf+libtool seemed to work fine for gimp1.2.3. So if it wasnt broke, > why are you trying to 'fix' it? could you please just stop talking about things you don't understand. Thanks. Salut, Sven FYI: pkg-config replaces glib-config, gtk-config, gimp-config and all those other foo-config scripts that have been around in the time before pkg-config. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] (±¤°í)³×ƼÁðÀÇ ÇʼöÇ°!! ÃÖ°ÀÇ »ç¾÷µ¿¹ÝÀÚ!!
Title: À̸¸ÇÑ ¼º´É¿¡ À̸¸ÇÑ °¡°ÝÀº ´õ ÀÌ»ó ¾ø½À´Ï´Ù ¡¡ Æİݼ¼ÀÏ!! 15¸¸¿ø À̸¸ÇÑ ¼º´É¿¡ À̸¸ÇÑ °¡°ÝÀº ´õ ÀÌ»ó ¾ø½À´Ï´Ù. ¹ß¼Û±â(5Á¾)+ÃßÃâ±â(4Á¾)+À̸ÞÀÏ(8000¸¸Åë)+º¸³Ê½ºÀ¯Æ¿ ±¸ÀÔ¹®ÀÇ : [EMAIL PROTECTED] ±ÍÇÏÀÇ Çã¶ô¾øÀÌ È«º¸¼º ÀüÀÚ ¿ìÆíÀ» º¸³»°Ô µÈ Á¡ Á¤ÁßÈ÷ »ç°ú µå¸³´Ï´Ù. Á¤º¸Åë½Å¸Á ÀÌ¿ëÃËÁø¹ý ±ÔÁ¤À» ÁؼöÇÏ¿© ±¤°í¸ÞÀÏÀÓÀ» Ç¥½ÃÇÏ¿´À¸¸ç, ¼ö½Å°ÅºÎ ÀåÄ¡¸¦ ¸¶·ÃÇÏ°í ÀÖ½À´Ï´Ù. ±ÍÇÏÀÇ ÀüÀÚ ¿ìÆí ÁÖ¼Ò´Â ÀÎÅÍ³Ý »óÀÇ °ø°³µÈ Àå¼Ò¿¡¼ ½ÀµæÇÏ¿´À¸¸ç, ÀúÈñ´Â ±ÍÇÏÀÇ ÀüÀÚ¿ìÆí ÁÖ¼Ò¿Ü ¾î¶°ÇÑ °³ÀÎÁ¤º¸µµ °¡Áö°í ÀÖÁö ¾ÊÀ¸¹Ç·Î ¾È½ÉÇϽñ⠹ٶø´Ï´Ù. ¼ö½ÅÀ» ¿øÄ¡ ¾ÊÀ¸½Ã¸é [¼ö½Å°ÅºÎ]¸¦ Ŭ¸¯ÇØ ÁֽʽÿÀ. ºÎõ½Ã ¼Ò»ç±¸ ±«¾Èµ¿ ¿ø¿õºô¶ó D/401 »ç¾÷ÀÚµî·Ï¹øÈ£ : 130-23-89800 Copyright ¨Ï 2001 Officegirl All rights reserved. ¡¡ ¡¡ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] dependancies
Philip Brown writes: > so far, you seem to have described a situation that implies that autoconf > can work without pkgconfig, but pkgconfig isnt that useful without > autoconf. Sure it is, it can be used in simple hand-written Makefiles, or even directly from the command line. > You did not mention, however, why pkgconfig was suddenly added to > gimp1.3.7, when it was not neccessary for gimp1.2.x Because it's there (even on Win32), it would be stupid not to use it. >> However, using pkg-config makes the configure.in files *less* complex.) > really? Yes. Your comparisons of configure.in sizes between GIMP 1.2.3 and 1.3.7 is unfair, because there are obviously lots of other changes in there, too. --tml ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
