When weird stuff like that happens, it's usually a sign that you need to do a btool clean, or at least a btool -Drefresh=true. I've learned that the hard way just recently.

I just built 18630 and had no problems, but had done a btool clean just before. My executable is 13,140 KB and the whole inkscape folder is 194Mb, which seems to be smaller than your .exe file. I'm using the latest dev libs from the new modevia svn server - see Bob's recent post - http://www.nabble.com/Win32-devlibs-in-Subversion-td17136562.html

Recent updates in SVN have also changed the buildtool.cpp file, so it might be worth deleting that and rebuilding it - g++ buildtool.cpp -o btool

Cheers,

Rygle.

On today's compile of Inkscape (XP, SVN 18630) I got an unpleasant surprise. My system complains: Program too big to fit in memory with inkscape.exe being 224,113,108 B

This might be a symptom of the thing I found in buildtool last weekend, where multiple substitutions would not be resolved, and it would try to execute something like:

${arch}strip inkscape.exe

If that happened, then it would fail, and inkscape.exe would have all of the debug symbols in it.

Just speculating... but that is fixed now.

bob

Marcin Floryan wrote:

On Fri, May 16, 2008 at 04:44:21AM -0700, rygle wrote:

...

When weird stuff like that happens, it's usually a sign that you need to do a btool clean, or at least a btool -Drefresh=true. I've learned that the hard way just recently.

Thanks Rygle,

As I've mentioned later build clean did help (and I have the latest btool and also the latest dev libs SVN up'ed). So long as it is just some garbage left over a non-clean build than I guess we're all right. I was just simply thinking if this is not a sign of a potential problem we might run into in the future.

Regards,

Marcin Floryan http://marcin.floryan.pl/ [GPG Key ID: 0D5581C5]

https://lists.sourceforge.net/lists/listinfo/inkscape-devel