lode leroy wrote:
Ah, now it starts up, and the Python-fu is there... yippee!
It should do so now out of the box, at least in current CVS... maybe
except for the interp file, but we should be able to fix this today.
And now lets hope some autotools-wizard can deduce from this mail what
needs
On Sunday 26 June 2005 11:19, Michael Schumacher wrote:
lode leroy wrote:
Ah, now it starts up, and the Python-fu is there... yippee!
It should do so now out of the box, at least in current CVS...
maybe except for the interp file, but we should be able to fix this
today.
Joao S. O. Bueno Calligaris wrote:
On Sunday 26 June 2005 11:19, Michael Schumacher wrote:
If you want to continue to work on scripting, and get even more
scripting languages to GIMP on the windows plattform, there is
gimp-perl, some java classes, a ruby binding and iirc even
something for
On 6/24/05, Alan Horkan [EMAIL PROTECTED] wrote:
On Fri, 24 Jun 2005, Michael Schumacher wrote:
Great work! Seems like we will finally have pygimp 2.4 for GIMP 2.4 on each
of the officially supported platforms. Hm, how about letting
Script-Fu/Tiny-Fu die in favor of it? ;)
The best
Python's module mechanism doesn't recognize the dll files as a python
module. Once you solve this (e.g. add or remove the compiler or linker flag
that makes it work or break resp.), it should work.
well, the first problem just now is that there is no .dll resulting from
the autotools
Von: lode leroy [EMAIL PROTECTED]
Aha! So I edited the Makefile, to add the missing path. and now alt least
I have a dll, although its called 'gimpmodule.dll'... suppose I can just
rename that to gimp.dll...
Didn't get a pth file from autotools...
So what am I supposed to do now?
Write
On Fri, 24 Jun 2005, Michael Schumacher wrote:
Great work! Seems like we will finally have pygimp 2.4 for GIMP 2.4 on each
of the officially supported platforms. Hm, how about letting
Script-Fu/Tiny-Fu die in favor of it? ;)
The best thing about Script-Fu has been knowing it would be
