Re: [Gimp-developer] gimp-cvs on msys/mingw

2005-07-06 Thread Michael Schumacher
 Von: lode leroy [EMAIL PROTECTED]

 Looking at cvs.sf.net, ftruncate is still defined in unistd.h,
 but it was added after the release I was using.

Well, they provide updates as well - and installing them is recommended :)

BTW, does anyone know what exactly the MinGwPORT stuff is about? Is it the
start of a package management system?

HTH,
Michael

-- 
5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail
+++ GMX - die erste Adresse für Mail, Message, More +++
___
Gimp-developer mailing list
Gimp-developer@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-cvs on msys/mingw

2005-07-06 Thread Tor Lillqvist
Michael Schumacher writes:
  BTW, does anyone know what exactly the MinGwPORT stuff is about? Is
  it the start of a package management system?

As far as I have been able to figure out, it's a way to package a
patch and pre- and post-build scripts to automate building something
from a pristine source tarball. No version or dependency tracking or
database of what's installed and where etc is involved, AFAICS. No
binary distribution packaging either. So it's not a package management
system. (Or maybe it's an early start of a such, although why invent
yet another format instead of trying to port dpkg or rpm seems odd.)

--tml

___
Gimp-developer mailing list
Gimp-developer@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-cvs on msys/mingw

2005-07-05 Thread michael chang
On 7/5/05, Tor Lillqvist [EMAIL PROTECTED] wrote:
 lode leroy writes:
   ftruncate is not present in my version of mingw, so I changed it to make it
   compile.
 
 Why don't you upgrade to a more recent version then? (Or have they
 dropped their inline ftruncate() implementation in unistd.h from
 bleeding-edge versions?)
 

MinGW/MSYS comes in about 20 or so different packages, which can be
confusing to install.  Did you install everything binary from
MSYS/MinGW?  If not, then we might have to go figure out which
MinGW/MSYS components are prequesites to installing The GIMP.

-- 
~Mike
___
Gimp-developer mailing list
Gimp-developer@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-cvs on msys/mingw

2005-07-05 Thread Tor Lillqvist
michael chang writes:
  MinGW/MSYS comes in about 20 or so different packages, which can be
  confusing to install.

Umm, isn't it more like half a dozen? From memory: gcc, binutils, gdb,
w32api, msys, maybe the msysDTK (or whatever it was called, the
package that contains the auto* support stuff if one needs that).

  Did you install everything binary from MSYS/MinGW? 

Only the parts I needed. Not the Fortran or Objective C compilers, for
instance.

--tml

___
Gimp-developer mailing list
Gimp-developer@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-cvs on msys/mingw

2005-06-29 Thread lode leroy




From: Manish Singh [EMAIL PROTECTED]
Reply-To: Manish Singh [EMAIL PROTECTED]
To: michael chang [EMAIL PROTECTED]
CC: lode leroy 
[EMAIL PROTECTED],gimp-developer@lists.xcf.berkeley.edu

Subject: Re: [Gimp-developer] gimp-cvs on msys/mingw
Date: Tue, 28 Jun 2005 09:45:38 -0700

On Tue, Jun 28, 2005 at 12:40:37PM -0400, michael chang wrote:
 On 6/28/05, Manish Singh [EMAIL PROTECTED] wrote:

  Changing stuff outside of gimp should be considered last resort.
 
   which is still not perfect: I modified python.m4 to replace \es by 
/es:

  
  [am_cv_python_pythondir=`$PYTHON -c from distutils import 
sysconfig;

   print
   
sysconfig.get_python_lib(0,0,prefix='$PYTHON_PREFIX').replace('\\','/')

   2/dev/
   null ||
 
  Why is this needed at all? gimp doesn't use $pythondir anywhere.

 I don't know, but maybe this has something to do with python-fu or
 whatever it is [scripting in The GIMP with Python, as opposed to e.g.
 Perl or Script-Fu].  IIRC, some info about Python-Fu building on Win32
 just came through the gimp-devel list, so... *shrugs*


yes. my info on compiling gimp from cvs :-)



Uh, that's what this thread is about, pygimp on Win32.



This is indeed needed to compile the pygimp plugin on Win32/MSYS/MinGW.

This particular test determines the libraries needed to link agains 
libpython.

the result is c:\Python24\Lib\site-packages.

MSYS (especially sh.exe) expects that to be c:/Python24/Lib/site-packages.


The point being, $pythondir isn't used by the pygimp build stuff at all,
so changing the above automake stuff won't actually do anything.

-Yosh



___
Gimp-developer mailing list
Gimp-developer@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-cvs on msys/mingw

2005-06-29 Thread lode leroy




From: Manish Singh [EMAIL PROTECTED]
On Tue, Jun 28, 2005 at 11:31:48AM +0200, lode leroy wrote:

...

Your libwmf library is too old. Upgrade.


will do. I just took the stuff from tml's gimp-for-windows page


 the autodetection of python on MSYS is not too good:
 the \es need to be replaced with /es, so I added this to

Where did it screw up? You sure you are using a CVS snapshot with all
the relevant changes? The ChangeLog should have:


MSYS (especially sh.exe) needs / instead of \ in the paths.
Printing paths from python (in pythondev.m4 and 
/usr/share/aclocal-1.9/python.m4)



 C:\Python24\lib\site-packages\site-customize.py
Changing stuff outside of gimp should be considered last resort.


I do not see an alternative: /usr/share/aclocal-1.9/python.m4 is not part of 
gimp,

but is used via aclocal...

 which is still not perfect: I modified python.m4 to replace \es by 
/es:


[am_cv_python_pythondir=`$PYTHON -c from distutils import sysconfig; 
print

 sysconfig.get_python_lib(0,0,prefix='$PYTHON_PREFIX').replace('\\','/')
 2/dev/ null ||

Why is this needed at all? gimp doesn't use $pythondir anywhere.


this particular test is used to detect the LDFLAGS to link pygimp against 
libpython


-- lode


___
Gimp-developer mailing list
Gimp-developer@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-cvs on msys/mingw

2005-06-29 Thread Manish Singh
On Wed, Jun 29, 2005 at 09:02:54AM +0200, lode leroy wrote:
  the autodetection of python on MSYS is not too good:
  the \es need to be replaced with /es, so I added this to
 
 Where did it screw up? You sure you are using a CVS snapshot with all
 the relevant changes? The ChangeLog should have:
 
 MSYS (especially sh.exe) needs / instead of \ in the paths.
 Printing paths from python (in pythondev.m4 and 
 /usr/share/aclocal-1.9/python.m4)

Yes, and the configure script should take care of this. This is why I
asked for confirmation that you have all the stuff needed for this to
work (which you did not answer).
 
  C:\Python24\lib\site-packages\site-customize.py
 Changing stuff outside of gimp should be considered last resort.
 
 I do not see an alternative: /usr/share/aclocal-1.9/python.m4 is not part 
 of gimp,
 but is used via aclocal...

Except the stuff you changed isn't used in the build...
 
  which is still not perfect: I modified python.m4 to replace \es by 
 /es:
 
 [am_cv_python_pythondir=`$PYTHON -c from distutils import sysconfig; 
 print
  sysconfig.get_python_lib(0,0,prefix='$PYTHON_PREFIX').replace('\\','/')
  2/dev/ null ||
 
 Why is this needed at all? gimp doesn't use $pythondir anywhere.
 
 this particular test is used to detect the LDFLAGS to link pygimp against 
 libpython

But $pythondir isn't used in LDFLAGS. $PYLINK_LIBS is used, and the
backslash to forward slash transformation is performed on this.

If you're having to make changes to these files, it sounds like you're
not using current enough sources.

-Yosh
___
Gimp-developer mailing list
Gimp-developer@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-cvs on msys/mingw

2005-06-29 Thread lode leroy




From: Manish Singh [EMAIL PROTECTED]
Yes, and the configure script should take care of this. This is why I
asked for confirmation that you have all the stuff needed for this to
work (which you did not answer).


I did run cvs update, and it did compile.


...
Except the stuff you changed isn't used in the build...


I have now reverted my changes to
/usr/share/aclocal-1.9/python.m4, 
C:\Python24\lib\site-packages\site-customize.py

and m4macros/pythondev.m4
and re-ran autogen...



If you're having to make changes to these files, it sounds like you're
not using current enough sources.


and indeed my modifications are no longer needed.



-Yosh


Thanks for adding support for msys to the gimp build files, yosh!

Sorry about the noise.

-- lode


___
Gimp-developer mailing list
Gimp-developer@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-cvs on msys/mingw

2005-06-28 Thread Michael Schumacher
 Von: lode leroy [EMAIL PROTECTED]
 
 some hints and remarks for building gimp-2.3.1+ from cvs
 
 ftruncate is not present in my version of mingw, so I changed it to make
 it compile.

 Maybe this should be autodetected by configure as
 HAVE_WIN32_FTRUNCATE
 or maybe glib should provide g_ftruncate to wrap the platform-specific 
 implementation...

There has been some confusion about this in glib and mingw. We shouldn't
change anything without talking to the glib developers.

 the autodetection of python on MSYS is not too good:
 the \es need to be replaced with /es, so I added this to

We took care of this in the GIMP build environment, but fixing it on the
Python level is better, of course - especially as paths with forward slashes
are valid at the Windows API level as well.


Michael

-- 
5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail
+++ GMX - die erste Adresse für Mail, Message, More +++
___
Gimp-developer mailing list
Gimp-developer@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer


Re: [Gimp-developer] gimp-cvs on msys/mingw

2005-06-28 Thread michael chang
On 6/28/05, Manish Singh [EMAIL PROTECTED] wrote:

 Changing stuff outside of gimp should be considered last resort.
 
  which is still not perfect: I modified python.m4 to replace \es by /es:
 
 [am_cv_python_pythondir=`$PYTHON -c from distutils import sysconfig;
  print
  sysconfig.get_python_lib(0,0,prefix='$PYTHON_PREFIX').replace('\\','/')
  2/dev/
  null ||
 
 Why is this needed at all? gimp doesn't use $pythondir anywhere.
 
 -Yosh
 ___
 Gimp-developer mailing list
 Gimp-developer@lists.xcf.berkeley.edu
 http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
 

I don't know, but maybe this has something to do with python-fu or
whatever it is [scripting in The GIMP with Python, as opposed to e.g.
Perl or Script-Fu].  IIRC, some info about Python-Fu building on Win32
just came through the gimp-devel list, so... *shrugs*

-- 
~Mike
___
Gimp-developer mailing list
Gimp-developer@lists.xcf.berkeley.edu
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer