wingimp and gtk+ 2
Bryan
I like wingimp 1.2.4, but I think gtk+ 1.3 is ugly. :-(
Is it possible to use the windows gtk+ 2 with wingimp?
If not, why has the switch not been made for the windows port of gimp?
Thank you ;)
Olivier Ripoll
It will soon (a few months, not a few weeks) be possible to make use of
gtk2 with the Windows BUILD(*) of Gimp, but this will be for gimp 1.4,
which does not exist yet, although gimp 1.3.x starts to look and act very
well.
But, until gimp 1.4 appears, the old look of gtk 1.x will be the only one
for gimp 1.2.3 and the soon to be released gimp 1.2.4.
Regards,
Olivier.
(*) "Build" and not "port", because the source code is the same now. The
only difference is the platform the binaries are compiled/built on.
Ann Lee
visit
http://gug.sunsite.dk/forums/?threadid=820
AJB 2K3 is one of my names.
had had repoted this possible .
"Olivier Ripoll" <olivier...@unine.ch> wrote in message
news:3E632578...@unine.ch...
Bryan
> gtk2 with the Windows BUILD(*) of Gimp, but this will be for gimp 1.4,
> which does not exist yet, although gimp 1.3.x starts to look and act very
> well.
>
> But, until gimp 1.4 appears, the old look of gtk 1.x will be the only one
> for gimp 1.2.3 and the soon to be released gimp 1.2.4.
>
> Regards,
>
> Olivier.
>
> (*) "Build" and not "port", because the source code is the same now. The
> only difference is the platform the binaries are compiled/built on.
the source is the same now? So, is it possible to use CVS to checkout the
source for gimp 1.4 and compile it for windows? I'm running Gimp CVS on my
linux machine, i prefer it over wingimp 1.2.4. I don't expect the windows
build of gimp to be as good or stable, but I also find wingimp to crash
more. :(
Tor Lillqvist
> the source is the same now? So, is it possible to use CVS to checkout the
> source for gimp 1.4 and compile it for windows?
He was talking about the source for the 1.2.x branch, which has been the
same all the time, except for some ugly details in the Windows build,
that I used to have only on my machine (and in the source zipfiles I
made available). But these details (that were committed to CVS just some
weeks ago) were in no way essential for building GIMP 1.2.x on Windows.
I.e. it hasn't in some magical way become easier to build GIMP 1.2.x on
Windows just because I have committed to CVS those hacks I previously
considered too ugly to have in the official sources. You could have done
it before, too.
As for the HEAD branch, i.e. what will eventually become GIMP 1.4: Yes,
it is possible to build it on Windows. I have only had time to do it
once in a month or so, so with the fast pace of development it is
possible that buildability has broken in some minor way since I last had
a look.
And before somebody asks: No, I am not going to provide binaries of GIMP
1.3.x before 1.4 has been released.
--tml
Phil Harper
how complicated would it be to build GIMP 1.3.x on win32 with mingw?
are there any major changes i would need to make?
Phil.
Bryan
"Phil Harper" <philh...@hotmail.com> wrote in message
news:c2d34e16.0303...@posting.google.com...
I'm interested in knowing the same.
I would like to go about compiling gimp 1.4 cvs for windows myself, since
you won't provide binaries (i don't blame you)
buuuuuut i've never taken such an undertaking in windows, and i'm not
totally sure that a cvs checkout would compile correctly for windows
out-of-the-box, if anyone could provide more information, I would be very
thankful!
Michael Schumacher
> I'm interested in knowing the same.
> I would like to go about compiling gimp 1.4 cvs for windows myself, since
> you won't provide binaries (i don't blame you)
> buuuuuut i've never taken such an undertaking in windows, and i'm not
> totally sure that a cvs checkout would compile correctly for windows
> out-of-the-box, if anyone could provide more information, I would be very
> thankful!
AFAIK, there is no configure script in CVS, so you'll have to create it
yourself with autoconf. I don't know if this is supposed to work, but I
never managed to get a working configure out of it.
There is a configure script in the snapshots (GIMP 1.3.11, GIMP 1.3.12), and
I got pretty far using it. I had to remove some strange '^A's from
the Makefiles, but after that, compilation ran smooth. There were some
linking problems that made me stop because I ran out of time, but it should
be possible to solve them.
HTH,
Michael
--
schumamls Netzpl@zle: http://schumaml.gmxhome.de
Tor Lillqvist
> I would like to go about compiling gimp 1.4 cvs for windows myself, since
> you won't provide binaries (i don't blame you)
> buuuuuut i've never taken such an undertaking in windows, and i'm not
> totally sure that a cvs checkout would compile correctly for windows
> out-of-the-box, if anyone could provide more information, I would be very
> thankful!
First learn to build it on Linux. Then, when you have a rough
understanding what the auto* tools and libtool do, try it on Windows.
You might be able to use Cygwin's default auto* tools. but most probably
you will need to fetch and install a rather recent version of libtool.
You could also try MSYS.
A useful hint: As you presumably will use a mixture of Cygwin-based
tools (shell, m4, awk, perl) and native Win32 ones (mingw, binutils),
you should make sure that you have all the developer packages and the
GIMP source files in such paths that the same path is valid both from
Cygwin's and Win32's perspective. I.e. keep everything on the same
drive, and make sure the top-level Windows folders in question are
visible in Cygwin also as top-level directories. If you use MSYS this
shouldn't be an issue.
If nothing of the above makes any sense to you, forget it.
--tml