Ok, thanks. So it should work by running btool first, so all libraries are created (no need to debug those) and then just feeding btool make like commands via WinGDB.
If I can make this to work I will create a new wiki page. I think a lot of people will find this useful.
Regards, Tjeerd
On Mon, Mar 2, 2015 at 3:01 AM, Krzysztof Kosiński <tweenk.pl@...1063....> wrote:
2015-03-01 15:29 GMT+01:00 Bit Barrel <bitbarrelmedia@...400...>:
I would like to debug Inkscape on Windows but given the lack of response here, I want to try a different approach. http://sourceforge.net/p/inkscape/mailman/message/33438177/
Our current debugging process on Windows involves simply using commandline GDB. I don't know whether any of our Windows developers figured out how to make everything work in an IDE.
It is possible to debug a linux application on Windows using Visual
Studio
and WinGDB. However, they only support Make, not Btool.
I asked WinGDB for support and this was their reply:
/////////////// WinGDB can work with other build systems than make, but project generation is supported only for make. You should be able to build and debug, though.
You need to change default command lines from 'make' calls to something suitable to build system used. Please consult following sections of the documentation:
http://www.wingdb.com/docs/pages/wg_dev_mingw.htm http://www.wingdb.com/docs/pages/wg_remotebuild.htm
We are not familiar with 'btool' build system, so you need to find out how to call it in order to perform build and clean tasks. /////////////
Anyone know what the btool commands are equivalent to make?
Basically the same as make, but to create a workable application you need to write "btool dist". This will create an "inkscape" directory that contains the main binary and all the required libraries.
Regards, Krzysztof