> >If you are using MSVC, I guess the real question is, is there any
> >chance that we will be able to claim supporting a MSVC build "out of
> >the box" with a straight face?
Hans Breuer writes:
> Probably not, at least not until the issues outlined in
The first issue there is about building fontconfig. Why assume
somebody building *GIMP* with MSVC would want to build *everything* it
depends on, too?
> Though I still have plans to extend Pango to allow
> 'render to bitmap' and 'get glyph outlines' at least with two
> backends (win32 and FT2), there seems to be noone else interested.
Well, at least for me the issue is that I haven't investigated deeply
enough of this to understand your point...
> >almost unmaintained, and requires manual intervention on the builder's
> >system. Is manual editing needed for the makefile.msc files?
> Only if there are files added or removed, so usually not that much
> when getting stable again ...
But surely the current stuff in module.defs, for instance, which
requires you to have the various dependency *sources* unpacked as
siblings to your GIMP source directory, is not a good idea? The
build/win32 stuff should be changed to use pkg-config and *installed*
developer packages of glib, gtk etc.
And that's not only for the glib/gtk/etc sources. For instance,
module.defs has the line: INTL = $(TOP)/gettext-0.10.40/intl even if
the prebuilt binary Win32 distributions of glib etc haven't used
gettext-0.10.40 for ages. The latest gettext-runtime distribution for
Win32 from FSF is what should be used.
Yes, I know that using pkg-config in a nmake makefile is not
straightforward (due to the lack of backticks in the Win32 "shells"),
but it can be done through some hackery involving building indirect
command line option files, and/or building temporary .bat files at
Whenever I look at the stuff in build/win32 I get so depressed and
feel that it should be junked altogether...
> >(If the GIMP's build directory is to be included in tarballs, it should
> >be added to the top Makefile.am.)
> It isn't as noted above, so please don't.
Then the "&build" should be removed from gimp's line in
CVSROOT/modules . Will this have some odd consequences, or can it be
done right away? (It probably should be removed from gtk+'s
CVSROOT/modules line as well.)
Gimp-developer mailing list