Re: [Gimp-developer] gimp-perl-cvs status
On Wed, Jul 23, 2003 at 03:33:55PM -0400, Carol Spears [EMAIL PROTECTED] wrote: i am going to spend some time at my moms early next week. this might be one of those cool occasions where i can have the perl I got it working with tml's native build, linking msvcrt and cygwin.dll into the same process (does not work, but actually works) I'll check in a README.win32 soon that describes very roughly what I did. *However* you would better allocate a few days to it. Apart from the compile speed (gcc on win32 compiles 5-10times slower on my machine than under linux), you need quite a lot of time selecting the right toolset and gtk version (there are *many* different gtk+ versions). I'd even recommend against it at this stage, and leave it somebody else to prepare a distribution once 2.0 is out.. :) what is the chances that the gimp perl plugins can run be running on my moms window box next monday evening? close to zero. -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | | ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl-cvs status
[EMAIL PROTECTED] ( Marc) (A.) (Lehmann ) writes: is it worth building the gimp-perl module from cvs yet? Depends on what you are needing it for. The evrsion in CVS seems to be fully working, except that none of the examples that use their own Gtk+ interface have been converted to gtk2 yet, and coredump. gtk2-perl binding is quite usuable now and conversion is not so difficult. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl-cvs status
[EMAIL PROTECTED] ( Marc) (A.) (Lehmann ) wrote: On Tue, Jul 22, 2003 at 02:51:16PM -0400, Carol Spears [EMAIL PROTECTED] wrote: is it worth building the gimp-perl module from cvs yet? Depends on what you are needing it for. The evrsion in CVS seems to be fully working, except that none of the examples that use their own Gtk+ interface have been converted to gtk2 yet, and coredump. Also, many constants have different names in 2.0, and, although I hopefully renamed them in the plug-ins, I certainly didn't test all the plug-ins. There are also certainly some edges, but you should be able to work with it quite nicely. And if some plug-ins don't work just delete them. (I even built it on windows for fun.. and as I though, no sourcecode changes were required, although I built with cygwin using gtk+2-win32) thats awesome. gimp-perl is broken right now for gimp-1.2, i get this message from gimp that if i am elite enough to use threading, then i am elite enough to fix it. i think if i pin perl from woody, i am elite enough to fix it. also, i really really never ever thought that gimp-perl would be available for wingimp. i am also impressed that you can send all that mail and still get things done. thank you carol ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl-cvs status / wingimp
On Wed, Jul 23, 2003 at 09:47:37AM -0400, Carol Spears [EMAIL PROTECTED] wrote: get this message from gimp that if i am elite enough to use threading, then i am elite enough to fix it. ;) i think if i pin perl from woody, i am elite enough to fix it. The problem is that debian woody uses an experimental and very very broken option when compiling their perl, namely the 5.005 threading model. It's known not to work with gimp or many other modules, and since it's explicitly flagged as experimental people really wonder why debian chose to enable it. The perl from testing or unstable (one of them has 5.008) should work. (Please note that it explicitly says that it is a warning only, doesn't mention elite anywhere and all that is requested is to not send complaints when it breaks, as you have been warned). also, i really really never ever thought that gimp-perl would be available for wingimp. The problem is that there seem to be two modes of building gimp or gtk+2, the using unix-like tools, and the (standard!) one. You could have the first (easy, for unixians) way with gtk1, too, but then gimp would only run with an X11 server. Gtk+2 can be built with the normal win32 backend even under cygwin now. That might not be the platform that people want (no nice installer etc.), which is why I think it will take some time until all this works out of the box. gimp-perl would need to be modified in it's config mechanism since the 1.2 wingimp doesn't provide the configuration framework needed. I do not know wether this will be true for the 2.0 version, but I suspect it will (?). while gimp-perl-1.2 could be modified, all hopes are gone when it comes to Gtk1. The situation is very different to gtk+2, though, since standard cygwin builds are available and useful and support pkgconfig. The build framework of Gtk+2-perl is also working with that. So, getting gimp-perl-1.3 Gtk+2 and gimp working under windows is just a matter of a lot of time and patience. -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | | ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl-cvs status
[EMAIL PROTECTED] ( Marc) (A.) (Lehmann ) wrote: On Tue, Jul 22, 2003 at 02:51:16PM -0400, Carol Spears [EMAIL PROTECTED] wrote: is it worth building the gimp-perl module from cvs yet? Depends on what you are needing it for. The evrsion in CVS seems to be fully working, except that none of the examples that use their own Gtk+ interface have been converted to gtk2 yet, and coredump. Also, many constants have different names in 2.0, and, although I hopefully renamed them in the plug-ins, I certainly didn't test all the plug-ins. There are also certainly some edges, but you should be able to work with it quite nicely. And if some plug-ins don't work just delete them. (I even built it on windows for fun.. and as I though, no sourcecode changes were required, although I built with cygwin using gtk+2-win32) i am going to spend some time at my moms early next week. this might be one of those cool occasions where i can have the perl plugins working on wingimp and not on my elite debian gnu/linux box cvs gimp build. is that cool or what? do you think there might be something to show her while i am there? i will warn you, i am having a whippet party with my good friend szell earlier this day, so i will not be as clear thinking as usual. what is the chances that the gimp perl plugins can run be running on my moms window box next monday evening? carol ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl-cvs status / wingimp
[EMAIL PROTECTED] ( Marc) (A.) (Lehmann ) wrote: On Wed, Jul 23, 2003 at 09:47:37AM -0400, Carol Spears [EMAIL PROTECTED] wrote: get this message from gimp that if i am elite enough to use threading, then i am elite enough to fix it. ;) i think if i pin perl from woody, i am elite enough to fix it. The problem is that debian woody uses an experimental and very very broken option when compiling their perl, namely the 5.005 threading model. It's known not to work with gimp or many other modules, and since it's explicitly flagged as experimental people really wonder why debian chose to enable it. The perl from testing or unstable (one of them has 5.008) should work. (Please note that it explicitly says that it is a warning only, doesn't mention elite anywhere and all that is requested is to not send complaints when it breaks, as you have been warned). also, i really really never ever thought that gimp-perl would be available for wingimp. The problem is that there seem to be two modes of building gimp or gtk+2, the using unix-like tools, and the (standard!) one. You could have the first (easy, for unixians) way with gtk1, too, but then gimp would only run with an X11 server. Gtk+2 can be built with the normal win32 backend even under cygwin now. That might not be the platform that people want (no nice installer etc.), which is why I think it will take some time until all this works out of the box. gimp-perl would need to be modified in it's config mechanism since the 1.2 wingimp doesn't provide the configuration framework needed. I do not know wether this will be true for the 2.0 version, but I suspect it will (?). while gimp-perl-1.2 could be modified, all hopes are gone when it comes to Gtk1. The situation is very different to gtk+2, though, since standard cygwin builds are available and useful and support pkgconfig. The build framework of Gtk+2-perl is also working with that. So, getting gimp-perl-1.3 Gtk+2 and gimp working under windows is just a matter of a lot of time and patience. sorry, i hadn't read this before mussing on getting those plugins to my moms computer. i didn't complain about the warning and the problem. i guess i even knew how to fix it. please ignore the email i most recently sent. carol ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] gimp-perl-cvs status
On Tue, Jul 22, 2003 at 02:51:16PM -0400, Carol Spears [EMAIL PROTECTED] wrote: is it worth building the gimp-perl module from cvs yet? Depends on what you are needing it for. The evrsion in CVS seems to be fully working, except that none of the examples that use their own Gtk+ interface have been converted to gtk2 yet, and coredump. Also, many constants have different names in 2.0, and, although I hopefully renamed them in the plug-ins, I certainly didn't test all the plug-ins. There are also certainly some edges, but you should be able to work with it quite nicely. And if some plug-ins don't work just delete them. (I even built it on windows for fun.. and as I though, no sourcecode changes were required, although I built with cygwin using gtk+2-win32) -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | | ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
