List of dependencies (versions and configuration options) for GIMP on Windows
This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.
This is a read-only list on gimpusers.com so this discussion thread is read-only, too.
List of dependencies (versions and configuration options) for GIMP on Windows
Hi Jernej, or any other developer able to answer before,
This is a question about the official Windows build, which I understand you are the maintainer of.
A user has a problem with fonts on Windows. Fonts with no bold/italic typeface usually can have a simulated bold/italic version. I tested it on Linux, it indeed works well, but not on Windows. I think that Pango is taking care of it since it has such a feature.
Anyway the user says this was working fine on GIMP 2.8.4, but not on GIMP 2.8.6. So I compiled GIMP master, GIMP 2.8.6, 2.8.4 and even older versions. I also tried older versions of pango, freetype, etc. Well I never was able to have this work on Windows. Would you mind telling me exactly the list of dependencies included in your builds, their versions and the configure options? Thanks!
Jehan
P.S.: you can see the bug here: https://bugzilla.gnome.org/show_bug.cgi?id=708110
List of dependencies (versions and configuration options) for GIMP on Windows
On Sunday, September 22, 2013, 10:16:11, Jehan Pagès wrote:
Anyway the user says this was working fine on GIMP 2.8.4, but not on GIMP 2.8.6. So I compiled GIMP master, GIMP 2.8.6, 2.8.4 and even older versions. I also tried older versions of pango, freetype, etc. Well I never was able to have this work on Windows. Would you mind telling me exactly the list of dependencies included in your builds, their versions and the configure options?
Uhh, that's a bit hard - I only build GIMP myself, and use binaries
from OpenSuSE build service
(http://download.opensuse.org/repositories/windows:/mingw:/) for all
dependencies (which I normally update before each build).
I've given up trying to manage dependencies myself a long time ago. I use the following two scripts to get them automatically:
< Jernej Simončič ><><><><>< http://eternallybored.org/ > Those who live closest arrive last. -- Mesta's Law of Parties
List of dependencies (versions and configuration options) for GIMP on Windows
Hi,
On Sun, Sep 22, 2013 at 9:23 PM, Jernej Simončič wrote:
On Sunday, September 22, 2013, 10:16:11, Jehan Pagès wrote:
Anyway the user says this was working fine on GIMP 2.8.4, but not on GIMP 2.8.6. So I compiled GIMP master, GIMP 2.8.6, 2.8.4 and even older versions. I also tried older versions of pango, freetype, etc. Well I never was able to have this work on Windows. Would you mind telling me exactly the list of dependencies included in your builds, their versions and the configure options?
Uhh, that's a bit hard - I only build GIMP myself, and use binaries from OpenSuSE build service
(http://download.opensuse.org/repositories/windows:/mingw:/) for all dependencies (which I normally update before each build).I've given up trying to manage dependencies myself a long time ago. I use the following two scripts to get them automatically:
Ow. That's also what I do. :-/ But since the OpenSuSe repo is
obviously updated regularly, it does not tell us what version was used
back then.
So you have no good way to tell what version of the libraries you used
at the time when you compiled GIMP 2.8.4?
Jehan
< Jernej Simončič ><><><><>< http://eternallybored.org/ >
Those who live closest arrive last. -- Mesta's Law of Parties
_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List of dependencies (versions and configuration options) for GIMP on Windows
On 22.09.2013 at 10:16 A.M., Jehan Pags wrote:
Would you mind telling me exactly the list of dependencies included in your builds, their versions and the configure options?
Hi Jehan,
the dependencies can be found in configure.ac.
Kind regards,
Sven
List of dependencies (versions and configuration options) for GIMP on Windows
Hello,
On Sun, Sep 22, 2013 at 10:21 PM, Sven Claussner wrote:
On 22.09.2013 at 10:16 A.M., Jehan Pagès wrote:
Would you mind telling me exactly the list of dependencies included in your builds, their versions and the configure options?
Hi Jehan,
the dependencies can be found in configure.ac.
Thanks Sven, but that does not say what versions are used on GIMP 2.8.4, official build, which was my question. :-)
Jehan
Kind regards,
Sven
_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List of dependencies (versions and configuration options) for GIMP on Windows
On 22.09.2013 at 12:32 P.M., Jehan Pagès wrote:
Thanks Sven, but that does not say what versions are used on GIMP 2.8.4, official build, which was my question. :-)
Sorry for being a bit terse, I'm in a rush ;-)
You can find the official 2.8.4 build at
Running GIMP with the -v or --version parameter shows the versions of the used libraries.
You can also find the 2.8.4 sources at the Web-Git site: https://git.gnome.org/browse/gimp
Kind regards,
Sven
List of dependencies (versions and configuration options) for GIMP on Windows
Hi,
On Mon, Sep 23, 2013 at 12:49 AM, Sven Claussner wrote:
On 22.09.2013 at 12:32 P.M., Jehan Pagès wrote:
Thanks Sven, but that does not say what versions are used on GIMP 2.8.4, official build, which was my question. :-)
Sorry for being a bit terse, I'm in a rush ;-)
You can find the official 2.8.4 build at
Running GIMP with the -v or --version parameter shows the versions of the used libraries.
Oh thanks, I did not know this one! Jernej actually already sent me an archive with the dependency tree of his build. I was planning to check the .pc files. Fortunately I did not start. And your solution will be easier *and* more accurate. :-)
You can also find the 2.8.4 sources at the Web-Git site: https://git.gnome.org/browse/gimp
Yes the source, I already have them, no problem. :-) Thanks again.
Jehan
Kind regards,
Sven
List of dependencies (versions and configuration options) for GIMP on Windows
As much fun as I'm sure you're all having debugging this, I think I've seen this before. I already fixed this with my windows nightlies (actually, scl reported it, so I guess he forgot about that).
There are two potential issues: 1. fontconfig includes an absolute path to its config directory, so when you move the files to a windows system it cannot find them.
2. The config files themselves are symlinks, which may cause them to not exist on windows, depending on how the files are packaged.
The solutions: 1. Modify etc/fonts/fonts.conf to remove the absolute path and replace it with a relative one (it should just say "conf.d", not long/path/and/then/conf.d). I compile fontconfig with this patch: https://git.gnome.org/browse/gimp/tree/build/windows/jhbuild/patches/fontconfig-fix-config-dir.patch You can achieve the same effect by modifying the config files by hand.
2. Ensure the files in etc/fonts/conf.d/ exist. If not, copy the files from share/fontconfig/conf.avail into that folder.
At the time I fixed this, Jernej's builds did not exhibit the problem because they used an older version of fontconfig. I did not report this upstream because it's a configuration issue, but now that I think about it, the defaults should perhaps be changed on windows (or maybe when cross compiling).
On Sun, Sep 22, 2013 at 9:09 AM, Jehan Pags wrote:
Hi,
On Mon, Sep 23, 2013 at 12:49 AM, Sven Claussner wrote:
On 22.09.2013 at 12:32 P.M., Jehan Pags wrote:
Thanks Sven, but that does not say what versions are used on GIMP 2.8.4, official build, which was my question. :-)
Sorry for being a bit terse, I'm in a rush ;-)
You can find the official 2.8.4 build at
Running GIMP with the -v or --version parameter shows the versions of the used libraries.
Oh thanks, I did not know this one! Jernej actually already sent me an archive with the dependency tree of his build. I was planning to check the .pc files. Fortunately I did not start. And your solution will be easier *and* more accurate. :-)
You can also find the 2.8.4 sources at the Web-Git site: https://git.gnome.org/browse/gimp
Yes the source, I already have them, no problem. :-) Thanks again.
Jehan
Kind regards,
Sven
_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List of dependencies (versions and configuration options) for GIMP on Windows
Needless to say, when I build Gimp, I don't have fontconfig issues.
On Sun, Sep 22, 2013 at 9:51 AM, Michael Henning wrote:
As much fun as I'm sure you're all having debugging this, I think I've seen this before. I already fixed this with my windows nightlies (actually, scl reported it, so I guess he forgot about that).
There are two potential issues: 1. fontconfig includes an absolute path to its config directory, so when you move the files to a windows system it cannot find them.
2. The config files themselves are symlinks, which may cause them to not exist on windows, depending on how the files are packaged.
The solutions: 1. Modify etc/fonts/fonts.conf to remove the absolute path and replace it with a relative one (it should just say "conf.d", not long/path/and/then/conf.d). I compile fontconfig with this patch:
https://git.gnome.org/browse/gimp/tree/build/windows/jhbuild/patches/fontconfig-fix-config-dir.patch You can achieve the same effect by modifying the config files by hand.
2. Ensure the files in etc/fonts/conf.d/ exist. If not, copy the files from share/fontconfig/conf.avail into that folder.
At the time I fixed this, Jernej's builds did not exhibit the problem because they used an older version of fontconfig. I did not report this upstream because it's a configuration issue, but now that I think about it, the defaults should perhaps be changed on windows (or maybe when cross compiling).
On Sun, Sep 22, 2013 at 9:09 AM, Jehan Pags wrote:
Hi,
On Mon, Sep 23, 2013 at 12:49 AM, Sven Claussner
wrote:
On 22.09.2013 at 12:32 P.M., Jehan Pags wrote:
Thanks Sven, but that does not say what versions are used on GIMP 2.8.4, official build, which was my question. :-)
Sorry for being a bit terse, I'm in a rush ;-)
You can find the official 2.8.4 build at
Running GIMP with the -v or --version parameter shows the versions of the used libraries.
Oh thanks, I did not know this one! Jernej actually already sent me an archive with the dependency tree of his build. I was planning to check the .pc files. Fortunately I did not start. And your solution will be easier *and* more accurate. :-)
You can also find the 2.8.4 sources at the Web-Git site: https://git.gnome.org/browse/gimp
Yes the source, I already have them, no problem. :-) Thanks again.
Jehan
Kind regards,
Sven
_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership:https://mail.gnome.org/mailman/listinfo/gimp-developer-list _______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership:
https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List of dependencies (versions and configuration options) for GIMP on Windows
On 22.09.2013 20:30, Partha Bagchi wrote:
Needless to say, when I build Gimp, I don't have fontconfig issues.
And this is because you're building *on* a Windows platform? Or have you found a different solution to the fontconfig configuration?
Regards, Michael GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
List of dependencies (versions and configuration options) for GIMP on Windows
You are correct. I am building on a Windows platform. I assumed that Ender did that too?
On Sun, Sep 22, 2013 at 2:33 PM, Michael Schumacher wrote:
On 22.09.2013 20:30, Partha Bagchi wrote:
Needless to say, when I build Gimp, I don't have fontconfig issues.
And this is because you're building *on* a Windows platform? Or have you found a different solution to the fontconfig configuration?
-- Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD _______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership:
https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List of dependencies (versions and configuration options) for GIMP on Windows
Hi,
On Mon, Sep 23, 2013 at 1:51 AM, Michael Henning wrote:
As much fun as I'm sure you're all having debugging this, I think I've seen this before. I already fixed this with my windows nightlies (actually, scl reported it, so I guess he forgot about that).
There are two potential issues: 1. fontconfig includes an absolute path to its config directory, so when you move the files to a windows system it cannot find them.
2. The config files themselves are symlinks, which may cause them to not exist on windows, depending on how the files are packaged.
The solutions: 1. Modify etc/fonts/fonts.conf to remove the absolute path and replace it with a relative one (it should just say "conf.d", not long/path/and/then/conf.d). I compile fontconfig with this patch: https://git.gnome.org/browse/gimp/tree/build/windows/jhbuild/patches/fontconfig-fix-config-dir.patch You can achieve the same effect by modifying the config files by hand.
2. Ensure the files in etc/fonts/conf.d/ exist. If not, copy the files from share/fontconfig/conf.avail into that folder.
Sorry for the late reply. I wanted to test myself first to be sure it
fixed the issue.
And it does. I just tested on my master build. :-)
So that's indeed the problem and its solution.
At the time I fixed this, Jernej's builds did not exhibit the problem because they used an older version of fontconfig. I did not report this upstream because it's a configuration issue, but now that I think about it, the defaults should perhaps be changed on windows (or maybe when cross compiling).
Yes I am not sure if upstream or else, but definitely somethings should be done *somewhere*, otherwise we might have various new developers to the team (or the same ones, forgetting it happened already) scratching their head with this problem every 6 months. The simple fact that the last Windows build is broken even though you had this fixed from before this release is a sign there should be something in place for this to not happen again. :-)
Thanks!
Jehan
On Sun, Sep 22, 2013 at 9:09 AM, Jehan Pagès wrote:
Hi,
On Mon, Sep 23, 2013 at 12:49 AM, Sven Claussner wrote:
On 22.09.2013 at 12:32 P.M., Jehan Pagès wrote:
Thanks Sven, but that does not say what versions are used on GIMP 2.8.4, official build, which was my question. :-)
Sorry for being a bit terse, I'm in a rush ;-)
You can find the official 2.8.4 build at
Running GIMP with the -v or --version parameter shows the versions of the used libraries.
Oh thanks, I did not know this one! Jernej actually already sent me an archive with the dependency tree of his build. I was planning to check the .pc files. Fortunately I did not start. And your solution will be easier *and* more accurate. :-)
You can also find the 2.8.4 sources at the Web-Git site: https://git.gnome.org/browse/gimp
Yes the source, I already have them, no problem. :-) Thanks again.
Jehan
Kind regards,
Sven
_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List of dependencies (versions and configuration options) for GIMP on Windows
Hi,
On Thu, Sep 26, 2013 at 2:50 PM, Jehan Pagès wrote:
Hi,
On Mon, Sep 23, 2013 at 1:51 AM, Michael Henning wrote:
At the time I fixed this, Jernej's builds did not exhibit the problem because they used an older version of fontconfig. I did not report this upstream because it's a configuration issue, but now that I think about it, the defaults should perhaps be changed on windows (or maybe when cross compiling).
Yes I am not sure if upstream or else, but definitely somethings should be done *somewhere*, otherwise we might have various new developers to the team (or the same ones, forgetting it happened already) scratching their head with this problem every 6 months. The simple fact that the last Windows build is broken even though you had this fixed from before this release is a sign there should be something in place for this to not happen again. :-)
Just for information, I have now opened a report upstream: https://bugs.freedesktop.org/show_bug.cgi?id=69836
Jehan
List of dependencies (versions and configuration options) for GIMP on Windows
Hi,
On Sun, Sep 29, 2013 at 11:19 PM, Jehan Pagès wrote:
Hi,
On Thu, Sep 26, 2013 at 2:50 PM, Jehan Pagès wrote:
Hi,
On Mon, Sep 23, 2013 at 1:51 AM, Michael Henning wrote:
At the time I fixed this, Jernej's builds did not exhibit the problem because they used an older version of fontconfig. I did not report this upstream because it's a configuration issue, but now that I think about it, the defaults should perhaps be changed on windows (or maybe when cross compiling).
Yes I am not sure if upstream or else, but definitely somethings should be done *somewhere*, otherwise we might have various new developers to the team (or the same ones, forgetting it happened already) scratching their head with this problem every 6 months. The simple fact that the last Windows build is broken even though you had this fixed from before this release is a sign there should be something in place for this to not happen again. :-)
Just for information, I have now opened a report upstream: https://bugs.freedesktop.org/show_bug.cgi?id=69836
The font bugs on Windows are still present in GIMP 2.8.8! If we use an older version of fontconfig, Drawoc has a patch all ready for this: build/windows/jhbuild/patches/fontconfig-fix-config-dir.patch Other than that, we can just use fontconfig 2.11.0 (current stable), or over when there will be. Fontconfig has the fix since 2.11.0.
Could we make sure the same process is applied for the Windows nightbuilds (which use the patches in build/windows/) and the releases (which apparently do not)? That makes it less useful to have nightbuilds if we don't even provide the same in a release!
And can something be done for GIMP 2.8.8? Since it has just been out, and that's not a change in GIMP itself, can we update the Windows packages? Or once it is out, we say it is too late? Thanks!
Jehan
Jehan
List of dependencies (versions and configuration options) for GIMP on Windows
Hi,
ok I think I got misleaded. The official Windows package maintainer is
actually Jernej, isn't it?
Anyway see below about the unpatched Windows package.
Jehan
On Wed, Nov 6, 2013 at 11:31 AM, Jehan Pagès wrote:
Hi,
On Sun, Sep 29, 2013 at 11:19 PM, Jehan Pagès wrote:
Hi,
On Thu, Sep 26, 2013 at 2:50 PM, Jehan Pagès wrote:
Hi,
On Mon, Sep 23, 2013 at 1:51 AM, Michael Henning wrote:
At the time I fixed this, Jernej's builds did not exhibit the problem because they used an older version of fontconfig. I did not report this upstream because it's a configuration issue, but now that I think about it, the defaults should perhaps be changed on windows (or maybe when cross compiling).
Yes I am not sure if upstream or else, but definitely somethings should be done *somewhere*, otherwise we might have various new developers to the team (or the same ones, forgetting it happened already) scratching their head with this problem every 6 months. The simple fact that the last Windows build is broken even though you had this fixed from before this release is a sign there should be something in place for this to not happen again. :-)
Just for information, I have now opened a report upstream: https://bugs.freedesktop.org/show_bug.cgi?id=69836
The font bugs on Windows are still present in GIMP 2.8.8! If we use an older version of fontconfig, Drawoc has a patch all ready for this: build/windows/jhbuild/patches/fontconfig-fix-config-dir.patch Other than that, we can just use fontconfig 2.11.0 (current stable), or over when there will be. Fontconfig has the fix since 2.11.0.
Could we make sure the same process is applied for the Windows nightbuilds (which use the patches in build/windows/) and the releases (which apparently do not)? That makes it less useful to have nightbuilds if we don't even provide the same in a release!
And can something be done for GIMP 2.8.8? Since it has just been out, and that's not a change in GIMP itself, can we update the Windows packages? Or once it is out, we say it is too late? Thanks!
Jehan
Jehan
