btool slower to link with recent devlibs on Windows (32 bit)
Hi all,
Finally had a chance to update things on my Windows XP 32 bit build box. Devlibs 53 -> 61 and now current inkscape trunk. I'm observing that the link stage is taking a very, very, Very long time to complete. Many minutes. I do not recall it taking that long previously.
Am I hallucinating or is it really slower than it used to be? Is there an easy way to disable the build for inkview, so that I can at least not have to wait for that progam's equally slow link?
Also I have forgotten the trick to get btool to show what it is doing when it compiles a module. That is, to show the cxx line rather than
compile (modulename)
Finally, gdb seems to be more hit and miss than I remembered. Doing it this way:
gdb file inkscape/inkscape.exe inkscape/inkscape.dbg # set break point here run /c/temp/test2.emf
is doing strange things. The break points will not always set. Sometimes it says that it doesn't see the file (emf-inout.c) and other times that it does not see the line specified. build.xml was modified with -O2 -> -O0, so nothing should have been optimized away. Yet other times, it works as one would expect. Also when it segfaults "bt" is wildly uninformative. For the case at hand it is >600 levels deep and each level is just described by a few numbers - no file or module names are shown.
Thanks,
David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech
Am 03.03.2016 um 01:58 schrieb mathog:
Hi all,
Finally had a chance to update things on my Windows XP 32 bit build box. Devlibs 53 -> 61 and now current inkscape trunk. I'm observing that the link stage is taking a very, very, Very long time to complete. Many minutes. I do not recall it taking that long previously.
Am I hallucinating or is it really slower than it used to be? Is there an easy way to disable the build for inkview, so that I can at least not have to wait for that progam's equally slow link?
Use "btool dist-inkscape -file build.xml" to only link inkscape.exe and inkscape.com. You could define another <target> in "build.xml" to also exclude linking the console version.
Also I have forgotten the trick to get btool to show what it is doing when it compiles a module. That is, to show the cxx line rather than
compile (modulename)
I'm not aware of such an option. The file "compile.lst" in the root directory contains all the command lines as well as stdout/stderr of the last btool run, though.
Finally, gdb seems to be more hit and miss than I remembered. Doing it this way:
gdb file inkscape/inkscape.exe inkscape/inkscape.dbg # set break point here run /c/temp/test2.emf
is doing strange things. The break points will not always set. Sometimes it says that it doesn't see the file (emf-inout.c) and other times that it does not see the line specified. build.xml was modified with -O2 -> -O0, so nothing should have been optimized away. Yet other times, it works as one would expect. Also when it segfaults "bt" is wildly uninformative. For the case at hand it is >600 levels deep and each level is just described by a few numbers - no file or module names are shown.
Thanks,
David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech
Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
participants (2)
-
Eduard Braun -
mathog