Sven: Try one of the builds from September 12 or later. There were some crashes being caused by a specific version of cairo that I was building with. I switched cairo versions, and now those crashes should be gone. If that doesn't help, I'll make a debug build for you. (I have plans to make the debug builds happen every night as well, I just haven't gotten around to it yet.) Jari: The mkarchive script has code to remove unneeded files. In mkarchive, comment out line 63, which should say "rm -rf $f" and then run mkarchive. Then, in targets/combined you should see a folder. That folder contains the GIMP, with all unnecessary files removed. -- drawoc On Wed, Sep 12, 2012 at 3:14 PM, scl <scl.gplus@xxxxxxxxx> wrote: > On 09.08.12 at 10:09 pm drawoc wrote: >> I've set up a machine to do start doing nightly builds of the GIMP for >> Windows. >> >> Anyone who's interested can find them here: >> http://nightly.darkrefraction.com/gimp/ > > > Thanks, drawoc, for the nightly builds. This makes it easier to detect and > report bugs before a release. > Unfortunately your builds don't contain debug symbols. So in case of a crash > a post-mortem-analysis can't be done. > A current example is bug #682742. I encountered a crash when trying to edit > the module settings (Edit/Modules). Due to missing debug symbols the > stacktrace [1] is completely useless. Can you include debug symbols, please? > I'd personally prefer PDB format for Visual Studio, if it's possible to do > that. > > Thank you, > > Sven > > > > [1] https://bugzilla.gnome.org/show_bug.cgi?id=682742#c9 > > _______________________________________________ > gimp-developer-list mailing list > gimp-developer-list@xxxxxxxxx > https://mail.gnome.org/mailman/listinfo/gimp-developer-list _______________________________________________ gimp-developer-list mailing list gimp-developer-list@xxxxxxxxx https://mail.gnome.org/mailman/listinfo/gimp-developer-list
