Jernej Simon i (jernej@xxxxxx) wrote (in part) (on 2009-02-23 at 08:13): > On 23. februar 2009, 3:08:08, Alec Burgess wrote: > > > > Is there any way that Jernej could provide a debug-enabled exe > for GIMP > > > 2.7 win32 or do attempts to report bugs just get in the way of > the > > > "real" work being done by those competent to deal with them? > > All unstable releases of GIMP (those, that have "I won't bug > developers" checkbox) are unstripped, and should contain debugging > symbols (though I think I forgot to remove -O2 from CFLAGS for the > current 2.7.0 build - I'll provide another build soon). The release I got was: gimp-2.7.0-r28042-i686-setup.exe from (I think): http://sourceforge.net/project/showfiles.php?group_id=121075&package_id=240554 That file now longer is available there - it still shows up in the Google cache: http://74.125.95.132/search?q=cache:EhGRmoW3i74J:sourceforge.net/project/showfiles.php%3Fgroup_id%3D121075%26package_id%3D240554+gimp-2.7.0-r28042-i686-setup&hl=en&ct=clnk&cd=2 The current version of that page now shows: GIMP 2.7.0 (SVN rev.28070) + GTK+ 2.14.7 no setup.exe files, just three babl, gegl and gimp tar.lzma files which I assume (?) are source files. Am I looking in the correct place but just jumping the gun because you haven't yet created the expected setup.exe file? Is an RSS-feed watch on that page the correct way to find out when you have created a new win32 build? -- Regards ... Alec (buralex@gmail & WinLiveMess - alec.m.burgess@skype) |
_______________________________________________ Gimp-user@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user