[Gimp-user] Basic GIMP compilation question
I am running a Red Hat 9.0 system that currently has GIMP 1.2.3 installed on it. I'd like to check out 2.0 and have been trying to figure out how to get it together. I haven't compiled much large, involved software yet so I am running into some fundamental questions. First it looks like I need to update my GTK+ (2.2.1-4 installed). After I grabbed the newest GTK, GLib, Pango and ATK tar balls as well as GIMP 2.0.1, I realized that I don't know the procedure for updating an RPM with a program from source code. Do I compile and install the source right over the installed package? Do I need to remove the package first? Won't this wreak havoc with regard to dependencies, etc? Secondly, in the GIMP ftp directory I saw a patch for 2.0.1. What is this patch for and do I need it? Third my system lists a GLib2 2.2.1 package. Am I correct in assuming that this is the GLib referred to on the GIMP installation help page (as opposed to the glib 1.2.10-1 that is also installed on my system)? Is this sufficiently new so as not to need updating for GIMP 2.0.1? TIA, Barton ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Basic GIMP compilation question
Sven Neumann wrote: Hi, Barton Bosch <[EMAIL PROTECTED]> writes: I am running a Red Hat 9.0 system that currently has GIMP 1.2.3 installed on it. I'd like to check out 2.0 and have been trying to figure out how to get it together. I haven't compiled much large, involved software yet so I am running into some fundamental questions. I strongly suggest you don't compile GIMP from source then but use a precompiled binary. http://xach.com/ has RPMs for RedHat 9.0. Unfortunately not 2.0.1 yet but you could at least install all the dependencies from there and compile only GIMP. That will save you some major troubles. Getting all the dependencies compiled from source requires a good deal of experience building software from source. Thanks for the quick response and the link to the RPMs. Those should be very helpful. Did I miss this on gimp.org somehow? Secondly, in the GIMP ftp directory I saw a patch for 2.0.1. What is this patch for and do I need it? > It's the patch to update gimp-2.0.0 to gimp-2.0.1. Useful for people who downloaded gimp-2.0.0 earlier. Oh, ok, good to know. Barton ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] More GIMP compilation questions
Thanks to the link to the Red Hat 9.0 RPMs (kudos to xach) I've gotten my system updated far enough to attempt to compile gimp 2.0.1 from source. I've compiled and installed many of the optional packages as well. I am running into a couple of warning messages though, re: gtkhtml2 and the html help browser, laa/aa_printf, and llcms and the color proof module. FYI, for the time being I am configuring with the --disable-print option. Here is the relevant ./configure output: checking for aa_printf in -laa... no configure: WARNING: *** AA plug-in will not be built (AA library not found) *** ... checking for libgtkhtml-2.0 >= 2.0.0... Package libgtkhtml-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `libgtkhtml-2.0.pc' to the PKG_CONFIG_PATH environment variable configure: WARNING: *** Help browser plug-in will not be built (GtkHtml2 not found) *** ... checking for cmsCreate_sRGBProfile in -llcms... no configure: WARNING: *** color proof module will not be built (lcms not found or unuseable) *** I've checked my repositories for unistalled packages and their devel couterparts, done a good bit of googling for further packages/tar balls to download and install but no joy. Anyone have a solution? Thanks, Barton ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] More GIMP compilation questions and some answers
Owen wrote: On Mon, 03 May 2004 16:52:52 -0700 Barton Bosch <[EMAIL PROTECTED]> wrote: checking for aa_printf in -laa... no configure: WARNING: *** AA plug-in will not be built (AA library not found) *** ... checking for libgtkhtml-2.0 >= 2.0.0... Package libgtkhtml-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `libgtkhtml-2.0.pc' to the PKG_CONFIG_PATH environment variable configure: WARNING: *** Help browser plug-in will not be built (GtkHtml2 not found) *** ... checking for cmsCreate_sRGBProfile in -llcms... no configure: WARNING: *** color proof module will not be built (lcms not found or unuseable) *** I wouldn't worry too much about all those. I figured as much, but with such a long compile I thought I would try to get all of the wrinkles ironed out before I tried making gimp2.0.1. gtkthml2 was installed on my system, it was just lacking the headers from the devel package. I did run a check (actually double checked with the filter on my local repository) and i could have sworn gtkhtml was not installed... So the help browser situation was resolved with a simple rpm -Uvh. I thought that someone on the list might know what lcms and laa were off the top of their heads but in the meantime I did eventually manage to track these packages down. The ascii art plug in is not really essential, more of a toy in my view. A red hat 9 (shrike) rpm for laa can be found in on freshrpms (http://shrike.freshrpms.net/rpm.html?id=1184). libgtkhtml is for the help, but there's not much in the way of help at the moment, so you don't need it. If you want the help, you need to get it from CVS and build it from there. gtkhtml and gtkhtml2 are standard red hat rpms (I just looked through them somehow ). lcms, you sure you haven't got it? Anyway, it too is not really necessary for Gimp operation, but is useful for color proofing type work. lcms is not a standard red hat package as far as I can tell, and I wasn't able to find an rpm at all. The compile was more or less painless though. The source can be found at: http://www.littlecms.com/downloads.htm. Combined with the rpms for updating rh9 for compiling gimp2.0.x from source (found at http://xach.com/gimp/rpms/), the gimp-print rpms for rh9 (at: http://xoomer.virgilio.it/wvtberti/linux/stp_driver/gs_stp.htm), the gimp-gap source (which requires wavplay for audio playback to function -- this was a little tough to find as search engines turned up many random listings for obsolete versions, though I got the source for 1.4 from: http://adnc.linux.tucows.com/preview/47649.html), and a bunch of the optional packages (libexif, libwmf, libsrvg, the gimp-documentation, etc.); I did get the gimp compiled and configured. It even looks operational now, though I haven't had time to test it much yet . From what I have done the UI seems better, maybe a little smoother. GIMP also feels a little faster though that could be totally subjective. All in all, so far so good -- a bigup to all the developers and contributors for this fine free software. I do have another question, re: the Perl plugin though. When trying to compile it it says that it can't find gimp when it tries to run the test program: checking for GIMP - version >= 2.0.0... no *** Could not run GIMP test program, checking why... *** The test program compiled, but did not run. This usually means *** that the run-time linker is not finding GIMP or finding the wrong *** version of GIMP. If it is not finding GIMP, you'll need to set your *** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point *** to the installed location Also, make sure you have run ldconfig if that *** is required on your system *** *** If you have an old version installed, it is best to remove it, although *** you may also be able to get things to work by modifying LD_LIBRARY_PATH configure: error: ** unable to find gimp, make sure it's in your path (version 1.3.15+ required!) I tried putting the location of the gimp binary into ld.so.conf and the LD_LIBRARY_PATH variable, but no joy. What is the story here? Was I supposed to put the location of a library in the path variable? Something else entirely? Anyone have any solutions? There was also a small problem with the gimp swap file location. When I configured gimp on the first run I tried moving the swap file to /tmp as suggested but there was a problem (probably permissions) and gimp couldn't open it. In the Preferences->Folders menu there is a dialog box for changing the location of the swap file. I changed it to various locations, but each time I restarted the gimp it reverted to the location set during the original configuration. Changing it through the preferences menu wasn't possible. Eventually it was fixed by editing .gimp/gimprc the old fashioned way. Ciao, Barton ___ Gim
Re: [Gimp-user] GIMP compilation meltdown; xachs rpms
Sven Neumann wrote: Hi, Barton Bosch <[EMAIL PROTECTED]> writes: I do have another question, re: the Perl plugin though. When trying to compile it it says that it can't find gimp when it tries to run the test program: checking for GIMP - version >= 2.0.0... no *** Could not run GIMP test program, checking why... *** The test program compiled, but did not run. This usually means *** that the run-time linker is not finding GIMP or finding the wrong *** version of GIMP. If it is not finding GIMP, you'll need to set your *** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point *** to the installed location Also, make sure you have run ldconfig if that *** is required on your system *** *** If you have an old version installed, it is best to remove it, although *** you may also be able to get things to work by modifying LD_LIBRARY_PATH configure: error: ** unable to find gimp, make sure it's in your path (version 1.3.15+ required!) I tried putting the location of the gimp binary into ld.so.conf and the LD_LIBRARY_PATH variable, but no joy. What is the story here? Was I supposed to put the location of a library in the path variable? Something else entirely? Anyone have any solutions? Please read up on ld (man ld). You will need to configure the location of the gimp libraries, not the executable. Ok, thanks for the pointer to the documentation. The warning message in the configure log was a little opaque for my (lack of) softare compiling skills. Unfortunately, I guess I spoke too soon about the successful gimp2.0.1 install. The next day my whole system melted down and stopped functioning. I did a hardware reset and it crashed completely before it got past the x login screen. I did a complete reinstall of the root partition and tried to figure out if it was some mistake I made in compiling the various libraries and plugins or if it was one of the RPMs that I used. BTW, I am not running a vanilla rh 9.0 installtion here, but the Planet CCRMA digital audio sub-distro w/ low latency kernel, etc. The CCRMA install and configure followed the basic shrike install, updates with the rh and ccrma rpms -- everything running smoothly to this point. Then I installaed xach's update rpms. I noticed a couple of glitches in gnome, though it was basically functioning. In an attempt to isolate the problem I decided to reboot before adding any other software . The system crashed before it could shutdown cleanly so the trouble msut be some conflict between xach's rpms and either the CCRMA modifications or the basic Shrike installation. When I have more time (three reinstalls in 2 days, ugh) I will free up some room on the HDD and make a separate partition for a vanilla rh 9.0 installation and try to upgrade that with xachs's RPMs and then compile gimp2.0.1. For now I guess I am back to using gimp1.2.3. Ciao, Barton ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] GIMP 2.0.1 and Fedora Core 1
John Dietsch wrote: Greg, For Fedora, you need to learn to use yum. If you installed FC from an RPM, it should already be there. Check in /etc for yum.conf . If it's not there, go to the source where you got the Fedora RPM and install yum. For the new Gimp you need to be in Fedora Core 2. Should I take it that installing the new GIMP on FC1 is not significantly easier than on rh 9 (shrike)? I am fairly happily running shrike but am not really up for burning too many more days trying to get GIMP 2.x running on it. I was assuming that the availability of a GIMP 2.x RPM for FC1 meant that there would be a smooth install and was planning on making an FC1 partition on my HDD. What are people's experiences re: GIMP 2.x and FC1? Is it the same nightmare of rebuilding gtk2? Or is it better than rh 9? I hope this helps. Thanks, Barton ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] Re: GIMP 2.0.1 and Fedora Core 1
John Dietsch wrote: On Sat, 12 Jun 2004, Barton Bosch wrote: Should I take it that installing the new GIMP on FC1 is not significantly easier than on rh 9 (shrike)? It is the same. What are people's experiences re: GIMP 2.x and FC1? Is it the same nightmare of rebuilding gtk2? Or is it better than rh 9? I tried it. There are 79 packages involed. If you are not an expert do not try it. If you are running RH9 or FC1 you can upgrade to FC2. If you want the simple easy answer just upgrade to fc2. It comes with version 2.0 of gimp. I have only done a bit of checking into the newer distros, but isn't FC2 a 64 bit OS? That would make it incompatible with my PIII 550, correct? On a related note, would that mean that when FC1 hits its EOL date (if it hasn't already) that there will be no more official updates or security fixes for redhat based x86 operating systems? Ciao, Barton ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Re: GIMP 2.0.1 and Fedora Core 1
Michael Schumacher wrote: I have only done a bit of checking into the newer distros, but isn't FC2 a 64 bit OS? That would make it incompatible with my PIII 550, correct? Don't start spreading FUD. From http://fedora.redhat.com Sorry, no FUD intended. The info I got: CPU Requirements This section lists the CPU specifications required by Fedora Core 2. * AMD64 processors (both Athlon64 and Opteron) * Intel processors with IntelĀ® Extended Memory 64 Technology (IntelĀ® EM64T) was from: http://fedora.redhat.com/docs/release-notes/ Not sure how the direct contradiction between the main FC2 page that you linked to and the release notes pages that a search for "fedora core system requirements" search took me to happened, but it is reassuring that FC2 is available for x86-64 and i386. How is FC2 running for folks (especially with regard to GIMP 2.0.1)? Chances are that if I install FC2 I will just put it in a spare partition and keep rh 9 as my production os. I briefly considered branching out to s Debian Sarge partition that would allow an 'apt-get install gimp', but my situation is further complicated by being on a 56k line. A kind windows user is downloading the isos of the new distro for me and I really don't see him installing Debian Jigdo to get the Sarge cd images But your general statement about discontinuing support for "redhat based x86 operating systems" is wrong, as indicated by the release anouncement - it is even ambiguous, since the 64 bit version is for "x86-64" :) Yeah ok, thanks for sorting that out. Barton ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] dpi from 75 -> 300 ??
While we're on the topic of scaling/resampling maybe someone could clarify something for me. I read somewhere that when scaling an image for display on a monitor that it was best to change the dpi by the same ratio to avoid interpolation. Elsewhere I have gotten the impression that dpi was totally and always irrelevant to images on the screen. My limited understanding is that when scaling an image from, e.g. 1600 pixels wide to 400 pixels wide, that it is best to change dpi in the same ratio, say, from 72 dpi to 288 dpi. And further that it is even more important when upsampling an image. The desired result being the avoidance of any blurring from the software not being able to map the scaled image pixel for pixel. Is this accurate? Does any of it actually show up on the screen or would it only apply to printed images? Thanks, Barton ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] dpi from 75 -> 300 ??
Sven Neumann wrote: Hi, Barton Bosch <[EMAIL PROTECTED]> writes: While we're on the topic of scaling/resampling maybe someone could clarify something for me. I read somewhere that when scaling an image for display on a monitor that it was best to change the dpi by the same ratio to avoid interpolation. Elsewhere I have gotten the impression that dpi was totally and always irrelevant to images on the screen. My limited understanding is that when scaling an image from, e.g. 1600 pixels wide to 400 pixels wide, that it is best to change dpi in the same ratio, say, from 72 dpi to 288 dpi. And further that it is even more important when upsampling an image. The desired result being the avoidance of any blurring from the software not being able to map the scaled image pixel for pixel. Unless you disable "Dot-for-Dot" in the GIMP's image window (it's in the View menu), you will always see one pixel of the image taking up one pixel on screen (of course only in 1:1 zoom ratio). The dpi setting is irrelevant for the image display. It becomes of importance if you want to use the rulers or the measure tool with real-world units. Then GIMP needs to know how large a pixel will end up on the final print or projection or whatever your final media is. Changing the dpi setting alone won't alter your pixel data. It's just some meta information. Even if you disable dot-for-dot view in GIMP, the dpi information is only used in the display routines. Your pixel data is not changed. Okay, thanks for the definitive answer. The few references to changing the dpi when scaling must have been in regards to printed images. ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] unsharp mask and jpg with quality setting change
I have some 1200 dpi scans that need to be scaled down, sharpened with unsharp mask and then saved as jpgs at ~50% quality setting. Should the operations be performed in the order above or would it be better to scale->save as 50% qual jpg->unsharp mask->save as 100% qual jpg? Thanks, Barton ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] unsharp mask and jpg with quality setting change
Carol Spears wrote: On Sat, Oct 02, 2004 at 02:07:43PM -0700, Barton Bosch wrote: I have some 1200 dpi scans that need to be scaled down, sharpened with unsharp mask and then saved as jpgs at ~50% quality setting. i am curious for the reason for saving at the 50% quality setting. fiddling with the quality setting is good to do if you are trying to improve the load speed of a web page and perhaps to save disc space if this is a problem. i guess i would like to know what the purpose is for the image. Yup, just trying to make the document a little lighter weight. The basic purpse of the doc is as a series of reference charts and tables that will be hyperlinked -- eliminating the need to repeatedly refer to the paper book that the scans were taken from. Nothing especially exciting, but I am learning about different practices for high quality image manipulation in The GIMP. Should the operations be performed in the order above or would it be better to scale->save as 50% qual jpg->unsharp mask->save as 100% qual jpg? saving should be only one step and the last step. the unsharp mask should be the second to the last step. if sharpening is necessary, it should be done on each size that you save. so in short: 1) scale 2) sharpen 3) save Ok, thanks. Barton ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] Curving an image
What are the best ways to take an image of a straight line and bend it into an s-curve with The GIMP? I have tried the perspective and shear tools as well as the distort->curve bend filter without producing an ideal result. Are there other options? I'd like to be able to set some points and pull them around with the mouse similar to the UI for the path tool. Thanks, Barton ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Curving an image
Joao S. O. Bueno Calligaris wrote: On Wednesday 10 November 2004 06:44, Carol Spears wrote: On Tue, Nov 09, 2004 at 03:44:52PM -0800, Barton Bosch wrote: What are the best ways to take an image of a straight line and bend it into an s-curve with The GIMP? I have tried the perspective and shear tools as well as the distort->curve bend filter without producing an ideal result. In a word: iwarp . Search for the iwarp filter in the Distorts menu - that is your man. Huh, I tried the Iwarp filter but it seems to be broken (GIMP 2.0.4 from the FC2 rpm). It showed the layer in the preview window but regardless of any changes in parameters it didn't alter the image at all. Did I miss something, is this a known problem or a mystery? Barton ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Curving an image
Sven Neumann wrote: Hi, Barton Bosch <[EMAIL PROTECTED]> writes: Huh, I tried the Iwarp filter but it seems to be broken (GIMP 2.0.4 from the FC2 rpm). It showed the layer in the preview window but regardless of any changes in parameters it didn't alter the image at all. Did I miss something, is this a known problem or a mystery? You missed the fact that you need to manipulate the preview by clicking and dragging it. It isn't easily discoverable, I admit. Patches to improve this or contributions to the help are of course appreciated. I was wondering whether the parameters were unnecessarily vague or I was just failing to grok the filter. Just now gave it a whirl and it is the filter for the task. You're probably way ahead of me on this but wouldn't a larger preview window and an expanded UI (e.g., like the path tool) be great with Iwarp? Maybe implementing it as a tool rather than a filter would be in order as well? Regardless, I've been doing some real work (TM) with The GIMP lately and I'd like to say thanks for the excellent app and all of the effort that goes into creating it, thanks a lot. Ciao, Barton ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Curving an image
Sven Neumann wrote: Hi, Barton Bosch <[EMAIL PROTECTED]> writes: You're probably way ahead of me on this but wouldn't a larger preview window and an expanded UI (e.g., like the path tool) be great with Iwarp? Maybe implementing it as a tool rather than a filter would be in order as well? Sure, noone would disagree that the plug-in urgently needs some love. But so far noone has taken responsibility for it. There are a lot of plug-ins that are part of the distribution but are basically unmaintained. We don't have enough developer resources to work on the core and improve the ~ 200 plug-ins in the GIMP tree. Heh heh. I fully appreciate your point and understand what it means for a project on the scale of The GIMP to be brought into the world by volunteers. I hope that the understanding is reciprocated in that my comments shouldn't be taken as implying dissatisfaction with the developers' efforts or any kind of demand for a specific feature to be implemented. Just casual commentary to be taken for what its worth. As I said already, if you want to contribute, please do so. You wouldn't have to necessarily write code. The GIMP help team (the people working on the user manual) are looking for contributors as well as the GIMP web team. Other than a little photo cropping, the last few days have been the first opportunity I've had to do any significant gimping. To this point I've been contributing by not messing up the works with my ignorance of digital image manipulation in general or of The GIMP in particular. With a little bit of experience I may actually have something worthwhile to contribute so I'll check into the documentation project in the near future. Regards, Barton ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Layers merging on exit
Ryan Coyner wrote: Hey guys. I'm having some problems with layers, and if any of you can help me find a solution, I'd appreciate it. When I quit (after saving) the gimp while working a project with multiple layers, all the layers seem to merge into one called "Background" when I open it up again. Is there a way to preserve the multiple layers so tha when I come back to the project I can edit the individual layers? Thanks in advance. Try saving in .xcf format, it should save most Gimp relevant items along with your image data. Barton ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Gimp 2.2.6 on Fedora Core 3
Owen Cook wrote: On Sun, 17 Apr 2005, Asif Lodhi wrote: OK, go to your gimp-2.2.6 directory type ./configure --help and have a read, even it it means little You will see how to install in another prefix, example ./configure --prefix=/opt will configure so that it is built in /opt I've been meaning to take another shot at learning how to compile the gimp from source for a while now. I'm running FC2 which has rpms available for almost all of the requirements and optional packages. Unfortunately the atk rpm is version 1.6.0 (www.gimp.org/source lists 1.6.1 as required) and the fontconfig rpm is 2.2.1-10 (2.2.2 required). Seeing how these are quite close and as you mentioned the parallel /opt configure method, I went ahead and ./configure, make and make installed. Gimp 2.2.6 did compile without error messages but didn't function properly. After opening a few jpgs and cropping them, it saved the first immediately without opening the jpg options dialog, and on the second and subsequent attempts to save jpgs it hung (though it did respond to the close button as opposed to requiring a killall -HUP gimp). So, two main questions: 1) is there a way to compile atk and fontconfig in parallel to the already installed rpms (as the gimp 2.2.6 was) and then pass a configure option or edit a script to have gimp use the new versions?; and, 2) when it became necessary to uninstall the faulty 2.2.6 I found that make clean from the source directory tried to erase files from /usr/local/ rather than /opt where gimp 2.2.6 was actually installed -- is there a way to pass an option to make clean to tell it to remove the gimp from /opt? Are /opt and /home/.gimp-2.2 the only directories (besides the untarred source directory) that need to be manually deleted? Thanks, Barton -- "All experience hath shown that even under the best forms of government those entrusted with power have in time and by slow operations perverted power to tyranny, and it would seem that the best means of preventing this would be, insofar as practicable, to enlighten the minds of the public at large." -- Thomas Jefferson ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Gimp 2.2.6 on Fedora Core 3
Owen Cook wrote: On Mon, 18 Apr 2005, Barton Bosch wrote: So, two main questions: 1) is there a way to compile atk and fontconfig in parallel to the already installed rpms (as the gimp 2.2.6 was) and then pass a configure option or edit a script to have gimp use the new versions?; and, 2) when it became necessary to uninstall the faulty 2.2.6 I found that make clean from the source directory tried to erase files from /usr/local/ rather than /opt where gimp 2.2.6 was actually installed -- is there a way to pass an option to make clean to tell it to remove the gimp from /opt? Are /opt and /home/.gimp-2.2 the only directories (besides the untarred source directory) that need to be manually deleted? There will/should also be files called gimp-2.0.pc gimpui-2.0.pc and gimpthumb-2.0.pc You better find out where these are as if you had two Gimps installed you might be in big trouble as where your gimp-2.2.6 was looking for things. Ok, these files were missing when I first checked but may have been part of the gimp-devel rpm which I did not have installed at the time. My gimp 2.0.5 rpm installation seemed to be working fine but just for the hell of it, I uninstalled and then reinstalled both gimp and gimp-devel 2.0.5. Then I found the gimp*.pc files in /usr/lib/pkgconfig. Have a look there and see if you can psyche out the gimp-2.0.pc matter and search paths. Look back in these archives I think for where you should set the LD_LIBRARY PATH The /usr/lib/pkgconfig/gimp-2.0.pc file shows: libdir=/usr/lib ... gimplibdir=/usr/lib/gimp/2.0 ... Libs: -L${libdir} -lgimp-2.0 -lgimpmath-2.0 -lgimpcolor-2.0 -lgimpbase-2.0 whereas /opt/lib/pkgconfig/gimp-2.0.pc is the same, but with everything preceded by {prefix} (which is set to /opt), e.g.: prefix=/opt exec_prefix=${prefix} libdir=${exec_prefix}/lib What I think might be happening is that your are using the /opt/bin/gimp binary but loading the libraries from your other installation So it seems that this is being set up correctly by ./configure. In running through this again to verify everything before this post to the list, I happened to do the initial run of /opt/bin/gimp-2.2 from the root terminal window that I compiled and installed from rather than from a regular user term. I vaguely remember something like gimp 1.2 needing to be run once as root before regular users could run it. Could the fact that I did not do this last time have caused the malfunctions? Additionally, for this installation I chose not to migrate my user settings and just clicked through all of the user customization options on default. In a brief test I seem to have a functional gimp-2.2.6, or at least have shed the problems that I was experiencing with the prior installation attempt. When I get more time I'll do a more thorough test run, thanks for the help. BTW, if I were to experience problems related to an obsolete atk or fontconfig, how would they be likely to manifest themselves? Barton -- "It is public domain knowledge that has led to creation of specialized knowledge. The issue is that our policymakers have to take into consideration the needs of the common man ie. the public domain as well as the interests of companies. In the US, software patents have been taken to ridiculous lengths - [Yoyodyne Propulsion Systems] owns the patent for single click online shopping so anyone starting a shopping website has to use a system which requires the user to click at least twice." -- DB Phatak ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] How to change font size?
David Adam wrote: Greetings, helpful people! I need to add annotation to images, but cannot figure out what to do to change the font size. The documentation clearly states that this is easy to do, but I have been unable to find out how to do it under Gimp 2.2. In particular, Tools -> Text and Dialogs -> Fonts do not seem to lead me where I want to go. I'm sure the answer is simple, but I'm stumped. What do I do? Not sure where you're seeing "Text and Dialogs" but if you wish to add Text to an image click the T icon in the tools dock which will bring up the Text Tool options, including "Size:". Then click the up and down arrows or enter a number into the field directly. Also, check: http://docs.gimp.org/en/ch02s04s12.html Peace, Barton -- "Those who can make you believe absurdities can make you commit atrocities" -- Voltaire ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Fast way to view all patterns?
Joao S. O. Bueno Calligaris wrote: On Monday 16 May 2005 22:18, Rikard Johnels wrote: Hello all! Is there a fast way to view all patterns a bit bigger then the iconic view in the selection tools? I would like to have a palette to view ca. 200x200 pixels big. It would make it easier for me to choose the right one faster. The only way I can think of doing this is buiding an image that displays the patterns the way you like ,a nd keeping this iamge open around. Open a pattern dialog in the dock, select the pattern dialog tab, click on the tab menu (little triangle in the square) button, pick preview size from the menu and then choose a larger size than the default (medium) for the pattern previews. Heh, just learned this one today by reading: http://docs.gimp.org/en/ch02s03s04.html Barton -- "All experience hath shown that even under the best forms of government those entrusted with power have in time and by slow operations perverted power to tyranny, and it would seem that the best means of preventing this would be, insofar as practicable, to enlighten the minds of the public at large." -- Thomas Jefferson ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] Font formats in GIMP
This might be slightly OT, my apologies if it causes any inconvenience. I just got some new fonts and am not quite sure how/if I can use some of them. The TTF fonts are familiar; I just put them into my font directory. There are also a few .AFM (Adobe?) fonts. I found other .afm files on my (fedora) machine. Are these only for acrobat and printing? Can I use them with The Gimp? How can/would I install them. Then there are .wfn fonts which are apparently some proprietary Corel format and are nowhere to be found on my machine. Are these Gimp/Linux compatible at all? Thanks, Barton -- "Concern for man himself and his fate must always be the chief interest of all technical endeavors In order that the creations of our mind shall be a blessing and not a curse to mankind. Never forget this in the midst of your diagrams and equations." -- Albert Einstein ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user