Hi all,
The win32 devlibs have just been updated (rev. 54) to fix the following reports: - Bug #1530286 "Inkscape fails to build on Window with GC errors", - Bug #1156664 "Compile against external libpotrace".
The build.xml files also changed in rev. 14559, so don't forget to update the devlibs and run "btool clean" before compiling!
Regards, -- Nicolas
Hi Nicolas,
Thanks for taking care of this. I wonder if you have time to look into updating Poppler too? At the moment, we have a lot of conditionally-built code to support ancient Poppler versions... Devlibs is really the only blocker for getting rid of it.
Thanks,
AV
On 1 January 2016 at 07:36, Nicolas Dufour <nicoduf@...48...> wrote:
Hi all,
The win32 devlibs have just been updated (rev. 54) to fix the following reports:
- Bug #1530286 "Inkscape fails to build on Window with GC errors",
- Bug #1156664 "Compile against external libpotrace".
The build.xml files also changed in rev. 14559, so don't forget to update the devlibs and run "btool clean" before compiling!
Regards,
Nicolas
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi ALex (and all!),
Le Samedi 2 janvier 2016 16h44, Alex Valavanis <valavanisalex@...400...> a écrit :
Thanks for taking care of this. I wonder if you have time to look into updating Poppler too? At the moment, we have a lot of conditionally-built code to support ancient Poppler versions... Devlibs is really the only blocker for getting rid of it.
Poppler updated (with poppler-0.39.0 and poppler-data-0.4.7) in the devlibs, rev. 56. Inkscape also updated (changes in build.xml) in the trunk (rev. 14566) and 0.91.x branch (rev. 13853).
Now that the devlibs have the latest poppler version, I guess you can now remove some unnecessary code.
@Windows users - again, don't forget to update the devlibs and run "btool clean" before compiling!
Regards, -- Nicolas
That's great. Thanks for all your hard work! I'll tidy up the poppler and gc code accordingly.
AV On 8 Jan 2016 9:02 a.m., "Nicolas Dufour" <nicoduf@...48...> wrote:
Hi ALex (and all!),
Le Samedi 2 janvier 2016 16h44, Alex Valavanis <valavanisalex@...400...> a écrit :
Thanks for taking care of this. I wonder if you have time to look into updating Poppler too? At the moment, we have a lot of conditionally-built code to support ancient Poppler versions... Devlibs is really the only blocker for getting rid of it.
Poppler updated (with poppler-0.39.0 and poppler-data-0.4.7) in the devlibs, rev. 56. Inkscape also updated (changes in build.xml) in the trunk (rev. 14566) and 0.91.x branch (rev. 13853).
Now that the devlibs have the latest poppler version, I guess you can now remove some unnecessary code.
@Windows users - again, don't forget to update the devlibs and run "btool clean" before compiling!
Regards,
Nicolas
libcdr (Corel Draw importer) and libvisio (MS-Visio importer) just updated in devlibs r57 and r58. Both libraries now depend on a new librevenge library, added r57. Please update your devlibs!
Regards, -- Nicolas
Hi Nicolas,
great work!
Did you also consider giving the 64bit devlibs some love while you're at it?
Best Regards, Eduard
Am 08.01.2016 um 10:01 schrieb Nicolas Dufour:
Hi ALex (and all!),
Le Samedi 2 janvier 2016 16h44, Alex Valavanis <valavanisalex@...400...> a écrit :
Thanks for taking care of this. I wonder if you have time to look into updating Poppler too? At the moment, we have a lot of conditionally-built code to support ancient Poppler versions... Devlibs is really the only blocker for getting rid of it.
Poppler updated (with poppler-0.39.0 and poppler-data-0.4.7) in the devlibs, rev. 56. Inkscape also updated (changes in build.xml) in the trunk (rev. 14566) and 0.91.x branch (rev. 13853).
Now that the devlibs have the latest poppler version, I guess you can now remove some unnecessary code.
@Windows users - again, don't forget to update the devlibs and run "btool clean" before compiling!
Regards,
Nicolas
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Oh, and I assume you would make a lot of people very happy when addressing https://bugs.launchpad.net/inkscape-devlibs/+bug/1335954 (The current version of Cairo in the devlibs is too old so gradient meshes won't work)
Don't know how much work this needs, though, so please only see it as suggestion.
Regards, Eduard
Am 10.01.2016 um 22:57 schrieb Eduard Braun:
Hi Nicolas,
great work!
Did you also consider giving the 64bit devlibs some love while you're at it?
Best Regards, Eduard
Am 08.01.2016 um 10:01 schrieb Nicolas Dufour:
Hi ALex (and all!),
Le Samedi 2 janvier 2016 16h44, Alex Valavanis <valavanisalex@...400...> a écrit :
Thanks for taking care of this. I wonder if you have time to look into updating Poppler too? At the moment, we have a lot of conditionally-built code to support ancient Poppler versions... Devlibs is really the only blocker for getting rid of it.
Poppler updated (with poppler-0.39.0 and poppler-data-0.4.7) in the devlibs, rev. 56. Inkscape also updated (changes in build.xml) in the trunk (rev. 14566) and 0.91.x branch (rev. 13853).
Now that the devlibs have the latest poppler version, I guess you can now remove some unnecessary code.
@Windows users - again, don't forget to update the devlibs and run "btool clean" before compiling!
Regards,
Nicolas
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
I provided the 64-bit devlibs in the past and can provide updates if needed.
Of course, one can simply download my latest GIMP 2.9.3 build and simply extract the Frameworks folder to get the latest 64-bit DLLs.
Thanks, Partha
On Sun, Jan 10, 2016 at 7:12 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Oh, and I assume you would make a lot of people very happy when addressing https://bugs.launchpad.net/inkscape-devlibs/+bug/1335954 (The current version of Cairo in the devlibs is too old so gradient meshes won't work)
Don't know how much work this needs, though, so please only see it as suggestion.
Regards, Eduard
Am 10.01.2016 um 22:57 schrieb Eduard Braun:
Hi Nicolas,
great work!
Did you also consider giving the 64bit devlibs some love while you're at it?
Best Regards, Eduard
Am 08.01.2016 um 10:01 schrieb Nicolas Dufour:
Hi ALex (and all!),
Le Samedi 2 janvier 2016 16h44, Alex Valavanis <valavanisalex@...400...> a écrit :
Thanks for taking care of this. I wonder if you have time to look into updating Poppler too? At the moment, we have a lot of conditionally-built code to support ancient Poppler versions... Devlibs is really the only blocker for getting rid of it.
Poppler updated (with poppler-0.39.0 and poppler-data-0.4.7) in the devlibs, rev. 56. Inkscape also updated (changes in build.xml) in the trunk (rev. 14566) and 0.91.x branch (rev. 13853).
Now that the devlibs have the latest poppler version, I guess you can now remove some unnecessary code.
@Windows users - again, don't forget to update the devlibs and run "btool clean" before compiling!
Regards,
Nicolas
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi,
Le Dimanche 10 janvier 2016 22h57, Eduard Braun <Eduard.Braun2@...173...> a écrit :
Did you also consider giving the 64bit devlibs some love while you're at it?
My main computer is on Xubuntu 15.10, and I only have one official Windows XP (32bit) license, installed in a Virtualbox -mainly for testing Inkscape and updating devlibs. But I have no 64bit Windows that I could use to work on 64bit devlibs, sorry.
#### That said, we currently rely on a quite old TDM-GCC 4.6 version, and updating the devlibs is a manual and tedious process. It would be great if we could improve the way we maintain our devlibs, and somewhat automate it if possible. I'm currently investigating some possibilities, and MSYS2 (sourceforge.net/projects/msys2/) seems to be a good one -it already provides some of our dependencies (and, well, Inskcape 0.91 itself, see http://sourceforge.net/p/msys2/wiki/Packages/) and gives nice tools to build custom packages. Of course, we can also use TDM-GCC-5.1 with MSYS or maybe with MSYS2. Or use cross-compiled libraries such as the ones provided by OpenSuse (my old gtk3 test branch still works, see https://code.launchpad.net/~inkscape.dev/inkscape-devlibs/devlibs-gtk3). To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs?
There are some points we need to take into consideration (I probably forgot some): * The new devlibs must be easier to maintain compared to the current ones. * It should be possible to use the same steps to update win32 and win64 devlibs. * If both devlibs could provide exactly the same packages versions, it would greatly help bug tracking (and fixing)... * Do we still need to link libstdc++ statically? (Opensuse cross-compiled packages need a shared library.)
Regards, -- Nicolas
On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> wrote: ...
To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs?
There are some points we need to take into consideration (I probably forgot some):
- The new devlibs must be easier to maintain compared to the current ones.
- It should be possible to use the same steps to update win32 and win64 devlibs.
- If both devlibs could provide exactly the same packages versions, it would greatly help bug tracking (and fixing)...
- Do we still need to link libstdc++ statically? (Opensuse cross-compiled packages need a shared library.)
Regards,
Nicolas
Nicolas,
I build my 64bit libs from scratch. I use MSYS as my shell if you will and gcc 5.1.0 as my compiler.
No, I don't think you have to statically link libstdc++.
I'll try to provide a 64bit devlibs build this weekend if that's not too late.
Thanks, Partha
If you have some time this weekend, then adding potrace to the 64bit devlibs should probably be a high priority. Right now it breaks 64bit builds since it seems the logic for excluding code depending on potrace if it's not available does not work for btool-based builds (at least I was not able to make it work)
Regards, Eduard
Am 11.01.2016 um 11:42 schrieb Partha Bagchi:
On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> wrote: ...
To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs?
There are some points we need to take into consideration (I probably forgot some):
- The new devlibs must be easier to maintain compared to the current ones.
- It should be possible to use the same steps to update win32 and win64 devlibs.
- If both devlibs could provide exactly the same packages versions, it would greatly help bug tracking (and fixing)...
- Do we still need to link libstdc++ statically? (Opensuse cross-compiled packages need a shared library.)
Regards,
Nicolas
Nicolas,
I build my 64bit libs from scratch. I use MSYS as my shell if you will and gcc 5.1.0 as my compiler.
No, I don't think you have to statically link libstdc++.
I'll try to provide a 64bit devlibs build this weekend if that's not too late.
Thanks, Partha
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi Eduard,
I have uploaded the Windows 64bit devlibs here: http://www.partha.com/temp/inkscape-devlibs.7z
Can you (or someone) upload it to its final destination? The devlibs include potrace 1.13.
Please let me know if you have any questions.
Thanks, Partha
On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
If you have some time this weekend, then adding potrace to the 64bit devlibs should probably be a high priority. Right now it breaks 64bit builds since it seems the logic for excluding code depending on potrace if it's not available does not work for btool-based builds (at least I was not able to make it work)
Regards, Eduard
Am 11.01.2016 um 11:42 schrieb Partha Bagchi:
On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> wrote: ...
To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs?
There are some points we need to take into consideration (I probably forgot some):
- The new devlibs must be easier to maintain compared to the current
ones.
- It should be possible to use the same steps to update win32 and win64
devlibs.
- If both devlibs could provide exactly the same packages versions, it
would greatly help bug tracking (and fixing)...
- Do we still need to link libstdc++ statically? (Opensuse cross-compiled
packages need a shared library.)
Regards,
Nicolas
Nicolas,
I build my 64bit libs from scratch. I use MSYS as my shell if you will and gcc 5.1.0 as my compiler.
No, I don't think you have to statically link libstdc++.
I'll try to provide a 64bit devlibs build this weekend if that's not too late.
Thanks, Partha
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi Partha,
that's great, thanks!
I've built Inkscape 64bit with the new devlibs yesterday, with only a few minor issues.
Since I noticed Johan updated the devlibs64 before I'd like some feedback from him, since I'm not too familiar with these kinds of things (handling libraries / build processes). Maybe he can make the necessary changes also this time. Of course I'd be happy to help, too, if for any reason Johan is not available. I guess I'd be able to figure out what to do.
One last thing: Can you provide a README or something similar with the included libraries (don't know if there's an automated process for this)? I noticed the 32bit version has something like that [1] and I guess it would be helpful to get an overview of what's available and to simplify updates.
Best regards, Eduard
[1] http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs/trunk/view/head:/...
Am 17.01.2016 um 20:34 schrieb Partha Bagchi:
Hi Eduard,
I have uploaded the Windows 64bit devlibs here: http://www.partha.com/temp/inkscape-devlibs.7z
Can you (or someone) upload it to its final destination? The devlibs include potrace 1.13.
Please let me know if you have any questions.
Thanks, Partha
On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
If you have some time this weekend, then adding potrace to the 64bit devlibs should probably be a high priority. Right now it breaks 64bit builds since it seems the logic for excluding code depending on potrace if it's not available does not work for btool-based builds (at least I was not able to make it work)
Regards, Eduard
Am 11.01.2016 um 11:42 schrieb Partha Bagchi:
On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> wrote: ...
To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs?
There are some points we need to take into consideration (I probably forgot some):
- The new devlibs must be easier to maintain compared to the current
ones.
- It should be possible to use the same steps to update win32 and win64
devlibs.
- If both devlibs could provide exactly the same packages versions, it
would greatly help bug tracking (and fixing)...
- Do we still need to link libstdc++ statically? (Opensuse cross-compiled
packages need a shared library.)
Regards,
Nicolas
Nicolas,
I build my 64bit libs from scratch. I use MSYS as my shell if you will and gcc 5.1.0 as my compiler.
No, I don't think you have to statically link libstdc++.
I'll try to provide a 64bit devlibs build this weekend if that's not too late.
Thanks, Partha
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Tue, Jan 19, 2016 at 9:52 AM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Hi Partha,
that's great, thanks!
You are welcome. :)
I've built Inkscape 64bit with the new devlibs yesterday, with only a few minor issues.
Please let me know what those issues are. Please contact me offline.
Since I noticed Johan updated the devlibs64 before I'd like some feedback from him, since I'm not too familiar with these kinds of things (handling libraries / build processes). Maybe he can make the necessary changes also this time. Of course I'd be happy to help, too, if for any reason Johan is not available. I guess I'd be able to figure out what to do.
One last thing: Can you provide a README or something similar with the included libraries (don't know if there's an automated process for this)?
Sure no problems. If you want, you can create the file yourself with a simple shell script (or command line). Something like:
for files in /opt/lib/pkgconfig/*.pc; do VERSION=$(grep Version: $files |sed -e 's/Version: //') SOFTWARE=$(grep Name: $files |sed -e 's/Name: //'); echo "$SOFTWARE, $VERSION" >> "Readme.Txt" done
I noticed the 32bit version has something like that [1] and I guess it would be helpful to get an overview of what's available and to simplify updates.
Best regards, Eduard
[1] http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs/trunk/view/head:/...
Am 17.01.2016 um 20:34 schrieb Partha Bagchi:
Hi Eduard,
I have uploaded the Windows 64bit devlibs here: http://www.partha.com/temp/inkscape-devlibs.7z
Can you (or someone) upload it to its final destination? The devlibs include potrace 1.13.
Please let me know if you have any questions.
Thanks, Partha
On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
If you have some time this weekend, then adding potrace to the 64bit devlibs should probably be a high priority. Right now it breaks 64bit builds since it seems the logic for excluding code depending on potrace if it's not available does not work for btool-based builds (at least I was not able to make it work)
Regards, Eduard
Am 11.01.2016 um 11:42 schrieb Partha Bagchi:
On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> wrote: ...
To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs?
There are some points we need to take into consideration (I probably forgot some):
- The new devlibs must be easier to maintain compared to the current
ones.
- It should be possible to use the same steps to update win32 and win64
devlibs.
- If both devlibs could provide exactly the same packages versions, it
would greatly help bug tracking (and fixing)...
- Do we still need to link libstdc++ statically? (Opensuse
cross-compiled packages need a shared library.)
Regards,
Nicolas
Nicolas,
I build my 64bit libs from scratch. I use MSYS as my shell if you will and gcc 5.1.0 as my compiler.
No, I don't think you have to statically link libstdc++.
I'll try to provide a 64bit devlibs build this weekend if that's not too late.
Thanks, Partha
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Eduard,
The Readme.txt file is available is here: http://www.partha.com/temp/Readme.txt
Please let me know if it's adequate for your purpose.
Thanks, Partha
On Tue, Jan 19, 2016 at 7:18 PM, Partha Bagchi <partha1b@...400...> wrote:
On Tue, Jan 19, 2016 at 9:52 AM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Hi Partha,
that's great, thanks!
You are welcome. :)
I've built Inkscape 64bit with the new devlibs yesterday, with only a few minor issues.
Please let me know what those issues are. Please contact me offline.
Since I noticed Johan updated the devlibs64 before I'd like some feedback from him, since I'm not too familiar with these kinds of things (handling libraries / build processes). Maybe he can make the necessary changes also this time. Of course I'd be happy to help, too, if for any reason Johan is not available. I guess I'd be able to figure out what to do.
One last thing: Can you provide a README or something similar with the included libraries (don't know if there's an automated process for this)?
Sure no problems. If you want, you can create the file yourself with a simple shell script (or command line). Something like:
for files in /opt/lib/pkgconfig/*.pc; do VERSION=$(grep Version: $files |sed -e 's/Version: //') SOFTWARE=$(grep Name: $files |sed -e 's/Name: //'); echo "$SOFTWARE, $VERSION" >> "Readme.Txt" done
I noticed the 32bit version has something like that [1] and I guess it would be helpful to get an overview of what's available and to simplify updates.
Best regards, Eduard
[1] http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs/trunk/view/head:/...
Am 17.01.2016 um 20:34 schrieb Partha Bagchi:
Hi Eduard,
I have uploaded the Windows 64bit devlibs here: http://www.partha.com/temp/inkscape-devlibs.7z
Can you (or someone) upload it to its final destination? The devlibs include potrace 1.13.
Please let me know if you have any questions.
Thanks, Partha
On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
If you have some time this weekend, then adding potrace to the 64bit devlibs should probably be a high priority. Right now it breaks 64bit builds since it seems the logic for excluding code depending on potrace if it's not available does not work for btool-based builds (at least I was not able to make it work)
Regards, Eduard
Am 11.01.2016 um 11:42 schrieb Partha Bagchi:
On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> wrote: ...
To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs?
There are some points we need to take into consideration (I probably forgot some):
- The new devlibs must be easier to maintain compared to the current
ones.
- It should be possible to use the same steps to update win32 and win64
devlibs.
- If both devlibs could provide exactly the same packages versions, it
would greatly help bug tracking (and fixing)...
- Do we still need to link libstdc++ statically? (Opensuse
cross-compiled packages need a shared library.)
Regards,
Nicolas
Nicolas,
I build my 64bit libs from scratch. I use MSYS as my shell if you will and gcc 5.1.0 as my compiler.
No, I don't think you have to statically link libstdc++.
I'll try to provide a 64bit devlibs build this weekend if that's not too late.
Thanks, Partha
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
I finally got around to have a look at the 64-bit devlibs Partha provided. I'm afraid however that I didn't succeed to build Inkscape with them yet (this is really not my area of expertise so any help is *very* welcome!).
* What I noticed so far: The new devlibs are based on a MinGW build with win32 threads and SEH exception handling (possibly x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z, see [1]) whereas the old devlibs are based on MinGW with posix threads and SJLJ exception handling (x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z, see [2]).
So my first question is if this would work with Inkscape in principle? Not that I (or anybody else) try to make something work that can not work to start with...
* In case win32 threads and SEH exception handling are OK for Inkscape I suppose we'd also need to rebuild all other dependencies with the new compiler? (Again, I have no clue about these things, but from what I got from a quick Internet search the old and new binaries are not compatible?)
Libraries that I spotted which are currently not included in the new devlibs-package: o gtkmm/gdkmm 2.4 (the package includes only 3.0) o aspell o ImageMagick o poppler-data (for eastern-character support) o librevenge (optional if we want to include newer versions of the various import libraries [3])
Regards, Eduard
[1] http://www.partha.com/temp/Readme.txt [2] http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/view/head... [3] http://www.documentliberation.org/projects/
Am 17.01.2016 um 20:34 schrieb Partha Bagchi:
Hi Eduard,
I have uploaded the Windows 64bit devlibs here: http://www.partha.com/temp/inkscape-devlibs.7z
Can you (or someone) upload it to its final destination? The devlibs include potrace 1.13.
Please let me know if you have any questions.
Thanks, Partha
On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
If you have some time this weekend, then adding potrace to the 64bit devlibs should probably be a high priority. Right now it breaks 64bit builds since it seems the logic for excluding code depending on potrace if it's not available does not work for btool-based builds (at least I was not able to make it work)
Regards, Eduard
Am 11.01.2016 um 11:42 schrieb Partha Bagchi:
On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> wrote: ...
To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs?
There are some points we need to take into consideration (I probably forgot some):
- The new devlibs must be easier to maintain compared to the current
ones.
- It should be possible to use the same steps to update win32 and win64
devlibs.
- If both devlibs could provide exactly the same packages versions, it
would greatly help bug tracking (and fixing)...
- Do we still need to link libstdc++ statically? (Opensuse cross-compiled
packages need a shared library.)
Regards,
Nicolas
Nicolas,
I build my 64bit libs from scratch. I use MSYS as my shell if you will and gcc 5.1.0 as my compiler.
No, I don't think you have to statically link libstdc++.
I'll try to provide a 64bit devlibs build this weekend if that's not too late.
Thanks, Partha
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Sat, Jan 23, 2016 at 1:06 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
I finally got around to have a look at the 64-bit devlibs Partha provided. I'm afraid however that I didn't succeed to build Inkscape with them yet (this is really not my area of expertise so any help is *very* welcome!).
I'll take a look into building it for you if that helps?
What I noticed so far: The new devlibs are based on a MinGW build with win32 threads and SEH exception handling (possibly x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z, see [1]) whereas the old devlibs are based on MinGW with posix threads and SJLJ exception handling (x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z, see [2]).
I think the previous 64-bit devlibs were also built with SEH and using 4.9.2. See this thread: http://sourceforge.net/p/inkscape/mailman/message/34099214/
So my first question is if this would work with Inkscape in principle? Not that I (or anybody else) try to make something work that can not work to start with...
In case win32 threads and SEH exception handling are OK for Inkscape I suppose we'd also need to rebuild all other dependencies with the new compiler? (Again, I have no clue about these things, but from what I got from a quick Internet search the old and new binaries are not compatible?)
Which other dependencies need to be built?
Libraries that I spotted which are currently not included in the new devlibs-package:
gtkmm/gdkmm 2.4 (the package includes only 3.0)
gtkmm 2.4 series is out dated. Do we still use it? With the move to GTK3, this should not be needed?
aspell
aspell is optional.
ImageMagick
Oops, my bad. I'll update the libs.
poppler-data (for eastern-character support)
ditto.
librevenge (optional if we want to include newer versions of the various import libraries [3])
OK, I'll build this too.
Regards, Eduard
[1] http://www.partha.com/temp/Readme.txt [2] http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/view/head... [3] http://www.documentliberation.org/projects/
Am 17.01.2016 um 20:34 schrieb Partha Bagchi:
Hi Eduard,
I have uploaded the Windows 64bit devlibs here: http://www.partha.com/temp/inkscape-devlibs.7z
Can you (or someone) upload it to its final destination? The devlibs include potrace 1.13.
Please let me know if you have any questions.
Thanks, Partha
On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
If you have some time this weekend, then adding potrace to the 64bit devlibs should probably be a high priority. Right now it breaks 64bit builds since it seems the logic for excluding code depending on potrace if it's not available does not work for btool-based builds (at least I was not able to make it work)
Regards, Eduard
Am 11.01.2016 um 11:42 schrieb Partha Bagchi:
On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> wrote: ...
To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs?
There are some points we need to take into consideration (I probably forgot some):
- The new devlibs must be easier to maintain compared to the current
ones.
- It should be possible to use the same steps to update win32 and win64
devlibs.
- If both devlibs could provide exactly the same packages versions, it
would greatly help bug tracking (and fixing)...
- Do we still need to link libstdc++ statically? (Opensuse cross-compiled
packages need a shared library.)
Regards,
Nicolas
Nicolas,
I build my 64bit libs from scratch. I use MSYS as my shell if you will and gcc 5.1.0 as my compiler.
No, I don't think you have to statically link libstdc++.
I'll try to provide a 64bit devlibs build this weekend if that's not too late.
Thanks, Partha
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Am 23.01.2016 um 20:28 schrieb Partha Bagchi:
On Sat, Jan 23, 2016 at 1:06 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
I finally got around to have a look at the 64-bit devlibs Partha provided. I'm afraid however that I didn't succeed to build Inkscape with them yet (this is really not my area of expertise so any help is *very* welcome!).
I'll take a look into building it for you if that helps?
Obviously you have more experience, so I guess you'd be able to figure out what is going wrong. Probably it's just some stupid error of mine which would be trivial to fix ;-). I don't want you to feel obliged, though, especially with respect to my next comment...
What I noticed so far: The new devlibs are based on a MinGW build with win32 threads and SEH exception handling (possibly x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z, see [1]) whereas the old devlibs are based on MinGW with posix threads and SJLJ exception handling (x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z, see [2]).
I think the previous 64-bit devlibs were also built with SEH and using 4.9.2. See this thread: http://sourceforge.net/p/inkscape/mailman/message/34099214/
Oh, wow, I didn't know about these... I based my work on the latest 64-bit devlibs available on launchpad (https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk) and those date back to 2014 (with the readme stating posix/sjlj was in use, no idea if that's correct). I assume your updated builds never made it into the public repository.
So my first question is if this would work with Inkscape in principle? Not that I (or anybody else) try to make something work that can not work to start with...
In case win32 threads and SEH exception handling are OK for Inkscape I suppose we'd also need to rebuild all other dependencies with the new compiler? (Again, I have no clue about these things, but from what I got from a quick Internet search the old and new binaries are not compatible?)
Which other dependencies need to be built?
Only those I listed... some of these are in your package from 2015-05-10, though, so a new built might not be necessary.
Libraries that I spotted which are currently not included in the new devlibs-package:
gtkmm/gdkmm 2.4 (the package includes only 3.0)
gtkmm 2.4 series is out dated. Do we still use it? With the move to GTK3, this should not be needed?
As far as I know GTK3 is still experimental, normal builds still use GTK2.
aspell
aspell is optional.
Yes, sorry for not being more specific. We have it i current builds but I assume it's not mandatory.
ImageMagick
Oops, my bad. I'll update the libs.
Thanks, no problem!
poppler-data (for eastern-character support)
ditto.
librevenge (optional if we want to include newer versions of the various import libraries [3])
OK, I'll build this too.
Regards, Eduard
[1] http://www.partha.com/temp/Readme.txt [2] http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/view/head... [3] http://www.documentliberation.org/projects/
Am 17.01.2016 um 20:34 schrieb Partha Bagchi:
Hi Eduard,
I have uploaded the Windows 64bit devlibs here: http://www.partha.com/temp/inkscape-devlibs.7z
Can you (or someone) upload it to its final destination? The devlibs include potrace 1.13.
Please let me know if you have any questions.
Thanks, Partha
On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
If you have some time this weekend, then adding potrace to the 64bit devlibs should probably be a high priority. Right now it breaks 64bit builds since it seems the logic for excluding code depending on potrace if it's not available does not work for btool-based builds (at least I was not able to make it work)
Regards, Eduard
Am 11.01.2016 um 11:42 schrieb Partha Bagchi:
On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> wrote: ...
To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs?
There are some points we need to take into consideration (I probably forgot some):
- The new devlibs must be easier to maintain compared to the current
ones.
- It should be possible to use the same steps to update win32 and win64
devlibs.
- If both devlibs could provide exactly the same packages versions, it
would greatly help bug tracking (and fixing)...
- Do we still need to link libstdc++ statically? (Opensuse cross-compiled
packages need a shared library.)
Regards,
Nicolas
Nicolas,
I build my 64bit libs from scratch. I use MSYS as my shell if you will and gcc 5.1.0 as my compiler.
No, I don't think you have to statically link libstdc++.
I'll try to provide a 64bit devlibs build this weekend if that's not too late.
Thanks, Partha
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Well, I can't seem to get it working... Inkscape is compiling fine but I'm always getting linker errors:
Make error line 460: LINK problem: build\obj\extension\internal\bitmap\imagemagick.o:imagemagick.cpp:(.text+0x26b): undefined reference to `Magick::Blob::base64(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >)' build\obj\extension\internal\bitmap\imagemagick.o:imagemagick.cpp:(.text+0x34d): undefined reference to `Magick::Image::read(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' build\obj\extension\internal\bitmap\imagemagick.o:imagemagick.cpp:(.text+0x8de): undefined reference to `Magick::Blob::base64[abi:cxx11]()' build\obj\extension\internal\bitmap\imagemagick.o:imagemagick.cpp:(.text+0x93b): undefined reference to `Magick::Image::magick[abi:cxx11]() const' build\obj\extension\internal\image-resolution.o:image-resolution.cpp:(.text+0x4f6): undefined reference to `Magick::Image::read(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' build\obj\extension\internal\image-resolution.o:image-resolution.cpp:(.text+0x519): undefined reference to `Magick::Image::magick[abi:cxx11]() const' build\obj\libdepixelize\kopftracer2011.o:kopftracer2011.cpp:(.text+0x3a3): undefined reference to `Gdk::Pixbuf::create_from_file(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' build\obj\libdepixelize\kopftracer2011.o:kopftracer2011.cpp:(.text+0x593): undefined reference to `Gdk::Pixbuf::create_from_file(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' build\obj\libdepixelize\kopftracer2011.o:kopftracer2011.cpp:(.text+0x6d3): undefined reference to `Gdk::Pixbuf::create_from_file(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' build\obj\ui\clipboard.o:clipboard.cpp:(.text+0x71): undefined reference to `Gtk::SelectionData::get_target[abi:cxx11]() const' build\obj\ui\clipboard.o:clipboard.cpp:(.text+0xa85): undefined reference to `Gdk::Pixbuf::save(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, Glib::ustring const&)' build\obj\ui\clipboard.o:clipboard.cpp:(.text+0x17dc): undefined reference to `Gtk::SelectionData::get_target[abi:cxx11]() const' build\obj\ui\dialog\filedialogimpl-gtkmm.o:filedialogimpl-gtkmm.cpp:(.text+0x22db): undefined reference to `Gdk::Pixbuf::create_from_file(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' build\obj\ui\dialog\filedialogimpl-win32.o:filedialogimpl-win32.cpp:(.text+0x240c): undefined reference to `Gdk::Pixbuf::create_from_file(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' build\obj\ui\dialog\ocaldialogs.o:ocaldialogs.cpp:(.text+0xebd): undefined reference to `Gtk::Image::set(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' build\obj\ui\dialog\template-widget.o:template-widget.cpp:(.text+0x4b7): undefined reference to `Gtk::Image::set(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' build\obj\ui\widget\imageicon.o:imageicon.cpp:(.text+0xaf3): undefined reference to `Gdk::Pixbuf::create_from_file(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' build\obj\widgets\icon.o:icon.cpp:(.text+0xad47): undefined reference to `Gdk::Pixbuf::save(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, Glib::ustring const&)' build\obj\widgets\icon.o:icon.cpp:(.text+0xadf1): undefined reference to `Gdk::Pixbuf::create_from_file(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' collect2.exe: error: ld returned 1 exit status
Here's the command used by btool:
x86_64-w64-mingw32-g++ -o build/inkscape.exe -mwindows -m64 -mthreads build\obj\2geom\affine.o build\obj\2geom\basic-intersection.o build\obj\2geom\bezier-clipping.o build\obj\2geom\bezier-curve.o build\obj\2geom\bezier-utils.o build\obj\2geom\bezier.o build\obj\2geom\cairo-path-sink.o build\obj\2geom\circle.o build\obj\2geom\conic_section_clipper_impl.o build\obj\2geom\conicsec.o build\obj\2geom\convex-hull.o build\obj\2geom\coord.o build\obj\2geom\crossing.o build\obj\2geom\curve.o build\obj\2geom\d2-sbasis.o build\obj\2geom\ellipse.o build\obj\2geom\elliptical-arc-from-sbasis.o build\obj\2geom\elliptical-arc.o build\obj\2geom\geom.o build\obj\2geom\intersection-graph.o build\obj\2geom\line.o build\obj\2geom\nearest-time.o build\obj\2geom\numeric\matrix.o build\obj\2geom\path-intersection.o build\obj\2geom\path-sink.o build\obj\2geom\path.o build\obj\2geom\pathvector.o build\obj\2geom\piecewise.o build\obj\2geom\point.o build\obj\2geom\polynomial.o build\obj\2geom\rect.o build\obj\2geom\recursive-bezier-intersection.o build\obj\2geom\sbasis-2d.o build\obj\2geom\sbasis-geometric.o build\obj\2geom\sbasis-math.o build\obj\2geom\sbasis-poly.o build\obj\2geom\sbasis-roots.o build\obj\2geom\sbasis-to-bezier.o build\obj\2geom\sbasis.o build\obj\2geom\solve-bezier-one-d.o build\obj\2geom\solve-bezier-parametric.o build\obj\2geom\solve-bezier.o build\obj\2geom\svg-path-parser.o build\obj\2geom\svg-path-writer.o build\obj\2geom\sweep-bounds.o build\obj\2geom\toposweep.o build\obj\2geom\transforms.o build\obj\2geom\utils.o build\obj\2geom\viewbox.o build\obj\attribute-rel-css.o build\obj\attribute-rel-svg.o build\obj\attribute-rel-util.o build\obj\attributes.o build\obj\axis-manip.o build\obj\box3d-side.o build\obj\box3d.o build\obj\color-profile.o build\obj\color.o build\obj\composite-undo-stack-observer.o build\obj\conditions.o build\obj\conn-avoid-ref.o build\obj\console-output-undo-observer.o build\obj\context-fns.o build\obj\debug\demangle.o build\obj\debug\gdk-event-latency-tracker.o build\obj\debug\heap.o build\obj\debug\log-display-config.o build\obj\debug\logger.o build\obj\debug\sysv-heap.o build\obj\debug\timestamp.o build\obj\desktop-events.o build\obj\desktop-style.o build\obj\desktop.o build\obj\device-manager.o build\obj\dir-util.o build\obj\display\cairo-utils.o build\obj\display\canvas-arena.o build\obj\display\canvas-axonomgrid.o build\obj\display\canvas-bpath.o build\obj\display\canvas-grid.o build\obj\display\canvas-temporary-item-list.o build\obj\display\canvas-temporary-item.o build\obj\display\canvas-text.o build\obj\display\curve.o build\obj\display\drawing-context.o build\obj\display\drawing-group.o build\obj\display\drawing-image.o build\obj\display\drawing-item.o build\obj\display\drawing-pattern.o build\obj\display\drawing-shape.o build\obj\display\drawing-surface.o build\obj\display\drawing-text.o build\obj\display\drawing.o build\obj\display\gnome-canvas-acetate.o build\obj\display\grayscale.o build\obj\display\guideline.o build\obj\display\nr-3dutils.o build\obj\display\nr-filter-blend.o build\obj\display\nr-filter-colormatrix.o build\obj\display\nr-filter-component-transfer.o build\obj\display\nr-filter-composite.o build\obj\display\nr-filter-convolve-matrix.o build\obj\display\nr-filter-diffuselighting.o build\obj\display\nr-filter-displacement-map.o build\obj\display\nr-filter-flood.o build\obj\display\nr-filter-gaussian.o build\obj\display\nr-filter-image.o build\obj\display\nr-filter-merge.o build\obj\display\nr-filter-morphology.o build\obj\display\nr-filter-offset.o build\obj\display\nr-filter-primitive.o build\obj\display\nr-filter-skeleton.o build\obj\display\nr-filter-slot.o build\obj\display\nr-filter-specularlighting.o build\obj\display\nr-filter-tile.o build\obj\display\nr-filter-turbulence.o build\obj\display\nr-filter-units.o build\obj\display\nr-filter.o build\obj\display\nr-light.o build\obj\display\nr-style.o build\obj\display\nr-svgfonts.o build\obj\display\snap-indicator.o build\obj\display\sodipodi-ctrl.o build\obj\display\sodipodi-ctrlrect.o build\obj\display\sp-canvas-util.o build\obj\display\sp-canvas.o build\obj\display\sp-ctrlcurve.o build\obj\display\sp-ctrlline.o build\obj\display\sp-ctrlquadr.o build\obj\document-subset.o build\obj\document-undo.o build\obj\document.o build\obj\ege-color-prof-tracker.o build\obj\event-log.o build\obj\extension\db.o build\obj\extension\dependency.o build\obj\extension\effect.o build\obj\extension\error-file.o build\obj\extension\execution-env.o build\obj\extension\extension.o build\obj\extension\implementation\implementation.o build\obj\extension\implementation\script.o build\obj\extension\implementation\xslt.o build\obj\extension\init.o build\obj\extension\input.o build\obj\extension\internal\bitmap\adaptiveThreshold.o build\obj\extension\internal\bitmap\addNoise.o build\obj\extension\internal\bitmap\blur.o build\obj\extension\internal\bitmap\channel.o build\obj\extension\internal\bitmap\charcoal.o build\obj\extension\internal\bitmap\colorize.o build\obj\extension\internal\bitmap\contrast.o build\obj\extension\internal\bitmap\crop.o build\obj\extension\internal\bitmap\cycleColormap.o build\obj\extension\internal\bitmap\despeckle.o build\obj\extension\internal\bitmap\edge.o build\obj\extension\internal\bitmap\emboss.o build\obj\extension\internal\bitmap\enhance.o build\obj\extension\internal\bitmap\equalize.o build\obj\extension\internal\bitmap\gaussianBlur.o build\obj\extension\internal\bitmap\imagemagick.o build\obj\extension\internal\bitmap\implode.o build\obj\extension\internal\bitmap\level.o build\obj\extension\internal\bitmap\levelChannel.o build\obj\extension\internal\bitmap\medianFilter.o build\obj\extension\internal\bitmap\modulate.o build\obj\extension\internal\bitmap\negate.o build\obj\extension\internal\bitmap\normalize.o build\obj\extension\internal\bitmap\oilPaint.o build\obj\extension\internal\bitmap\opacity.o build\obj\extension\internal\bitmap\raise.o build\obj\extension\internal\bitmap\reduceNoise.o build\obj\extension\internal\bitmap\sample.o build\obj\extension\internal\bitmap\shade.o build\obj\extension\internal\bitmap\sharpen.o build\obj\extension\internal\bitmap\solarize.o build\obj\extension\internal\bitmap\spread.o build\obj\extension\internal\bitmap\swirl.o build\obj\extension\internal\bitmap\threshold.o build\obj\extension\internal\bitmap\unsharpmask.o build\obj\extension\internal\bitmap\wave.o build\obj\extension\internal\bluredge.o build\obj\extension\internal\cairo-png-out.o build\obj\extension\internal\cairo-ps-out.o build\obj\extension\internal\cairo-render-context.o build\obj\extension\internal\cairo-renderer-pdf-out.o build\obj\extension\internal\cairo-renderer.o build\obj\extension\internal\cdr-input.o build\obj\extension\internal\emf-inout.o build\obj\extension\internal\emf-print.o build\obj\extension\internal\filter\filter-all.o build\obj\extension\internal\filter\filter-file.o build\obj\extension\internal\filter\filter.o build\obj\extension\internal\gdkpixbuf-input.o build\obj\extension\internal\gimpgrad.o build\obj\extension\internal\grid.o build\obj\extension\internal\image-resolution.o build\obj\extension\internal\javafx-out.o build\obj\extension\internal\latex-pstricks-out.o build\obj\extension\internal\latex-pstricks.o build\obj\extension\internal\latex-text-renderer.o build\obj\extension\internal\metafile-inout.o build\obj\extension\internal\metafile-print.o build\obj\extension\internal\odf.o build\obj\extension\internal\pdfinput\pdf-input.o build\obj\extension\internal\pdfinput\pdf-parser.o build\obj\extension\internal\pdfinput\svg-builder.o build\obj\extension\internal\pov-out.o build\obj\extension\internal\svg.o build\obj\extension\internal\svgz.o build\obj\extension\internal\text_reassemble.o build\obj\extension\internal\vsd-input.o build\obj\extension\internal\wmf-inout.o build\obj\extension\internal\wmf-print.o build\obj\extension\internal\wpg-input.o build\obj\extension\output.o build\obj\extension\param\bool.o build\obj\extension\param\color.o build\obj\extension\param\description.o build\obj\extension\param\enum.o build\obj\extension\param\float.o build\obj\extension\param\int.o build\obj\extension\param\notebook.o build\obj\extension\param\parameter.o build\obj\extension\param\radiobutton.o build\obj\extension\param\string.o build\obj\extension\patheffect.o build\obj\extension\prefdialog.o build\obj\extension\print.o build\obj\extension\system.o build\obj\extension\timer.o build\obj\extract-uri.o build\obj\file.o build\obj\filter-chemistry.o build\obj\filter-enums.o build\obj\filters\blend.o build\obj\filters\colormatrix.o build\obj\filters\componenttransfer-funcnode.o build\obj\filters\componenttransfer.o build\obj\filters\composite.o build\obj\filters\convolvematrix.o build\obj\filters\diffuselighting.o build\obj\filters\displacementmap.o build\obj\filters\distantlight.o build\obj\filters\flood.o build\obj\filters\gaussian-blur.o build\obj\filters\image.o build\obj\filters\merge.o build\obj\filters\mergenode.o build\obj\filters\morphology.o build\obj\filters\offset.o build\obj\filters\pointlight.o build\obj\filters\specularlighting.o build\obj\filters\spotlight.o build\obj\filters\tile.o build\obj\filters\turbulence.o build\obj\gc-anchored.o build\obj\gc-finalized.o build\obj\gradient-chemistry.o build\obj\gradient-drag.o build\obj\graphlayout.o build\obj\guide-snapper.o build\obj\help.o build\obj\helper\action-context.o build\obj\helper\action.o build\obj\helper\geom-nodetype.o build\obj\helper\geom-pathstroke.o build\obj\helper\geom.o build\obj\helper\gnome-utils.o build\obj\helper\pixbuf-ops.o build\obj\helper\png-write.o build\obj\helper\sp-marshal.o build\obj\helper\stock-items.o build\obj\helper\window.o build\obj\id-clash.o build\obj\inkgc\gc.o build\obj\inkres.o build\obj\inkscape-version.o build\obj\inkscape.o build\obj\io\base64stream.o build\obj\io\bufferstream.o build\obj\io\gzipstream.o build\obj\io\inkjar.o build\obj\io\inkscapestream.o build\obj\io\resource.o build\obj\io\stringstream.o build\obj\io\sys.o build\obj\io\uristream.o build\obj\io\xsltstream.o build\obj\knot-holder-entity.o build\obj\knot-ptr.o build\obj\knot.o build\obj\knotholder.o build\obj\layer-fns.o build\obj\layer-manager.o build\obj\layer-model.o build\obj\libavoid\connector.o build\obj\libavoid\geometry.o build\obj\libavoid\geomtypes.o build\obj\libavoid\graph.o build\obj\libavoid\makepath.o build\obj\libavoid\orthogonal.o build\obj\libavoid\router.o build\obj\libavoid\shape.o build\obj\libavoid\timer.o build\obj\libavoid\vertices.o build\obj\libavoid\viscluster.o build\obj\libavoid\visibility.o build\obj\libavoid\vpsc.o build\obj\libcola\cola.o build\obj\libcola\conjugate_gradient.o build\obj\libcola\connected_components.o build\obj\libcola\cycle_detector.o build\obj\libcola\gradient_projection.o build\obj\libcola\shortest_paths.o build\obj\libcola\straightener.o build\obj\libcroco\cr-additional-sel.o build\obj\libcroco\cr-attr-sel.o build\obj\libcroco\cr-cascade.o build\obj\libcroco\cr-declaration.o build\obj\libcroco\cr-doc-handler.o build\obj\libcroco\cr-enc-handler.o build\obj\libcroco\cr-fonts.o build\obj\libcroco\cr-input.o build\obj\libcroco\cr-libxml-node-iface.o build\obj\libcroco\cr-num.o build\obj\libcroco\cr-om-parser.o build\obj\libcroco\cr-parser.o build\obj\libcroco\cr-parsing-location.o build\obj\libcroco\cr-prop-list.o build\obj\libcroco\cr-pseudo.o build\obj\libcroco\cr-rgb.o build\obj\libcroco\cr-sel-eng.o build\obj\libcroco\cr-selector.o build\obj\libcroco\cr-simple-sel.o build\obj\libcroco\cr-statement.o build\obj\libcroco\cr-string.o build\obj\libcroco\cr-style.o build\obj\libcroco\cr-stylesheet.o build\obj\libcroco\cr-term.o build\obj\libcroco\cr-tknzr.o build\obj\libcroco\cr-token.o build\obj\libcroco\cr-utils.o build\obj\libdepixelize\kopftracer2011.o build\obj\libgdl\gdl-dock-bar.o build\obj\libgdl\gdl-dock-item-button-image.o build\obj\libgdl\gdl-dock-item-grip.o build\obj\libgdl\gdl-dock-item.o build\obj\libgdl\gdl-dock-master.o build\obj\libgdl\gdl-dock-notebook.o build\obj\libgdl\gdl-dock-object.o build\obj\libgdl\gdl-dock-paned.o build\obj\libgdl\gdl-dock-placeholder.o build\obj\libgdl\gdl-dock-tablabel.o build\obj\libgdl\gdl-dock.o build\obj\libgdl\gdl-i18n.o build\obj\libgdl\gdl-switcher.o build\obj\libgdl\gdl-win32.o build\obj\libgdl\libgdlmarshal.o build\obj\libgdl\libgdltypebuiltins.o build\obj\libnrtype\FontFactory.o build\obj\libnrtype\FontInstance.o build\obj\libnrtype\Layout-TNG-Compute.o build\obj\libnrtype\Layout-TNG-Input.o build\obj\libnrtype\Layout-TNG-OutIter.o build\obj\libnrtype\Layout-TNG-Output.o build\obj\libnrtype\Layout-TNG-Scanline-Makers.o build\obj\libnrtype\Layout-TNG.o build\obj\libnrtype\TextWrapper.o build\obj\libnrtype\font-lister.o build\obj\libnrtype\nr-type-primitives.o build\obj\libuemf\symbol_convert.o build\obj\libuemf\uemf.o build\obj\libuemf\uemf_endian.o build\obj\libuemf\uemf_print.o build\obj\libuemf\uemf_safe.o build\obj\libuemf\uemf_utf.o build\obj\libuemf\upmf.o build\obj\libuemf\upmf_print.o build\obj\libuemf\uwmf.o build\obj\libuemf\uwmf_endian.o build\obj\libuemf\uwmf_print.o build\obj\libvpsc\block.o build\obj\libvpsc\blocks.o build\obj\libvpsc\constraint.o build\obj\libvpsc\generate-constraints.o build\obj\libvpsc\pairingheap\PairingHeap.o build\obj\libvpsc\remove_rectangle_overlap.o build\obj\libvpsc\solve_VPSC.o build\obj\libvpsc\variable.o build\obj\line-geometry.o build\obj\line-snapper.o build\obj\livarot\AVL.o build\obj\livarot\AlphaLigne.o build\obj\livarot\BitLigne.o build\obj\livarot\Path.o build\obj\livarot\PathConversion.o build\obj\livarot\PathCutting.o build\obj\livarot\PathOutline.o build\obj\livarot\PathSimplify.o build\obj\livarot\PathStroke.o build\obj\livarot\Shape.o build\obj\livarot\ShapeDraw.o build\obj\livarot\ShapeMisc.o build\obj\livarot\ShapeRaster.o build\obj\livarot\ShapeSweep.o build\obj\livarot\float-line.o build\obj\livarot\int-line.o build\obj\livarot\path-description.o build\obj\livarot\sweep-event.o build\obj\livarot\sweep-tree-list.o build\obj\livarot\sweep-tree.o build\obj\live_effects\effect.o build\obj\live_effects\lpe-angle_bisector.o build\obj\live_effects\lpe-attach-path.o build\obj\live_effects\lpe-bendpath.o build\obj\live_effects\lpe-bounding-box.o build\obj\live_effects\lpe-bspline.o build\obj\live_effects\lpe-circle_3pts.o build\obj\live_effects\lpe-circle_with_radius.o build\obj\live_effects\lpe-clone-original.o build\obj\live_effects\lpe-constructgrid.o build\obj\live_effects\lpe-copy_rotate.o build\obj\live_effects\lpe-curvestitch.o build\obj\live_effects\lpe-dynastroke.o build\obj\live_effects\lpe-ellipse_5pts.o build\obj\live_effects\lpe-envelope.o build\obj\live_effects\lpe-extrude.o build\obj\live_effects\lpe-fill-between-many.o build\obj\live_effects\lpe-fill-between-strokes.o build\obj\live_effects\lpe-fillet-chamfer.o build\obj\live_effects\lpe-gears.o build\obj\live_effects\lpe-interpolate.o build\obj\live_effects\lpe-interpolate_points.o build\obj\live_effects\lpe-jointype.o build\obj\live_effects\lpe-knot.o build\obj\live_effects\lpe-lattice.o build\obj\live_effects\lpe-lattice2.o build\obj\live_effects\lpe-line_segment.o build\obj\live_effects\lpe-mirror_symmetry.o build\obj\live_effects\lpe-offset.o build\obj\live_effects\lpe-parallel.o build\obj\live_effects\lpe-path_length.o build\obj\live_effects\lpe-patternalongpath.o build\obj\live_effects\lpe-perp_bisector.o build\obj\live_effects\lpe-perspective-envelope.o build\obj\live_effects\lpe-perspective_path.o build\obj\live_effects\lpe-powerstroke.o build\obj\live_effects\lpe-recursiveskeleton.o build\obj\live_effects\lpe-rough-hatches.o build\obj\live_effects\lpe-roughen.o build\obj\live_effects\lpe-ruler.o build\obj\live_effects\lpe-show_handles.o build\obj\live_effects\lpe-simplify.o build\obj\live_effects\lpe-skeleton.o build\obj\live_effects\lpe-sketch.o build\obj\live_effects\lpe-spiro.o build\obj\live_effects\lpe-tangent_to_curve.o build\obj\live_effects\lpe-taperstroke.o build\obj\live_effects\lpe-test-doEffect-stack.o build\obj\live_effects\lpe-text_label.o build\obj\live_effects\lpe-transform_2pts.o build\obj\live_effects\lpe-vonkoch.o build\obj\live_effects\lpegroupbbox.o build\obj\live_effects\lpeobject-reference.o build\obj\live_effects\lpeobject.o build\obj\live_effects\parameter\array.o build\obj\live_effects\parameter\bool.o build\obj\live_effects\parameter\filletchamferpointarray.o build\obj\live_effects\parameter\originalpath.o build\obj\live_effects\parameter\originalpatharray.o build\obj\live_effects\parameter\parameter.o build\obj\live_effects\parameter\path-reference.o build\obj\live_effects\parameter\path.o build\obj\live_effects\parameter\point.o build\obj\live_effects\parameter\powerstrokepointarray.o build\obj\live_effects\parameter\random.o build\obj\live_effects\parameter\text.o build\obj\live_effects\parameter\togglebutton.o build\obj\live_effects\parameter\transformedpoint.o build\obj\live_effects\parameter\unit.o build\obj\live_effects\parameter\vector.o build\obj\live_effects\spiro-converters.o build\obj\live_effects\spiro.o build\obj\main-cmdlineact.o build\obj\main.o build\obj\media.o build\obj\message-context.o build\obj\message-stack.o build\obj\mod360.o build\obj\object-hierarchy.o build\obj\object-snapper.o build\obj\path-chemistry.o build\obj\persp3d-reference.o build\obj\persp3d.o build\obj\perspective-line.o build\obj\preferences.o build\obj\prefix.o build\obj\print.o build\obj\profile-manager.o build\obj\proj_pt.o build\obj\pure-transform.o build\obj\rdf.o build\obj\registrytool.o build\obj\removeoverlap.o build\obj\resource-manager.o build\obj\rubberband.o build\obj\satisfied-guide-cns.o build\obj\selcue.o build\obj\selection-chemistry.o build\obj\selection-describer.o build\obj\selection.o build\obj\seltrans-handles.o build\obj\seltrans.o build\obj\shortcuts.o build\obj\snap-preferences.o build\obj\snap.o build\obj\snapped-curve.o build\obj\snapped-line.o build\obj\snapped-point.o build\obj\snapper.o build\obj\sp-anchor.o build\obj\sp-clippath.o build\obj\sp-conn-end-pair.o build\obj\sp-conn-end.o build\obj\sp-cursor.o build\obj\sp-defs.o build\obj\sp-desc.o build\obj\sp-ellipse.o build\obj\sp-factory.o build\obj\sp-filter-primitive.o build\obj\sp-filter-reference.o build\obj\sp-filter.o build\obj\sp-flowdiv.o build\obj\sp-flowregion.o build\obj\sp-flowtext.o build\obj\sp-font-face.o build\obj\sp-font.o build\obj\sp-glyph-kerning.o build\obj\sp-glyph.o build\obj\sp-gradient-reference.o build\obj\sp-gradient.o build\obj\sp-guide.o build\obj\sp-hatch-path.o build\obj\sp-hatch.o build\obj\sp-image.o build\obj\sp-item-group.o build\obj\sp-item-notify-moveto.o build\obj\sp-item-rm-unsatisfied-cns.o build\obj\sp-item-transform.o build\obj\sp-item-update-cns.o build\obj\sp-item.o build\obj\sp-line.o build\obj\sp-linear-gradient.o build\obj\sp-lpe-item.o build\obj\sp-marker.o build\obj\sp-mask.o build\obj\sp-mesh-array.o build\obj\sp-mesh-patch.o build\obj\sp-mesh-row.o build\obj\sp-mesh.o build\obj\sp-metadata.o build\obj\sp-missing-glyph.o build\obj\sp-namedview.o build\obj\sp-object-group.o build\obj\sp-object.o build\obj\sp-offset.o build\obj\sp-paint-server.o build\obj\sp-path.o build\obj\sp-pattern.o build\obj\sp-polygon.o build\obj\sp-polyline.o build\obj\sp-radial-gradient.o build\obj\sp-rect.o build\obj\sp-root.o build\obj\sp-script.o build\obj\sp-shape.o build\obj\sp-solid-color.o build\obj\sp-spiral.o build\obj\sp-star.o build\obj\sp-stop.o build\obj\sp-string.o build\obj\sp-style-elem.o build\obj\sp-switch.o build\obj\sp-symbol.o build\obj\sp-tag-use-reference.o build\obj\sp-tag-use.o build\obj\sp-tag.o build\obj\sp-text.o build\obj\sp-title.o build\obj\sp-tref-reference.o build\obj\sp-tref.o build\obj\sp-tspan.o build\obj\sp-use-reference.o build\obj\sp-use.o build\obj\splivarot.o build\obj\style-internal.o build\obj\style.o build\obj\svg-view-widget.o build\obj\svg-view.o build\obj\svg\css-ostringstream.o build\obj\svg\path-string.o build\obj\svg\stringstream.o build\obj\svg\strip-trailing-zeros.o build\obj\svg\svg-affine.o build\obj\svg\svg-angle.o build\obj\svg\svg-color.o build\obj\svg\svg-length.o build\obj\svg\svg-path.o build\obj\svg\test-stubs.o build\obj\text-chemistry.o build\obj\text-editing.o build\obj\trace\filterset.o build\obj\trace\imagemap-gdk.o build\obj\trace\imagemap.o build\obj\trace\potrace\inkscape-potrace.o build\obj\trace\quantize.o build\obj\trace\siox.o build\obj\trace\trace.o build\obj\transf_mat_3x4.o build\obj\ui\cache\svg_preview_cache.o build\obj\ui\clipboard.o build\obj\ui\control-manager.o build\obj\ui\dialog-events.o build\obj\ui\dialog\aboutbox.o build\obj\ui\dialog\align-and-distribute.o build\obj\ui\dialog\calligraphic-profile-rename.o build\obj\ui\dialog\clonetiler.o build\obj\ui\dialog\color-item.o build\obj\ui\dialog\debug.o build\obj\ui\dialog\desktop-tracker.o build\obj\ui\dialog\dialog-manager.o build\obj\ui\dialog\dialog.o build\obj\ui\dialog\dock-behavior.o build\obj\ui\dialog\document-metadata.o build\obj\ui\dialog\document-properties.o build\obj\ui\dialog\export.o build\obj\ui\dialog\extension-editor.o build\obj\ui\dialog\extensions.o build\obj\ui\dialog\filedialog.o build\obj\ui\dialog\filedialogimpl-gtkmm.o build\obj\ui\dialog\filedialogimpl-win32.o build\obj\ui\dialog\fill-and-stroke.o build\obj\ui\dialog\filter-effects-dialog.o build\obj\ui\dialog\find.o build\obj\ui\dialog\floating-behavior.o build\obj\ui\dialog\font-substitution.o build\obj\ui\dialog\glyphs.o build\obj\ui\dialog\grid-arrange-tab.o build\obj\ui\dialog\guides.o build\obj\ui\dialog\icon-preview.o build\obj\ui\dialog\inkscape-preferences.o build\obj\ui\dialog\input.o build\obj\ui\dialog\layer-properties.o build\obj\ui\dialog\layers.o build\obj\ui\dialog\livepatheffect-add.o build\obj\ui\dialog\livepatheffect-editor.o build\obj\ui\dialog\lpe-fillet-chamfer-properties.o build\obj\ui\dialog\lpe-powerstroke-properties.o build\obj\ui\dialog\memory.o build\obj\ui\dialog\messages.o build\obj\ui\dialog\new-from-template.o build\obj\ui\dialog\object-attributes.o build\obj\ui\dialog\object-properties.o build\obj\ui\dialog\objects.o build\obj\ui\dialog\ocaldialogs.o build\obj\ui\dialog\pixelartdialog.o build\obj\ui\dialog\polar-arrange-tab.o build\obj\ui\dialog\print-colors-preview-dialog.o build\obj\ui\dialog\print.o build\obj\ui\dialog\spellcheck.o build\obj\ui\dialog\svg-fonts-dialog.o build\obj\ui\dialog\swatches.o build\obj\ui\dialog\symbols.o build\obj\ui\dialog\tags.o build\obj\ui\dialog\template-load-tab.o build\obj\ui\dialog\template-widget.o build\obj\ui\dialog\text-edit.o build\obj\ui\dialog\tile.o build\obj\ui\dialog\tracedialog.o build\obj\ui\dialog\transformation.o build\obj\ui\dialog\undo-history.o build\obj\ui\dialog\xml-tree.o build\obj\ui\draw-anchor.o build\obj\ui\interface.o build\obj\ui\object-edit.o build\obj\ui\previewholder.o build\obj\ui\selected-color.o build\obj\ui\shape-editor.o build\obj\ui\tool-factory.o build\obj\ui\tool\control-point-selection.o build\obj\ui\tool\control-point.o build\obj\ui\tool\curve-drag-point.o build\obj\ui\tool\event-utils.o build\obj\ui\tool\manipulator.o build\obj\ui\tool\modifier-tracker.o build\obj\ui\tool\multi-path-manipulator.o build\obj\ui\tool\node.o build\obj\ui\tool\path-manipulator.o build\obj\ui\tool\selectable-control-point.o build\obj\ui\tool\selector.o build\obj\ui\tool\transform-handle-set.o build\obj\ui\tools-switch.o build\obj\ui\tools\arc-tool.o build\obj\ui\tools\box3d-tool.o build\obj\ui\tools\calligraphic-tool.o build\obj\ui\tools\connector-tool.o build\obj\ui\tools\dropper-tool.o build\obj\ui\tools\dynamic-base.o build\obj\ui\tools\eraser-tool.o build\obj\ui\tools\flood-tool.o build\obj\ui\tools\freehand-base.o build\obj\ui\tools\gradient-tool.o build\obj\ui\tools\lpe-tool.o build\obj\ui\tools\measure-tool.o build\obj\ui\tools\mesh-tool.o build\obj\ui\tools\node-tool.o build\obj\ui\tools\pen-tool.o build\obj\ui\tools\pencil-tool.o build\obj\ui\tools\rect-tool.o build\obj\ui\tools\select-tool.o build\obj\ui\tools\spiral-tool.o build\obj\ui\tools\spray-tool.o build\obj\ui\tools\star-tool.o build\obj\ui\tools\text-tool.o build\obj\ui\tools\tool-base.o build\obj\ui\tools\tweak-tool.o build\obj\ui\tools\zoom-tool.o build\obj\ui\uxmanager.o build\obj\ui\view\view-widget.o build\obj\ui\view\view.o build\obj\ui\widget\addtoicon.o build\obj\ui\widget\anchor-selector.o build\obj\ui\widget\button.o build\obj\ui\widget\clipmaskicon.o build\obj\ui\widget\color-entry.o build\obj\ui\widget\color-icc-selector.o build\obj\ui\widget\color-notebook.o build\obj\ui\widget\color-picker.o build\obj\ui\widget\color-preview.o build\obj\ui\widget\color-scales.o build\obj\ui\widget\color-slider.o build\obj\ui\widget\color-wheel-selector.o build\obj\ui\widget\dock-item.o build\obj\ui\widget\dock.o build\obj\ui\widget\entity-entry.o build\obj\ui\widget\entry.o build\obj\ui\widget\filter-effect-chooser.o build\obj\ui\widget\font-variants.o build\obj\ui\widget\frame.o build\obj\ui\widget\gimpcolorwheel.o build\obj\ui\widget\gimpspinscale.o build\obj\ui\widget\highlight-picker.o build\obj\ui\widget\imageicon.o build\obj\ui\widget\imagetoggler.o build\obj\ui\widget\insertordericon.o build\obj\ui\widget\labelled.o build\obj\ui\widget\layer-selector.o build\obj\ui\widget\layertypeicon.o build\obj\ui\widget\licensor.o build\obj\ui\widget\notebook-page.o build\obj\ui\widget\object-composite-settings.o build\obj\ui\widget\page-sizer.o build\obj\ui\widget\panel.o build\obj\ui\widget\point.o build\obj\ui\widget\preferences-widget.o build\obj\ui\widget\random.o build\obj\ui\widget\registered-widget.o build\obj\ui\widget\registry.o build\obj\ui\widget\rendering-options.o build\obj\ui\widget\rotateable.o build\obj\ui\widget\scalar-unit.o build\obj\ui\widget\scalar.o build\obj\ui\widget\selected-style.o build\obj\ui\widget\spin-scale.o build\obj\ui\widget\spin-slider.o build\obj\ui\widget\spinbutton.o build\obj\ui\widget\style-subject.o build\obj\ui\widget\style-swatch.o build\obj\ui\widget\text.o build\obj\ui\widget\tolerance-slider.o build\obj\ui\widget\unit-menu.o build\obj\ui\widget\unit-tracker.o build\obj\unclump.o build\obj\unicoderange.o build\obj\uri-references.o build\obj\uri.o build\obj\util\ege-appear-time-tracker.o build\obj\util\ege-tags.o build\obj\util\expression-evaluator.o build\obj\util\share.o build\obj\util\units.o build\obj\util\ziptool.o build\obj\vanishing-point.o build\obj\verbs.o build\obj\version.o build\obj\viewbox.o build\obj\widgets\arc-toolbar.o build\obj\widgets\box3d-toolbar.o build\obj\widgets\button.o build\obj\widgets\calligraphy-toolbar.o build\obj\widgets\connector-toolbar.o build\obj\widgets\dash-selector.o build\obj\widgets\desktop-widget.o build\obj\widgets\dropper-toolbar.o build\obj\widgets\eek-preview.o build\obj\widgets\ege-adjustment-action.o build\obj\widgets\ege-output-action.o build\obj\widgets\ege-paint-def.o build\obj\widgets\ege-select-one-action.o build\obj\widgets\eraser-toolbar.o build\obj\widgets\fill-style.o build\obj\widgets\font-selector.o build\obj\widgets\gradient-image.o build\obj\widgets\gradient-selector.o build\obj\widgets\gradient-toolbar.o build\obj\widgets\gradient-vector.o build\obj\widgets\icon.o build\obj\widgets\ink-action.o build\obj\widgets\ink-comboboxentry-action.o build\obj\widgets\lpe-toolbar.o build\obj\widgets\measure-toolbar.o build\obj\widgets\mesh-toolbar.o build\obj\widgets\node-toolbar.o build\obj\widgets\paint-selector.o build\obj\widgets\paintbucket-toolbar.o build\obj\widgets\pencil-toolbar.o build\obj\widgets\rect-toolbar.o build\obj\widgets\ruler.o build\obj\widgets\select-toolbar.o build\obj\widgets\shrink-wrap-button.o build\obj\widgets\sp-attribute-widget.o build\obj\widgets\sp-color-selector.o build\obj\widgets\sp-widget.o build\obj\widgets\sp-xmlview-attr-list.o build\obj\widgets\sp-xmlview-content.o build\obj\widgets\sp-xmlview-tree.o build\obj\widgets\spinbutton-events.o build\obj\widgets\spiral-toolbar.o build\obj\widgets\spray-toolbar.o build\obj\widgets\spw-utilities.o build\obj\widgets\star-toolbar.o build\obj\widgets\stroke-marker-selector.o build\obj\widgets\stroke-style.o build\obj\widgets\swatch-selector.o build\obj\widgets\text-toolbar.o build\obj\widgets\toolbox.o build\obj\widgets\tweak-toolbar.o build\obj\widgets\zoom-toolbar.o build\obj\winmain.o build\obj\xml\composite-node-observer.o build\obj\xml\croco-node-iface.o build\obj\xml\event.o build\obj\xml\helper-observer.o build\obj\xml\log-builder.o build\obj\xml\node-fns.o build\obj\xml\quote.o build\obj\xml\rebase-hrefs.o build\obj\xml\repr-css.o build\obj\xml\repr-io.o build\obj\xml\repr-sorting.o build\obj\xml\repr-util.o build\obj\xml\repr.o build\obj\xml\simple-document.o build\obj\xml\simple-node.o build\obj\xml\subtree.o -L/opt/lib -LE:\Temp\Downloads\Inkscape\build\devlibs64/lib -Wl,-luuid -lMagick++-6.Q16 -lMagickCore-6.Q16 -lMagickWand-6.Q16 -latk-1.0 -latkmm-1.6 -lcairo -lcairomm-1.0 -lcdr-0.0 -lcomdlg32 -lexif -lfontconfig -lfreetype -lgc -lgdi32 -lgdk-win32-2.0 -lgdk_pixbuf-2.0 -lgdkmm-2.4 -lgio-2.0 -lgiomm-2.4 -lglib-2.0 -lglibmm-2.4 -lgobject-2.0 -lgomp -lgsl -lgslcblas -lgthread-2.0 -lgtk-win32-2.0 -lgtkmm-2.4 -liconv -limm32 -lintl -ljpeg -llcms2 -lm -lmscms -lole32 -lpango-1.0 -lpangocairo-1.0 -lpangoft2-1.0 -lpangomm-1.4 -lpangowin32-1.0 -lpng -lpoppler -lpoppler-glib -lpopt -lpotrace -lshell32 -lsigc-2.0 -ltiff -lvisio-0.0 -lwinpthread-1 -lwpd-0.9 -lwpd-stream-0.9 -lwpg-0.2 -lws2_32 -lz E:\Temp\Downloads\Inkscape\build\devlibs64/bin/libexslt-0.dll E:\Temp\Downloads\Inkscape\build\devlibs64/bin/libxml2-2.dll E:\Temp\Downloads\Inkscape\build\devlibs64/bin/libxslt-1.dll
Any idea what's going wrong (and how to fix it)?
Regards, Eduard
Am 23.01.2016 um 21:22 schrieb Eduard Braun:
Am 23.01.2016 um 20:28 schrieb Partha Bagchi:
On Sat, Jan 23, 2016 at 1:06 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
I finally got around to have a look at the 64-bit devlibs Partha provided. I'm afraid however that I didn't succeed to build Inkscape with them yet (this is really not my area of expertise so any help is *very* welcome!).
I'll take a look into building it for you if that helps?
Obviously you have more experience, so I guess you'd be able to figure out what is going wrong. Probably it's just some stupid error of mine which would be trivial to fix ;-). I don't want you to feel obliged, though, especially with respect to my next comment...
What I noticed so far: The new devlibs are based on a MinGW build with win32 threads and SEH exception handling (possibly x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z, see [1]) whereas the old devlibs are based on MinGW with posix threads and SJLJ exception handling (x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z, see [2]).
I think the previous 64-bit devlibs were also built with SEH and using 4.9.2. See this thread: http://sourceforge.net/p/inkscape/mailman/message/34099214/
Oh, wow, I didn't know about these... I based my work on the latest 64-bit devlibs available on launchpad (https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk) and those date back to 2014 (with the readme stating posix/sjlj was in use, no idea if that's correct). I assume your updated builds never made it into the public repository.
So my first question is if this would work with Inkscape in principle? Not that I (or anybody else) try to make something work that can not work to start with...
In case win32 threads and SEH exception handling are OK for Inkscape I suppose we'd also need to rebuild all other dependencies with the new compiler? (Again, I have no clue about these things, but from what I got from a quick Internet search the old and new binaries are not compatible?)
Which other dependencies need to be built?
Only those I listed... some of these are in your package from 2015-05-10, though, so a new built might not be necessary.
Libraries that I spotted which are currently not included in the new devlibs-package:
gtkmm/gdkmm 2.4 (the package includes only 3.0)
gtkmm 2.4 series is out dated. Do we still use it? With the move to GTK3, this should not be needed?
As far as I know GTK3 is still experimental, normal builds still use GTK2.
aspell
aspell is optional.
Yes, sorry for not being more specific. We have it i current builds but I assume it's not mandatory.
ImageMagick
Oops, my bad. I'll update the libs.
Thanks, no problem!
poppler-data (for eastern-character support)
ditto.
librevenge (optional if we want to include newer versions of the various import libraries [3])
OK, I'll build this too.
Regards, Eduard
[1] http://www.partha.com/temp/Readme.txt [2] http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/view/head... [3] http://www.documentliberation.org/projects/
Am 17.01.2016 um 20:34 schrieb Partha Bagchi:
Hi Eduard,
I have uploaded the Windows 64bit devlibs here: http://www.partha.com/temp/inkscape-devlibs.7z
Can you (or someone) upload it to its final destination? The devlibs include potrace 1.13.
Please let me know if you have any questions.
Thanks, Partha
On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
If you have some time this weekend, then adding potrace to the 64bit devlibs should probably be a high priority. Right now it breaks 64bit builds since it seems the logic for excluding code depending on potrace if it's not available does not work for btool-based builds (at least I was not able to make it work)
Regards, Eduard
Am 11.01.2016 um 11:42 schrieb Partha Bagchi:
On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> wrote: ...
To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs?
There are some points we need to take into consideration (I probably forgot some):
- The new devlibs must be easier to maintain compared to the current
ones.
- It should be possible to use the same steps to update win32 and win64
devlibs.
- If both devlibs could provide exactly the same packages versions, it
would greatly help bug tracking (and fixing)...
- Do we still need to link libstdc++ statically? (Opensuse cross-compiled
packages need a shared library.)
Regards,
Nicolas
Nicolas,
I build my 64bit libs from scratch. I use MSYS as my shell if you will and gcc 5.1.0 as my compiler.
No, I don't think you have to statically link libstdc++.
I'll try to provide a 64bit devlibs build this weekend if that's not too late.
Thanks, Partha
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Seems my last mail didn't get through (probably because of pasted text), so here we go again...
I can't seem to get the win64 build working. Inkscape is compiling fine but I'm always getting linker errors:
https://inkscape.org/de/gallery/item/7421/
Here's the command used by btool:
https://inkscape.org/de/gallery/item/7426/
Any idea what's going wrong (and how to fix it)?
Regards, Eduard
Am 23.01.2016 um 21:22 schrieb Eduard Braun:
Am 23.01.2016 um 20:28 schrieb Partha Bagchi:
On Sat, Jan 23, 2016 at 1:06 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
I finally got around to have a look at the 64-bit devlibs Partha provided. I'm afraid however that I didn't succeed to build Inkscape with them yet (this is really not my area of expertise so any help is *very* welcome!).
I'll take a look into building it for you if that helps?
Obviously you have more experience, so I guess you'd be able to figure out what is going wrong. Probably it's just some stupid error of mine which would be trivial to fix ;-). I don't want you to feel obliged, though, especially with respect to my next comment...
What I noticed so far: The new devlibs are based on a MinGW build with win32 threads and SEH exception handling (possibly x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z, see [1]) whereas the old devlibs are based on MinGW with posix threads and SJLJ exception handling (x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z, see [2]).
I think the previous 64-bit devlibs were also built with SEH and using 4.9.2. See this thread: http://sourceforge.net/p/inkscape/mailman/message/34099214/
Oh, wow, I didn't know about these... I based my work on the latest 64-bit devlibs available on launchpad (https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk) and those date back to 2014 (with the readme stating posix/sjlj was in use, no idea if that's correct). I assume your updated builds never made it into the public repository.
So my first question is if this would work with Inkscape in principle? Not that I (or anybody else) try to make something work that can not work to start with...
In case win32 threads and SEH exception handling are OK for Inkscape I suppose we'd also need to rebuild all other dependencies with the new compiler? (Again, I have no clue about these things, but from what I got from a quick Internet search the old and new binaries are not compatible?)
Which other dependencies need to be built?
Only those I listed... some of these are in your package from 2015-05-10, though, so a new built might not be necessary.
Libraries that I spotted which are currently not included in the new devlibs-package:
gtkmm/gdkmm 2.4 (the package includes only 3.0)
gtkmm 2.4 series is out dated. Do we still use it? With the move to GTK3, this should not be needed?
As far as I know GTK3 is still experimental, normal builds still use GTK2.
aspell
aspell is optional.
Yes, sorry for not being more specific. We have it i current builds but I assume it's not mandatory.
ImageMagick
Oops, my bad. I'll update the libs.
Thanks, no problem!
poppler-data (for eastern-character support)
ditto.
librevenge (optional if we want to include newer versions of the various import libraries [3])
OK, I'll build this too.
Regards, Eduard
[1] http://www.partha.com/temp/Readme.txt [2] http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/view/head...
[3] http://www.documentliberation.org/projects/
Am 17.01.2016 um 20:34 schrieb Partha Bagchi:
Hi Eduard,
I have uploaded the Windows 64bit devlibs here: http://www.partha.com/temp/inkscape-devlibs.7z
Can you (or someone) upload it to its final destination? The devlibs include potrace 1.13.
Please let me know if you have any questions.
Thanks, Partha
On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
If you have some time this weekend, then adding potrace to the 64bit devlibs should probably be a high priority. Right now it breaks 64bit builds since it seems the logic for excluding code depending on potrace if it's not available does not work for btool-based builds (at least I was not able to make it work)
Regards, Eduard
Am 11.01.2016 um 11:42 schrieb Partha Bagchi:
On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> wrote: ...
To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs?
There are some points we need to take into consideration (I probably forgot some):
- The new devlibs must be easier to maintain compared to the current
ones.
- It should be possible to use the same steps to update win32 and win64
devlibs.
- If both devlibs could provide exactly the same packages versions, it
would greatly help bug tracking (and fixing)...
- Do we still need to link libstdc++ statically? (Opensuse
cross-compiled packages need a shared library.)
Regards,
Nicolas
Nicolas,
I build my 64bit libs from scratch. I use MSYS as my shell if you will and gcc 5.1.0 as my compiler.
No, I don't think you have to statically link libstdc++.
I'll try to provide a 64bit devlibs build this weekend if that's not too late.
Thanks, Partha
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Eduard,
I have updated the devlibs with the missing libraries. it now includes the Readme.txt in the base folder. Please download from the same place.
I didn't have issues with building inkscape-r14615. My command line was: ./configure --prefix=/opt/inkscape --build=x86_64-w64-mingw32 LIBS="-L/opt/lib -L/usr/python/Lib" CPPFLAGS="-I/opt/include -I/usr/python/include" CFLAGS="-w -O3 -ffast-math -ftree-vectorize" CXXFLAGS="-w -std=c++11 -O3 -ffast-math -ftree-vectorize"
The boost notes and warnings are annoying and so I suppressed them. :)
Since a whole bunch M_PI, M_PI_2, etc are undefined due to using -std=c++11, I modified the source by hand to fix those. Also, couple of files have WIN32 defined as opposed to _WIN32.
Please let me know if you have any questions.
Thanks, Partha
On Sun, Jan 24, 2016 at 10:18 AM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Seems my last mail didn't get through (probably because of pasted text), so here we go again...
I can't seem to get the win64 build working. Inkscape is compiling fine but I'm always getting linker errors:
https://inkscape.org/de/gallery/item/7421/
Here's the command used by btool:
https://inkscape.org/de/gallery/item/7426/
Any idea what's going wrong (and how to fix it)?
Regards, Eduard
Am 23.01.2016 um 21:22 schrieb Eduard Braun:
Am 23.01.2016 um 20:28 schrieb Partha Bagchi:
On Sat, Jan 23, 2016 at 1:06 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
I finally got around to have a look at the 64-bit devlibs Partha provided. I'm afraid however that I didn't succeed to build Inkscape with them yet (this is really not my area of expertise so any help is *very* welcome!).
I'll take a look into building it for you if that helps?
Obviously you have more experience, so I guess you'd be able to figure out what is going wrong. Probably it's just some stupid error of mine which would be trivial to fix ;-). I don't want you to feel obliged, though, especially with respect to my next comment...
What I noticed so far: The new devlibs are based on a MinGW build with win32 threads and SEH exception handling (possibly x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z, see [1]) whereas the old devlibs are based on MinGW with posix threads and SJLJ exception handling (x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z, see [2]).
I think the previous 64-bit devlibs were also built with SEH and using 4.9.2. See this thread: http://sourceforge.net/p/inkscape/mailman/message/34099214/
Oh, wow, I didn't know about these... I based my work on the latest 64-bit devlibs available on launchpad (https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk) and those date back to 2014 (with the readme stating posix/sjlj was in use, no idea if that's correct). I assume your updated builds never made it into the public repository.
So my first question is if this would work with Inkscape in principle? Not that I (or anybody else) try to make something work that can not work to start with...
In case win32 threads and SEH exception handling are OK for Inkscape I suppose we'd also need to rebuild all other dependencies with the new compiler? (Again, I have no clue about these things, but from what I got from a quick Internet search the old and new binaries are not compatible?)
Which other dependencies need to be built?
Only those I listed... some of these are in your package from 2015-05-10, though, so a new built might not be necessary.
Libraries that I spotted which are currently not included in the new devlibs-package:
gtkmm/gdkmm 2.4 (the package includes only 3.0)
gtkmm 2.4 series is out dated. Do we still use it? With the move to GTK3, this should not be needed?
As far as I know GTK3 is still experimental, normal builds still use GTK2.
aspell
aspell is optional.
Yes, sorry for not being more specific. We have it i current builds but I assume it's not mandatory.
ImageMagick
Oops, my bad. I'll update the libs.
Thanks, no problem!
poppler-data (for eastern-character support)
ditto.
librevenge (optional if we want to include newer versions of the various import libraries [3])
OK, I'll build this too.
Regards, Eduard
[1] http://www.partha.com/temp/Readme.txt [2]
http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/view/head... [3] http://www.documentliberation.org/projects/
Am 17.01.2016 um 20:34 schrieb Partha Bagchi:
Hi Eduard,
I have uploaded the Windows 64bit devlibs here: http://www.partha.com/temp/inkscape-devlibs.7z
Can you (or someone) upload it to its final destination? The devlibs include potrace 1.13.
Please let me know if you have any questions.
Thanks, Partha
On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
If you have some time this weekend, then adding potrace to the 64bit devlibs should probably be a high priority. Right now it breaks 64bit builds since it seems the logic for excluding code depending on potrace if it's not available does not work for btool-based builds (at least I was not able to make it work)
Regards, Eduard
Am 11.01.2016 um 11:42 schrieb Partha Bagchi:
On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> wrote: ...
To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs?
There are some points we need to take into consideration (I probably forgot some):
- The new devlibs must be easier to maintain compared to the current
ones.
- It should be possible to use the same steps to update win32 and win64
devlibs.
- If both devlibs could provide exactly the same packages versions, it
would greatly help bug tracking (and fixing)...
- Do we still need to link libstdc++ statically? (Opensuse
cross-compiled packages need a shared library.)
Regards,
Nicolas
Nicolas,
I build my 64bit libs from scratch. I use MSYS as my shell if you will and gcc 5.1.0 as my compiler.
No, I don't think you have to statically link libstdc++.
I'll try to provide a 64bit devlibs build this weekend if that's not too late.
Thanks, Partha
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Eduard,
I included my inkscape build in the devlibs inadvertently. Sorry about that. You can delete it.
Thanks, Partha
On Sun, Jan 24, 2016 at 5:07 PM, Partha Bagchi <partha1b@...400...> wrote:
Eduard,
I have updated the devlibs with the missing libraries. it now includes the Readme.txt in the base folder. Please download from the same place.
I didn't have issues with building inkscape-r14615. My command line was: ./configure --prefix=/opt/inkscape --build=x86_64-w64-mingw32 LIBS="-L/opt/lib -L/usr/python/Lib" CPPFLAGS="-I/opt/include -I/usr/python/include" CFLAGS="-w -O3 -ffast-math -ftree-vectorize" CXXFLAGS="-w -std=c++11 -O3 -ffast-math -ftree-vectorize"
The boost notes and warnings are annoying and so I suppressed them. :)
Since a whole bunch M_PI, M_PI_2, etc are undefined due to using -std=c++11, I modified the source by hand to fix those. Also, couple of files have WIN32 defined as opposed to _WIN32.
Please let me know if you have any questions.
Thanks, Partha
On Sun, Jan 24, 2016 at 10:18 AM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Seems my last mail didn't get through (probably because of pasted text), so here we go again...
I can't seem to get the win64 build working. Inkscape is compiling fine but I'm always getting linker errors:
https://inkscape.org/de/gallery/item/7421/
Here's the command used by btool:
https://inkscape.org/de/gallery/item/7426/
Any idea what's going wrong (and how to fix it)?
Regards, Eduard
Am 23.01.2016 um 21:22 schrieb Eduard Braun:
Am 23.01.2016 um 20:28 schrieb Partha Bagchi:
On Sat, Jan 23, 2016 at 1:06 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
I finally got around to have a look at the 64-bit devlibs Partha provided. I'm afraid however that I didn't succeed to build Inkscape with them yet (this is really not my area of expertise so any help is *very* welcome!).
I'll take a look into building it for you if that helps?
Obviously you have more experience, so I guess you'd be able to figure out what is going wrong. Probably it's just some stupid error of mine which would be trivial to fix ;-). I don't want you to feel obliged, though, especially with respect to my next comment...
What I noticed so far: The new devlibs are based on a MinGW build with win32 threads and SEH exception handling (possibly x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z, see [1]) whereas the old devlibs are based on MinGW with posix threads and SJLJ exception handling (x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z, see [2]).
I think the previous 64-bit devlibs were also built with SEH and using 4.9.2. See this thread: http://sourceforge.net/p/inkscape/mailman/message/34099214/
Oh, wow, I didn't know about these... I based my work on the latest 64-bit devlibs available on launchpad (https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk) and those date back to 2014 (with the readme stating posix/sjlj was in use, no idea if that's correct). I assume your updated builds never made it into the public repository.
So my first question is if this would work with Inkscape in principle? Not that I (or anybody else) try to make something work that can not work to start with...
In case win32 threads and SEH exception handling are OK for Inkscape I suppose we'd also need to rebuild all other dependencies with the new compiler? (Again, I have no clue about these things, but from what I got from a quick Internet search the old and new binaries are not compatible?)
Which other dependencies need to be built?
Only those I listed... some of these are in your package from 2015-05-10, though, so a new built might not be necessary.
Libraries that I spotted which are currently not included in the new devlibs-package:
gtkmm/gdkmm 2.4 (the package includes only 3.0)
gtkmm 2.4 series is out dated. Do we still use it? With the move to GTK3, this should not be needed?
As far as I know GTK3 is still experimental, normal builds still use GTK2.
aspell
aspell is optional.
Yes, sorry for not being more specific. We have it i current builds but I assume it's not mandatory.
ImageMagick
Oops, my bad. I'll update the libs.
Thanks, no problem!
poppler-data (for eastern-character support)
ditto.
librevenge (optional if we want to include newer versions of the various import libraries [3])
OK, I'll build this too.
Regards, Eduard
[1] http://www.partha.com/temp/Readme.txt [2]
http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/view/head... [3] http://www.documentliberation.org/projects/
Am 17.01.2016 um 20:34 schrieb Partha Bagchi:
Hi Eduard,
I have uploaded the Windows 64bit devlibs here: http://www.partha.com/temp/inkscape-devlibs.7z
Can you (or someone) upload it to its final destination? The devlibs include potrace 1.13.
Please let me know if you have any questions.
Thanks, Partha
On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
If you have some time this weekend, then adding potrace to the 64bit devlibs should probably be a high priority. Right now it breaks 64bit builds since it seems the logic for excluding code depending on potrace if it's not available does not work for btool-based builds (at least I was not able to make it work)
Regards, Eduard
Am 11.01.2016 um 11:42 schrieb Partha Bagchi:
On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> wrote: ...
To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs?
There are some points we need to take into consideration (I probably forgot some):
- The new devlibs must be easier to maintain compared to the current
ones.
- It should be possible to use the same steps to update win32 and win64
devlibs.
- If both devlibs could provide exactly the same packages versions, it
would greatly help bug tracking (and fixing)...
- Do we still need to link libstdc++ statically? (Opensuse
cross-compiled packages need a shared library.)
Regards,
Nicolas
Nicolas,
I build my 64bit libs from scratch. I use MSYS as my shell if you will and gcc 5.1.0 as my compiler.
No, I don't think you have to statically link libstdc++.
I'll try to provide a 64bit devlibs build this weekend if that's not too late.
Thanks, Partha
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi Partha,
thanks for the update! Inkscape compiles (and links!) fine now, also when using btool. When using "-std=gnu++0x" it's not even necessary to modify any files (or might this cause any issues?).
However I'm afraid while compiling works, running does not. Inkscape doesn't even open before it closes with an internal error... GDB tells me the error is in gdk_pixbuf_rotate_simple () inlibgdk_pixbuf-2.0-0.dll
A quick test shows your "forgotten build" might have the same issue? Running inkscape -g fails with (inkscape.exe:7532): GdkPixbuf-CRITICAL **: gdk_pixbuf_read_pixels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed for me. Did it work for work for you?
Good night, Eduard
Am 24.01.2016 um 23:07 schrieb Partha Bagchi:
Eduard,
I have updated the devlibs with the missing libraries. it now includes the Readme.txt in the base folder. Please download from the same place.
I didn't have issues with building inkscape-r14615. My command line was: ./configure --prefix=/opt/inkscape --build=x86_64-w64-mingw32 LIBS="-L/opt/lib -L/usr/python/Lib" CPPFLAGS="-I/opt/include -I/usr/python/include" CFLAGS="-w -O3 -ffast-math -ftree-vectorize" CXXFLAGS="-w -std=c++11 -O3 -ffast-math -ftree-vectorize"
The boost notes and warnings are annoying and so I suppressed them. :)
Since a whole bunch M_PI, M_PI_2, etc are undefined due to using -std=c++11, I modified the source by hand to fix those. Also, couple of files have WIN32 defined as opposed to _WIN32.
Please let me know if you have any questions.
Thanks, Partha
On Sun, Jan 24, 2016 at 10:18 AM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Seems my last mail didn't get through (probably because of pasted text), so here we go again...
I can't seem to get the win64 build working. Inkscape is compiling fine but I'm always getting linker errors:
https://inkscape.org/de/gallery/item/7421/
Here's the command used by btool:
https://inkscape.org/de/gallery/item/7426/
Any idea what's going wrong (and how to fix it)?
Regards, Eduard
Am 23.01.2016 um 21:22 schrieb Eduard Braun:
Am 23.01.2016 um 20:28 schrieb Partha Bagchi:
On Sat, Jan 23, 2016 at 1:06 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
I finally got around to have a look at the 64-bit devlibs Partha provided. I'm afraid however that I didn't succeed to build Inkscape with them yet (this is really not my area of expertise so any help is *very* welcome!).
I'll take a look into building it for you if that helps?
Obviously you have more experience, so I guess you'd be able to figure out what is going wrong. Probably it's just some stupid error of mine which would be trivial to fix ;-). I don't want you to feel obliged, though, especially with respect to my next comment...
What I noticed so far: The new devlibs are based on a MinGW build with win32 threads and SEH exception handling (possibly x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z, see [1]) whereas the old devlibs are based on MinGW with posix threads and SJLJ exception handling (x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z, see [2]).
I think the previous 64-bit devlibs were also built with SEH and using 4.9.2. See this thread: http://sourceforge.net/p/inkscape/mailman/message/34099214/
Oh, wow, I didn't know about these... I based my work on the latest 64-bit devlibs available on launchpad (https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk) and those date back to 2014 (with the readme stating posix/sjlj was in use, no idea if that's correct). I assume your updated builds never made it into the public repository.
So my first question is if this would work with Inkscape in principle? Not that I (or anybody else) try to make something work that can not work to start with...
In case win32 threads and SEH exception handling are OK for Inkscape I suppose we'd also need to rebuild all other dependencies with the new compiler? (Again, I have no clue about these things, but from what I got from a quick Internet search the old and new binaries are not compatible?)
Which other dependencies need to be built?
Only those I listed... some of these are in your package from 2015-05-10, though, so a new built might not be necessary.
Libraries that I spotted which are currently not included in the new devlibs-package:
gtkmm/gdkmm 2.4 (the package includes only 3.0)
gtkmm 2.4 series is out dated. Do we still use it? With the move to GTK3, this should not be needed?
As far as I know GTK3 is still experimental, normal builds still use GTK2.
aspell
aspell is optional.
Yes, sorry for not being more specific. We have it i current builds but I assume it's not mandatory.
ImageMagick
Oops, my bad. I'll update the libs.
Thanks, no problem!
poppler-data (for eastern-character support)
ditto.
librevenge (optional if we want to include newer versions of the various import libraries [3])
OK, I'll build this too.
Regards, Eduard
[1] http://www.partha.com/temp/Readme.txt [2]
http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/view/head... [3] http://www.documentliberation.org/projects/
Am 17.01.2016 um 20:34 schrieb Partha Bagchi:
Hi Eduard,
I have uploaded the Windows 64bit devlibs here: http://www.partha.com/temp/inkscape-devlibs.7z
Can you (or someone) upload it to its final destination? The devlibs include potrace 1.13.
Please let me know if you have any questions.
Thanks, Partha
On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
If you have some time this weekend, then adding potrace to the 64bit devlibs should probably be a high priority. Right now it breaks 64bit builds since it seems the logic for excluding code depending on potrace if it's not available does not work for btool-based builds (at least I was not able to make it work)
Regards, Eduard
Am 11.01.2016 um 11:42 schrieb Partha Bagchi:
On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> wrote: ...
To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs?
There are some points we need to take into consideration (I probably forgot some):
- The new devlibs must be easier to maintain compared to the current
ones.
- It should be possible to use the same steps to update win32 and win64
devlibs.
- If both devlibs could provide exactly the same packages versions, it
would greatly help bug tracking (and fixing)...
- Do we still need to link libstdc++ statically? (Opensuse
cross-compiled packages need a shared library.)
Regards,
Nicolas
Nicolas,
I build my 64bit libs from scratch. I use MSYS as my shell if you will and gcc 5.1.0 as my compiler.
No, I don't think you have to statically link libstdc++.
I'll try to provide a 64bit devlibs build this weekend if that's not too late.
Thanks, Partha
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi Eduard,
It's that gdiplus bug again and I had forgotten about it!! :(
I've re-uploaded the devlibs. You should be OK now. Please check.
I think we should use -std=c++11 which is standard don't you think?
Thanks, Partha
PS: seems like now I have to use inkscape -g to open the gui. :(
On Sun, Jan 24, 2016 at 9:14 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Hi Partha,
thanks for the update! Inkscape compiles (and links!) fine now, also when using btool. When using "-std=gnu++0x" it's not even necessary to modify any files (or might this cause any issues?).
However I'm afraid while compiling works, running does not. Inkscape doesn't even open before it closes with an internal error... GDB tells me the error is in gdk_pixbuf_rotate_simple () inlibgdk_pixbuf-2.0-0.dll
A quick test shows your "forgotten build" might have the same issue? Running inkscape -g fails with (inkscape.exe:7532): GdkPixbuf-CRITICAL **: gdk_pixbuf_read_pixels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed for me. Did it work for work for you?
Good night, Eduard
Am 24.01.2016 um 23:07 schrieb Partha Bagchi:
Eduard,
I have updated the devlibs with the missing libraries. it now includes the Readme.txt in the base folder. Please download from the same place.
I didn't have issues with building inkscape-r14615. My command line was: ./configure --prefix=/opt/inkscape --build=x86_64-w64-mingw32 LIBS="-L/opt/lib -L/usr/python/Lib" CPPFLAGS="-I/opt/include -I/usr/python/include" CFLAGS="-w -O3 -ffast-math -ftree-vectorize" CXXFLAGS="-w -std=c++11 -O3 -ffast-math -ftree-vectorize"
The boost notes and warnings are annoying and so I suppressed them. :)
Since a whole bunch M_PI, M_PI_2, etc are undefined due to using -std=c++11, I modified the source by hand to fix those. Also, couple of files have WIN32 defined as opposed to _WIN32.
Please let me know if you have any questions.
Thanks, Partha
On Sun, Jan 24, 2016 at 10:18 AM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Seems my last mail didn't get through (probably because of pasted text), so here we go again...
I can't seem to get the win64 build working. Inkscape is compiling fine but I'm always getting linker errors:
https://inkscape.org/de/gallery/item/7421/
Here's the command used by btool:
https://inkscape.org/de/gallery/item/7426/
Any idea what's going wrong (and how to fix it)?
Regards, Eduard
Am 23.01.2016 um 21:22 schrieb Eduard Braun:
Am 23.01.2016 um 20:28 schrieb Partha Bagchi:
On Sat, Jan 23, 2016 at 1:06 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
I finally got around to have a look at the 64-bit devlibs Partha provided. I'm afraid however that I didn't succeed to build Inkscape with them yet (this is really not my area of expertise so any help is *very* welcome!).
I'll take a look into building it for you if that helps?
Obviously you have more experience, so I guess you'd be able to figure out what is going wrong. Probably it's just some stupid error of mine which would be trivial to fix ;-). I don't want you to feel obliged, though, especially with respect to my next comment...
What I noticed so far: The new devlibs are based on a MinGW build with win32 threads and SEH exception handling (possibly x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z, see [1]) whereas the old devlibs are based on MinGW with posix threads and SJLJ exception handling (x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z, see [2]).
I think the previous 64-bit devlibs were also built with SEH and using 4.9.2. See this thread: http://sourceforge.net/p/inkscape/mailman/message/34099214/
Oh, wow, I didn't know about these... I based my work on the latest 64-bit devlibs available on launchpad (https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk) and those date back to 2014 (with the readme stating posix/sjlj was in use, no idea if that's correct). I assume your updated builds never made it into the public repository.
So my first question is if this would work with Inkscape in principle? Not that I (or anybody else) try to make something work that can not work to start with...
In case win32 threads and SEH exception handling are OK for Inkscape I suppose we'd also need to rebuild all other dependencies with the new compiler? (Again, I have no clue about these things, but from what I got from a quick Internet search the old and new binaries are not compatible?)
Which other dependencies need to be built?
Only those I listed... some of these are in your package from 2015-05-10, though, so a new built might not be necessary.
Libraries that I spotted which are currently not included in the new devlibs-package:
gtkmm/gdkmm 2.4 (the package includes only 3.0)
gtkmm 2.4 series is out dated. Do we still use it? With the move to GTK3, this should not be needed?
As far as I know GTK3 is still experimental, normal builds still use GTK2.
aspell
aspell is optional.
Yes, sorry for not being more specific. We have it i current builds but I assume it's not mandatory.
ImageMagick
Oops, my bad. I'll update the libs.
Thanks, no problem!
poppler-data (for eastern-character support)
ditto.
librevenge (optional if we want to include newer versions of the various import libraries [3])
OK, I'll build this too.
Regards, Eduard
[1] http://www.partha.com/temp/Readme.txt [2]
http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/view/head... [3] http://www.documentliberation.org/projects/
Am 17.01.2016 um 20:34 schrieb Partha Bagchi:
Hi Eduard,
I have uploaded the Windows 64bit devlibs here: http://www.partha.com/temp/inkscape-devlibs.7z
Can you (or someone) upload it to its final destination? The devlibs include potrace 1.13.
Please let me know if you have any questions.
Thanks, Partha
On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
If you have some time this weekend, then adding potrace to the 64bit devlibs should probably be a high priority. Right now it breaks 64bit builds since it seems the logic for excluding code depending on potrace if it's not available does not work for btool-based builds (at least I was not able to make it work)
Regards, Eduard
Am 11.01.2016 um 11:42 schrieb Partha Bagchi:
On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> wrote: ...
To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs?
There are some points we need to take into consideration (I probably forgot some):
- The new devlibs must be easier to maintain compared to the current
ones.
- It should be possible to use the same steps to update win32 and
win64 devlibs.
- If both devlibs could provide exactly the same packages versions, it
would greatly help bug tracking (and fixing)...
- Do we still need to link libstdc++ statically? (Opensuse
cross-compiled packages need a shared library.)
Regards,
Nicolas
Nicolas,
I build my 64bit libs from scratch. I use MSYS as my shell if you will and gcc 5.1.0 as my compiler.
No, I don't think you have to statically link libstdc++.
I'll try to provide a 64bit devlibs build this weekend if that's not too late.
Thanks, Partha
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi Partha,
great! I was already afraid we'd have to dig deeply to find the cause, but you solved it in no time. Is this bug (and the fix you applied) documented somewhere so it does not get lost for future reference?
In that regard also allow me to ask: Did you explain somewhere how you build your libraries? This might prove immensely valuable in case a library needs to be added or requires an update in the future... Not that I (and possibly others) won't enjoy bugging you with it and letting you do all the work ;-), but I assume it would be more efficient if the general built process was known to some people so minor updates could be implemented on-the-fly.
I'll test the updated devlibs this evening and see if it fixes all issues for me.
Regards and thanks again, Eduard
Am 25.01.2016 um 15:39 schrieb Partha Bagchi:
Hi Eduard,
It's that gdiplus bug again and I had forgotten about it!! :(
I've re-uploaded the devlibs. You should be OK now. Please check.
I think we should use -std=c++11 which is standard don't you think?
Thanks, Partha
PS: seems like now I have to use inkscape -g to open the gui. :(
On Sun, Jan 24, 2016 at 9:14 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Hi Partha,
thanks for the update! Inkscape compiles (and links!) fine now, also when using btool. When using "-std=gnu++0x" it's not even necessary to modify any files (or might this cause any issues?).
However I'm afraid while compiling works, running does not. Inkscape doesn't even open before it closes with an internal error... GDB tells me the error is in gdk_pixbuf_rotate_simple () inlibgdk_pixbuf-2.0-0.dll
A quick test shows your "forgotten build" might have the same issue? Running inkscape -g fails with (inkscape.exe:7532): GdkPixbuf-CRITICAL **: gdk_pixbuf_read_pixels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed for me. Did it work for work for you?
Good night, Eduard
Am 24.01.2016 um 23:07 schrieb Partha Bagchi:
Eduard,
I have updated the devlibs with the missing libraries. it now includes the Readme.txt in the base folder. Please download from the same place.
I didn't have issues with building inkscape-r14615. My command line was: ./configure --prefix=/opt/inkscape --build=x86_64-w64-mingw32 LIBS="-L/opt/lib -L/usr/python/Lib" CPPFLAGS="-I/opt/include -I/usr/python/include" CFLAGS="-w -O3 -ffast-math -ftree-vectorize" CXXFLAGS="-w -std=c++11 -O3 -ffast-math -ftree-vectorize"
The boost notes and warnings are annoying and so I suppressed them. :)
Since a whole bunch M_PI, M_PI_2, etc are undefined due to using -std=c++11, I modified the source by hand to fix those. Also, couple of files have WIN32 defined as opposed to _WIN32.
Please let me know if you have any questions.
Thanks, Partha
On Sun, Jan 24, 2016 at 10:18 AM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Seems my last mail didn't get through (probably because of pasted text), so here we go again...
I can't seem to get the win64 build working. Inkscape is compiling fine but I'm always getting linker errors:
https://inkscape.org/de/gallery/item/7421/
Here's the command used by btool:
https://inkscape.org/de/gallery/item/7426/
Any idea what's going wrong (and how to fix it)?
Regards, Eduard
Am 23.01.2016 um 21:22 schrieb Eduard Braun:
Am 23.01.2016 um 20:28 schrieb Partha Bagchi:
On Sat, Jan 23, 2016 at 1:06 PM, Eduard Braun <Eduard.Braun2@...173...> wrote: > I finally got around to have a look at the 64-bit devlibs Partha > provided. > I'm afraid however that I didn't succeed to build Inkscape with them > yet > (this is really not my area of expertise so any help is *very* > welcome!). > I'll take a look into building it for you if that helps?
Obviously you have more experience, so I guess you'd be able to figure out what is going wrong. Probably it's just some stupid error of mine which would be trivial to fix ;-). I don't want you to feel obliged, though, especially with respect to my next comment...
> What I noticed so far: > The new devlibs are based on a MinGW build with win32 threads and SEH > exception handling (possibly > x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z, > see [1]) whereas the old devlibs are based on MinGW with posix threads > and > SJLJ exception handling > (x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z, > see > [2]). > I think the previous 64-bit devlibs were also built with SEH and using 4.9.2. See this thread: http://sourceforge.net/p/inkscape/mailman/message/34099214/
Oh, wow, I didn't know about these... I based my work on the latest 64-bit devlibs available on launchpad (https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk) and those date back to 2014 (with the readme stating posix/sjlj was in use, no idea if that's correct). I assume your updated builds never made it into the public repository.
> So my first question is if this would work with Inkscape in principle? > Not > that I (or anybody else) try to make something work that can not work > to > start with... > > In case win32 threads and SEH exception handling are OK for Inkscape I > suppose we'd also need to rebuild all other dependencies with the new > compiler? (Again, I have no clue about these things, but from what I > got > from a quick Internet search the old and new binaries are not > compatible?) > Which other dependencies need to be built?
Only those I listed... some of these are in your package from 2015-05-10, though, so a new built might not be necessary.
> Libraries that I spotted which are currently not included in the new > devlibs-package: > > gtkmm/gdkmm 2.4 (the package includes only 3.0) gtkmm 2.4 series is out dated. Do we still use it? With the move to GTK3, this should not be needed?
As far as I know GTK3 is still experimental, normal builds still use GTK2.
> aspell aspell is optional.
Yes, sorry for not being more specific. We have it i current builds but I assume it's not mandatory.
> ImageMagick Oops, my bad. I'll update the libs.
Thanks, no problem!
> poppler-data (for eastern-character support) ditto. > librevenge (optional if we want to include newer versions of the > various > import libraries [3]) > OK, I'll build this too. > Regards, > Eduard > > [1] http://www.partha.com/temp/Readme.txt > [2] > > > http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/view/head... > [3] http://www.documentliberation.org/projects/ > > > Am 17.01.2016 um 20:34 schrieb Partha Bagchi: > > Hi Eduard, > > I have uploaded the Windows 64bit devlibs here: > http://www.partha.com/temp/inkscape-devlibs.7z > > Can you (or someone) upload it to its final destination? The devlibs > include potrace 1.13. > > Please let me know if you have any questions. > > Thanks, > Partha > > > On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173...> > wrote: > > If you have some time this weekend, then adding potrace to the 64bit > devlibs > should probably be a high priority. > Right now it breaks 64bit builds since it seems the logic for > excluding > code > depending on potrace if it's not available does not work for > btool-based > builds (at least I was not able to make it work) > > Regards, > Eduard > > > Am 11.01.2016 um 11:42 schrieb Partha Bagchi: > > On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> > wrote: > ... > > To be honest, I'm a bit lost and can't find the best solution for us. > Could anyone (Partha, Johan, Krzysztof, or someone else) give an > advice? > Partha, how do you build the 64bit devlibs? > > There are some points we need to take into consideration (I probably > forgot some): > * The new devlibs must be easier to maintain compared to the current > ones. > * It should be possible to use the same steps to update win32 and > win64 > devlibs. > * If both devlibs could provide exactly the same packages versions, it > would greatly help bug tracking (and fixing)... > * Do we still need to link libstdc++ statically? (Opensuse > cross-compiled > packages need a shared library.) > > Regards, > -- > Nicolas > > Nicolas, > > I build my 64bit libs from scratch. I use MSYS as my shell if you will > and gcc 5.1.0 as my compiler. > > No, I don't think you have to statically link libstdc++. > > I'll try to provide a 64bit devlibs build this weekend if that's not > too > late. > > Thanks, > Partha > > > > > ------------------------------------------------------------------------------ > 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=267308311&iu=/4140 > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > >
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Mon, Jan 25, 2016 at 10:00 AM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Hi Partha,
great! I was already afraid we'd have to dig deeply to find the cause, but you solved it in no time. Is this bug (and the fix you applied) documented somewhere so it does not get lost for future reference?
I found this reported here https://bugzilla.redhat.com/show_bug.cgi?id=795152#c1 and applied the same reasoning to my builds. So I build gdk-pixbuf with the option --without-gdiplus
In that regard also allow me to ask: Did you explain somewhere how you build your libraries?
Well, I have been meaning to do that but real life always intrudes. :( Anyway, basically I use MSYS as my shell and gcc from the mingW and build all libraries from scratch. I have a specific order in which I build starting with gnu tools/graphics tools/glib/gtk etc. I really should put pencil to paper one of these days when I have more time. In any case, most of my commandlines are similar to what I provided above to build Inkscape. Some of the command lines are of course tailored to specific software such as gdiplus for gdk-pixbuf etc.
This might prove immensely valuable in case a library needs to be added or requires an update in the future...
Yes, I agree.
Not that I (and possibly others) won't enjoy bugging you with it and letting you do all the work ;-), but I assume it would be more efficient if the general built process was known to some people so minor updates could be implemented on-the-fly.
I'll test the updated devlibs this evening and see if it fixes all issues for me.
Yes, please let me know.
Regards and thanks again, Eduard
Am 25.01.2016 um 15:39 schrieb Partha Bagchi:
Hi Eduard,
It's that gdiplus bug again and I had forgotten about it!! :(
I've re-uploaded the devlibs. You should be OK now. Please check.
I think we should use -std=c++11 which is standard don't you think?
Thanks, Partha
PS: seems like now I have to use inkscape -g to open the gui. :(
On Sun, Jan 24, 2016 at 9:14 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Hi Partha,
thanks for the update! Inkscape compiles (and links!) fine now, also when using btool. When using "-std=gnu++0x" it's not even necessary to modify any files (or might this cause any issues?).
However I'm afraid while compiling works, running does not. Inkscape doesn't even open before it closes with an internal error... GDB tells me the error is in gdk_pixbuf_rotate_simple () inlibgdk_pixbuf-2.0-0.dll
A quick test shows your "forgotten build" might have the same issue? Running inkscape -g fails with (inkscape.exe:7532): GdkPixbuf-CRITICAL **: gdk_pixbuf_read_pixels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed for me. Did it work for work for you?
Good night, Eduard
Am 24.01.2016 um 23:07 schrieb Partha Bagchi:
Eduard,
I have updated the devlibs with the missing libraries. it now includes the Readme.txt in the base folder. Please download from the same place.
I didn't have issues with building inkscape-r14615. My command line was: ./configure --prefix=/opt/inkscape --build=x86_64-w64-mingw32 LIBS="-L/opt/lib -L/usr/python/Lib" CPPFLAGS="-I/opt/include -I/usr/python/include" CFLAGS="-w -O3 -ffast-math -ftree-vectorize" CXXFLAGS="-w -std=c++11 -O3 -ffast-math -ftree-vectorize"
The boost notes and warnings are annoying and so I suppressed them. :)
Since a whole bunch M_PI, M_PI_2, etc are undefined due to using -std=c++11, I modified the source by hand to fix those. Also, couple of files have WIN32 defined as opposed to _WIN32.
Please let me know if you have any questions.
Thanks, Partha
On Sun, Jan 24, 2016 at 10:18 AM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Seems my last mail didn't get through (probably because of pasted text), so here we go again...
I can't seem to get the win64 build working. Inkscape is compiling fine but I'm always getting linker errors:
https://inkscape.org/de/gallery/item/7421/
Here's the command used by btool:
https://inkscape.org/de/gallery/item/7426/
Any idea what's going wrong (and how to fix it)?
Regards, Eduard
Am 23.01.2016 um 21:22 schrieb Eduard Braun:
Am 23.01.2016 um 20:28 schrieb Partha Bagchi: > > On Sat, Jan 23, 2016 at 1:06 PM, Eduard Braun <Eduard.Braun2@...173...> > wrote: >> >> I finally got around to have a look at the 64-bit devlibs Partha >> provided. >> I'm afraid however that I didn't succeed to build Inkscape with them >> yet >> (this is really not my area of expertise so any help is *very* >> welcome!). >> > I'll take a look into building it for you if that helps?
Obviously you have more experience, so I guess you'd be able to figure out what is going wrong. Probably it's just some stupid error of mine which would be trivial to fix ;-). I don't want you to feel obliged, though, especially with respect to my next comment... >> >> What I noticed so far: >> The new devlibs are based on a MinGW build with win32 threads and >> SEH >> exception handling (possibly >> x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z, >> see [1]) whereas the old devlibs are based on MinGW with posix >> threads >> and >> SJLJ exception handling >> (x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z, >> see >> [2]). >> > I think the previous 64-bit devlibs were also built with SEH and > using > 4.9.2. See this thread: > http://sourceforge.net/p/inkscape/mailman/message/34099214/
Oh, wow, I didn't know about these... I based my work on the latest 64-bit devlibs available on launchpad (https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk) and those date back to 2014 (with the readme stating posix/sjlj was in use, no idea if that's correct). I assume your updated builds never made it into the public repository. >> >> So my first question is if this would work with Inkscape in >> principle? >> Not >> that I (or anybody else) try to make something work that can not >> work >> to >> start with... >> >> In case win32 threads and SEH exception handling are OK for Inkscape >> I >> suppose we'd also need to rebuild all other dependencies with the >> new >> compiler? (Again, I have no clue about these things, but from what I >> got >> from a quick Internet search the old and new binaries are not >> compatible?) >> > Which other dependencies need to be built?
Only those I listed... some of these are in your package from 2015-05-10, though, so a new built might not be necessary. >> >> Libraries that I spotted which are currently not included in the new >> devlibs-package: >> >> gtkmm/gdkmm 2.4 (the package includes only 3.0) > > gtkmm 2.4 series is out dated. Do we still use it? With the move to > GTK3, this should not be needed?
As far as I know GTK3 is still experimental, normal builds still use GTK2. >> >> aspell > > aspell is optional.
Yes, sorry for not being more specific. We have it i current builds but I assume it's not mandatory. >> >> ImageMagick > > Oops, my bad. I'll update the libs.
Thanks, no problem! >> >> poppler-data (for eastern-character support) > > ditto. >> >> librevenge (optional if we want to include newer versions of the >> various >> import libraries [3]) >> > OK, I'll build this too. >> >> Regards, >> Eduard >> >> [1] http://www.partha.com/temp/Readme.txt >> [2] >> >> >> >> http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/view/head... >> [3] http://www.documentliberation.org/projects/ >> >> >> Am 17.01.2016 um 20:34 schrieb Partha Bagchi: >> >> Hi Eduard, >> >> I have uploaded the Windows 64bit devlibs here: >> http://www.partha.com/temp/inkscape-devlibs.7z >> >> Can you (or someone) upload it to its final destination? The devlibs >> include potrace 1.13. >> >> Please let me know if you have any questions. >> >> Thanks, >> Partha >> >> >> On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173...> >> wrote: >> >> If you have some time this weekend, then adding potrace to the 64bit >> devlibs >> should probably be a high priority. >> Right now it breaks 64bit builds since it seems the logic for >> excluding >> code >> depending on potrace if it's not available does not work for >> btool-based >> builds (at least I was not able to make it work) >> >> Regards, >> Eduard >> >> >> Am 11.01.2016 um 11:42 schrieb Partha Bagchi: >> >> On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> >> wrote: >> ... >> >> To be honest, I'm a bit lost and can't find the best solution for >> us. >> Could anyone (Partha, Johan, Krzysztof, or someone else) give an >> advice? >> Partha, how do you build the 64bit devlibs? >> >> There are some points we need to take into consideration (I probably >> forgot some): >> * The new devlibs must be easier to maintain compared to the current >> ones. >> * It should be possible to use the same steps to update win32 and >> win64 >> devlibs. >> * If both devlibs could provide exactly the same packages versions, >> it >> would greatly help bug tracking (and fixing)... >> * Do we still need to link libstdc++ statically? (Opensuse >> cross-compiled >> packages need a shared library.) >> >> Regards, >> -- >> Nicolas >> >> Nicolas, >> >> I build my 64bit libs from scratch. I use MSYS as my shell if you >> will >> and gcc 5.1.0 as my compiler. >> >> No, I don't think you have to statically link libstdc++. >> >> I'll try to provide a 64bit devlibs build this weekend if that's not >> too >> late. >> >> Thanks, >> Partha >> >> >> >> >> >> ------------------------------------------------------------------------------ >> 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=267308311&iu=/4140 >> _______________________________________________ >> Inkscape-devel mailing list >> Inkscape-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/inkscape-devel >> >>
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
P.S. Regarding -std=c++11 vs. -std=gnu++11 I'll leave the answer to somebody else...
I assumed there's no real reason not to aim for -std=c++11 but since it threw a bunch of errors I simply assumed that -std=gnu++11 was the projects preferred way right know.
Am 25.01.2016 um 15:39 schrieb Partha Bagchi:
Hi Eduard,
It's that gdiplus bug again and I had forgotten about it!! :(
I've re-uploaded the devlibs. You should be OK now. Please check.
I think we should use -std=c++11 which is standard don't you think?
Thanks, Partha
PS: seems like now I have to use inkscape -g to open the gui. :(
On Sun, Jan 24, 2016 at 9:14 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Hi Partha,
thanks for the update! Inkscape compiles (and links!) fine now, also when using btool. When using "-std=gnu++0x" it's not even necessary to modify any files (or might this cause any issues?).
However I'm afraid while compiling works, running does not. Inkscape doesn't even open before it closes with an internal error... GDB tells me the error is in gdk_pixbuf_rotate_simple () inlibgdk_pixbuf-2.0-0.dll
A quick test shows your "forgotten build" might have the same issue? Running inkscape -g fails with (inkscape.exe:7532): GdkPixbuf-CRITICAL **: gdk_pixbuf_read_pixels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed for me. Did it work for work for you?
Good night, Eduard
Am 24.01.2016 um 23:07 schrieb Partha Bagchi:
Eduard,
I have updated the devlibs with the missing libraries. it now includes the Readme.txt in the base folder. Please download from the same place.
I didn't have issues with building inkscape-r14615. My command line was: ./configure --prefix=/opt/inkscape --build=x86_64-w64-mingw32 LIBS="-L/opt/lib -L/usr/python/Lib" CPPFLAGS="-I/opt/include -I/usr/python/include" CFLAGS="-w -O3 -ffast-math -ftree-vectorize" CXXFLAGS="-w -std=c++11 -O3 -ffast-math -ftree-vectorize"
The boost notes and warnings are annoying and so I suppressed them. :)
Since a whole bunch M_PI, M_PI_2, etc are undefined due to using -std=c++11, I modified the source by hand to fix those. Also, couple of files have WIN32 defined as opposed to _WIN32.
Please let me know if you have any questions.
Thanks, Partha
On Sun, Jan 24, 2016 at 10:18 AM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Seems my last mail didn't get through (probably because of pasted text), so here we go again...
I can't seem to get the win64 build working. Inkscape is compiling fine but I'm always getting linker errors:
https://inkscape.org/de/gallery/item/7421/
Here's the command used by btool:
https://inkscape.org/de/gallery/item/7426/
Any idea what's going wrong (and how to fix it)?
Regards, Eduard
Am 23.01.2016 um 21:22 schrieb Eduard Braun:
Am 23.01.2016 um 20:28 schrieb Partha Bagchi:
On Sat, Jan 23, 2016 at 1:06 PM, Eduard Braun <Eduard.Braun2@...173...> wrote: > I finally got around to have a look at the 64-bit devlibs Partha > provided. > I'm afraid however that I didn't succeed to build Inkscape with them > yet > (this is really not my area of expertise so any help is *very* > welcome!). > I'll take a look into building it for you if that helps?
Obviously you have more experience, so I guess you'd be able to figure out what is going wrong. Probably it's just some stupid error of mine which would be trivial to fix ;-). I don't want you to feel obliged, though, especially with respect to my next comment...
> What I noticed so far: > The new devlibs are based on a MinGW build with win32 threads and SEH > exception handling (possibly > x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z, > see [1]) whereas the old devlibs are based on MinGW with posix threads > and > SJLJ exception handling > (x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z, > see > [2]). > I think the previous 64-bit devlibs were also built with SEH and using 4.9.2. See this thread: http://sourceforge.net/p/inkscape/mailman/message/34099214/
Oh, wow, I didn't know about these... I based my work on the latest 64-bit devlibs available on launchpad (https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk) and those date back to 2014 (with the readme stating posix/sjlj was in use, no idea if that's correct). I assume your updated builds never made it into the public repository.
> So my first question is if this would work with Inkscape in principle? > Not > that I (or anybody else) try to make something work that can not work > to > start with... > > In case win32 threads and SEH exception handling are OK for Inkscape I > suppose we'd also need to rebuild all other dependencies with the new > compiler? (Again, I have no clue about these things, but from what I > got > from a quick Internet search the old and new binaries are not > compatible?) > Which other dependencies need to be built?
Only those I listed... some of these are in your package from 2015-05-10, though, so a new built might not be necessary.
> Libraries that I spotted which are currently not included in the new > devlibs-package: > > gtkmm/gdkmm 2.4 (the package includes only 3.0) gtkmm 2.4 series is out dated. Do we still use it? With the move to GTK3, this should not be needed?
As far as I know GTK3 is still experimental, normal builds still use GTK2.
> aspell aspell is optional.
Yes, sorry for not being more specific. We have it i current builds but I assume it's not mandatory.
> ImageMagick Oops, my bad. I'll update the libs.
Thanks, no problem!
> poppler-data (for eastern-character support) ditto. > librevenge (optional if we want to include newer versions of the > various > import libraries [3]) > OK, I'll build this too. > Regards, > Eduard > > [1] http://www.partha.com/temp/Readme.txt > [2] > > > http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/view/head... > [3] http://www.documentliberation.org/projects/ > > > Am 17.01.2016 um 20:34 schrieb Partha Bagchi: > > Hi Eduard, > > I have uploaded the Windows 64bit devlibs here: > http://www.partha.com/temp/inkscape-devlibs.7z > > Can you (or someone) upload it to its final destination? The devlibs > include potrace 1.13. > > Please let me know if you have any questions. > > Thanks, > Partha > > > On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173...> > wrote: > > If you have some time this weekend, then adding potrace to the 64bit > devlibs > should probably be a high priority. > Right now it breaks 64bit builds since it seems the logic for > excluding > code > depending on potrace if it's not available does not work for > btool-based > builds (at least I was not able to make it work) > > Regards, > Eduard > > > Am 11.01.2016 um 11:42 schrieb Partha Bagchi: > > On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> > wrote: > ... > > To be honest, I'm a bit lost and can't find the best solution for us. > Could anyone (Partha, Johan, Krzysztof, or someone else) give an > advice? > Partha, how do you build the 64bit devlibs? > > There are some points we need to take into consideration (I probably > forgot some): > * The new devlibs must be easier to maintain compared to the current > ones. > * It should be possible to use the same steps to update win32 and > win64 > devlibs. > * If both devlibs could provide exactly the same packages versions, it > would greatly help bug tracking (and fixing)... > * Do we still need to link libstdc++ statically? (Opensuse > cross-compiled > packages need a shared library.) > > Regards, > -- > Nicolas > > Nicolas, > > I build my 64bit libs from scratch. I use MSYS as my shell if you will > and gcc 5.1.0 as my compiler. > > No, I don't think you have to statically link libstdc++. > > I'll try to provide a 64bit devlibs build this weekend if that's not > too > late. > > Thanks, > Partha > > > > > ------------------------------------------------------------------------------ > 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=267308311&iu=/4140 > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > >
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Turns out I did *not* hit the gdiplus bug you mentioned before.
Instead the error was caused by "gdk-pixbuf" no being able to locate the file "loaders.cache" The path to this file (by default found in "\lib\gdk-pixbuf-2.0\2.10.0\loaders.cache") is hardcoded in the library and by default an absolute path is used (with your compiled version it would be searched in "Z:/opts/opt64-win32-thread/lib" which obviously does not exist on my system).
The result is that "gdk-pixbuf" is not able to load the loader for XPM. In the following ugly things in the function "sp_load_handles()" in "select-tool.cpp" are happening: "gdk_pixbuf_new_from_xpm_data()" fails and returns a null pointer which is fed into "gdk_pixbuf_rotate_simple()" where the segmentation fault happens.
The good news: This can be fixed by setting the "--enable-relocations" flag when configuring "gdk-pixbuff". Not a nice solution since it needs rebuilding but I wasn't able to find an alternative (except setting the environment variable "GDK_PIXBUF_MODULE_FILE" to point to "loaders.cache", but thats obviously only a workaround).
Regards, Eduard
Am 25.01.2016 um 15:39 schrieb Partha Bagchi:
Hi Eduard,
It's that gdiplus bug again and I had forgotten about it!! :(
I've re-uploaded the devlibs. You should be OK now. Please check.
I think we should use -std=c++11 which is standard don't you think?
Thanks, Partha
PS: seems like now I have to use inkscape -g to open the gui. :(
On Sun, Jan 24, 2016 at 9:14 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Hi Partha,
thanks for the update! Inkscape compiles (and links!) fine now, also when using btool. When using "-std=gnu++0x" it's not even necessary to modify any files (or might this cause any issues?).
However I'm afraid while compiling works, running does not. Inkscape doesn't even open before it closes with an internal error... GDB tells me the error is in gdk_pixbuf_rotate_simple () inlibgdk_pixbuf-2.0-0.dll
A quick test shows your "forgotten build" might have the same issue? Running inkscape -g fails with (inkscape.exe:7532): GdkPixbuf-CRITICAL **: gdk_pixbuf_read_pixels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed for me. Did it work for work for you?
Good night, Eduard
Am 24.01.2016 um 23:07 schrieb Partha Bagchi:
Eduard,
I have updated the devlibs with the missing libraries. it now includes the Readme.txt in the base folder. Please download from the same place.
I didn't have issues with building inkscape-r14615. My command line was: ./configure --prefix=/opt/inkscape --build=x86_64-w64-mingw32 LIBS="-L/opt/lib -L/usr/python/Lib" CPPFLAGS="-I/opt/include -I/usr/python/include" CFLAGS="-w -O3 -ffast-math -ftree-vectorize" CXXFLAGS="-w -std=c++11 -O3 -ffast-math -ftree-vectorize"
The boost notes and warnings are annoying and so I suppressed them. :)
Since a whole bunch M_PI, M_PI_2, etc are undefined due to using -std=c++11, I modified the source by hand to fix those. Also, couple of files have WIN32 defined as opposed to _WIN32.
Please let me know if you have any questions.
Thanks, Partha
On Sun, Jan 24, 2016 at 10:18 AM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Seems my last mail didn't get through (probably because of pasted text), so here we go again...
I can't seem to get the win64 build working. Inkscape is compiling fine but I'm always getting linker errors:
https://inkscape.org/de/gallery/item/7421/
Here's the command used by btool:
https://inkscape.org/de/gallery/item/7426/
Any idea what's going wrong (and how to fix it)?
Regards, Eduard
Am 23.01.2016 um 21:22 schrieb Eduard Braun:
Am 23.01.2016 um 20:28 schrieb Partha Bagchi:
On Sat, Jan 23, 2016 at 1:06 PM, Eduard Braun <Eduard.Braun2@...173...> wrote: > I finally got around to have a look at the 64-bit devlibs Partha > provided. > I'm afraid however that I didn't succeed to build Inkscape with them > yet > (this is really not my area of expertise so any help is *very* > welcome!). > I'll take a look into building it for you if that helps?
Obviously you have more experience, so I guess you'd be able to figure out what is going wrong. Probably it's just some stupid error of mine which would be trivial to fix ;-). I don't want you to feel obliged, though, especially with respect to my next comment...
> What I noticed so far: > The new devlibs are based on a MinGW build with win32 threads and SEH > exception handling (possibly > x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z, > see [1]) whereas the old devlibs are based on MinGW with posix threads > and > SJLJ exception handling > (x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z, > see > [2]). > I think the previous 64-bit devlibs were also built with SEH and using 4.9.2. See this thread: http://sourceforge.net/p/inkscape/mailman/message/34099214/
Oh, wow, I didn't know about these... I based my work on the latest 64-bit devlibs available on launchpad (https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk) and those date back to 2014 (with the readme stating posix/sjlj was in use, no idea if that's correct). I assume your updated builds never made it into the public repository.
> So my first question is if this would work with Inkscape in principle? > Not > that I (or anybody else) try to make something work that can not work > to > start with... > > In case win32 threads and SEH exception handling are OK for Inkscape I > suppose we'd also need to rebuild all other dependencies with the new > compiler? (Again, I have no clue about these things, but from what I > got > from a quick Internet search the old and new binaries are not > compatible?) > Which other dependencies need to be built?
Only those I listed... some of these are in your package from 2015-05-10, though, so a new built might not be necessary.
> Libraries that I spotted which are currently not included in the new > devlibs-package: > > gtkmm/gdkmm 2.4 (the package includes only 3.0) gtkmm 2.4 series is out dated. Do we still use it? With the move to GTK3, this should not be needed?
As far as I know GTK3 is still experimental, normal builds still use GTK2.
> aspell aspell is optional.
Yes, sorry for not being more specific. We have it i current builds but I assume it's not mandatory.
> ImageMagick Oops, my bad. I'll update the libs.
Thanks, no problem!
> poppler-data (for eastern-character support) ditto. > librevenge (optional if we want to include newer versions of the > various > import libraries [3]) > OK, I'll build this too. > Regards, > Eduard > > [1] http://www.partha.com/temp/Readme.txt > [2] > > > http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/view/head... > [3] http://www.documentliberation.org/projects/ > > > Am 17.01.2016 um 20:34 schrieb Partha Bagchi: > > Hi Eduard, > > I have uploaded the Windows 64bit devlibs here: > http://www.partha.com/temp/inkscape-devlibs.7z > > Can you (or someone) upload it to its final destination? The devlibs > include potrace 1.13. > > Please let me know if you have any questions. > > Thanks, > Partha > > > On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173...> > wrote: > > If you have some time this weekend, then adding potrace to the 64bit > devlibs > should probably be a high priority. > Right now it breaks 64bit builds since it seems the logic for > excluding > code > depending on potrace if it's not available does not work for > btool-based > builds (at least I was not able to make it work) > > Regards, > Eduard > > > Am 11.01.2016 um 11:42 schrieb Partha Bagchi: > > On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> > wrote: > ... > > To be honest, I'm a bit lost and can't find the best solution for us. > Could anyone (Partha, Johan, Krzysztof, or someone else) give an > advice? > Partha, how do you build the 64bit devlibs? > > There are some points we need to take into consideration (I probably > forgot some): > * The new devlibs must be easier to maintain compared to the current > ones. > * It should be possible to use the same steps to update win32 and > win64 > devlibs. > * If both devlibs could provide exactly the same packages versions, it > would greatly help bug tracking (and fixing)... > * Do we still need to link libstdc++ statically? (Opensuse > cross-compiled > packages need a shared library.) > > Regards, > -- > Nicolas > > Nicolas, > > I build my 64bit libs from scratch. I use MSYS as my shell if you will > and gcc 5.1.0 as my compiler. > > No, I don't think you have to statically link libstdc++. > > I'll try to provide a 64bit devlibs build this weekend if that's not > too > late. > > Thanks, > Partha > > > > > ------------------------------------------------------------------------------ > 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=267308311&iu=/4140 > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > >
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Eduard,
The relocation is not necessary. You can set the environment variables to take care of it. I hit segfault after taking care of the loader.cache file.
In any case, with the new rebuilds you will not have a segfault.
Thanks, Partha
On Mon, Jan 25, 2016 at 7:48 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Turns out I did *not* hit the gdiplus bug you mentioned before.
Instead the error was caused by "gdk-pixbuf" no being able to locate the file "loaders.cache" The path to this file (by default found in "\lib\gdk-pixbuf-2.0\2.10.0\loaders.cache") is hardcoded in the library and by default an absolute path is used (with your compiled version it would be searched in "Z:/opts/opt64-win32-thread/lib" which obviously does not exist on my system).
The result is that "gdk-pixbuf" is not able to load the loader for XPM. In the following ugly things in the function "sp_load_handles()" in "select-tool.cpp" are happening: "gdk_pixbuf_new_from_xpm_data()" fails and returns a null pointer which is fed into "gdk_pixbuf_rotate_simple()" where the segmentation fault happens.
The good news: This can be fixed by setting the "--enable-relocations" flag when configuring "gdk-pixbuff". Not a nice solution since it needs rebuilding but I wasn't able to find an alternative (except setting the environment variable "GDK_PIXBUF_MODULE_FILE" to point to "loaders.cache", but thats obviously only a workaround).
Regards, Eduard
Am 25.01.2016 um 15:39 schrieb Partha Bagchi:
Hi Eduard,
It's that gdiplus bug again and I had forgotten about it!! :(
I've re-uploaded the devlibs. You should be OK now. Please check.
I think we should use -std=c++11 which is standard don't you think?
Thanks, Partha
PS: seems like now I have to use inkscape -g to open the gui. :(
On Sun, Jan 24, 2016 at 9:14 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Hi Partha,
thanks for the update! Inkscape compiles (and links!) fine now, also when using btool. When using "-std=gnu++0x" it's not even necessary to modify any files (or might this cause any issues?).
However I'm afraid while compiling works, running does not. Inkscape doesn't even open before it closes with an internal error... GDB tells me the error is in gdk_pixbuf_rotate_simple () inlibgdk_pixbuf-2.0-0.dll
A quick test shows your "forgotten build" might have the same issue? Running inkscape -g fails with (inkscape.exe:7532): GdkPixbuf-CRITICAL **: gdk_pixbuf_read_pixels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed for me. Did it work for work for you?
Good night, Eduard
Am 24.01.2016 um 23:07 schrieb Partha Bagchi:
Eduard,
I have updated the devlibs with the missing libraries. it now includes the Readme.txt in the base folder. Please download from the same place.
I didn't have issues with building inkscape-r14615. My command line was: ./configure --prefix=/opt/inkscape --build=x86_64-w64-mingw32 LIBS="-L/opt/lib -L/usr/python/Lib" CPPFLAGS="-I/opt/include -I/usr/python/include" CFLAGS="-w -O3 -ffast-math -ftree-vectorize" CXXFLAGS="-w -std=c++11 -O3 -ffast-math -ftree-vectorize"
The boost notes and warnings are annoying and so I suppressed them. :)
Since a whole bunch M_PI, M_PI_2, etc are undefined due to using -std=c++11, I modified the source by hand to fix those. Also, couple of files have WIN32 defined as opposed to _WIN32.
Please let me know if you have any questions.
Thanks, Partha
On Sun, Jan 24, 2016 at 10:18 AM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Seems my last mail didn't get through (probably because of pasted text), so here we go again...
I can't seem to get the win64 build working. Inkscape is compiling fine but I'm always getting linker errors:
https://inkscape.org/de/gallery/item/7421/
Here's the command used by btool:
https://inkscape.org/de/gallery/item/7426/
Any idea what's going wrong (and how to fix it)?
Regards, Eduard
Am 23.01.2016 um 21:22 schrieb Eduard Braun:
Am 23.01.2016 um 20:28 schrieb Partha Bagchi:
> On Sat, Jan 23, 2016 at 1:06 PM, Eduard Braun <Eduard.Braun2@...173...> > wrote: > >> I finally got around to have a look at the 64-bit devlibs Partha >> provided. >> I'm afraid however that I didn't succeed to build Inkscape with them >> yet >> (this is really not my area of expertise so any help is *very* >> welcome!). >> >> I'll take a look into building it for you if that helps? > Obviously you have more experience, so I guess you'd be able to figure out what is going wrong. Probably it's just some stupid error of mine which would be trivial to fix ;-). I don't want you to feel obliged, though, especially with respect to my next comment...
> What I noticed so far: >> The new devlibs are based on a MinGW build with win32 threads and >> SEH >> exception handling (possibly >> x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z, >> see [1]) whereas the old devlibs are based on MinGW with posix >> threads >> and >> SJLJ exception handling >> (x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z, >> see >> [2]). >> >> I think the previous 64-bit devlibs were also built with SEH and > using > 4.9.2. See this thread: > http://sourceforge.net/p/inkscape/mailman/message/34099214/ > Oh, wow, I didn't know about these... I based my work on the latest 64-bit devlibs available on launchpad (https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk) and those date back to 2014 (with the readme stating posix/sjlj was in use, no idea if that's correct). I assume your updated builds never made it into the public repository.
> So my first question is if this would work with Inkscape in >> principle? >> Not >> that I (or anybody else) try to make something work that can not >> work >> to >> start with... >> >> In case win32 threads and SEH exception handling are OK for >> Inkscape I >> suppose we'd also need to rebuild all other dependencies with the >> new >> compiler? (Again, I have no clue about these things, but from what I >> got >> from a quick Internet search the old and new binaries are not >> compatible?) >> >> Which other dependencies need to be built? > Only those I listed... some of these are in your package from 2015-05-10, though, so a new built might not be necessary.
> Libraries that I spotted which are currently not included in the new >> devlibs-package: >> >> gtkmm/gdkmm 2.4 (the package includes only 3.0) >> > gtkmm 2.4 series is out dated. Do we still use it? With the move to > GTK3, this should not be needed? > As far as I know GTK3 is still experimental, normal builds still use GTK2.
> aspell >> > aspell is optional. > Yes, sorry for not being more specific. We have it i current builds but I assume it's not mandatory.
> ImageMagick >> > Oops, my bad. I'll update the libs. > Thanks, no problem!
> poppler-data (for eastern-character support) >> > ditto. > >> librevenge (optional if we want to include newer versions of the >> various >> import libraries [3]) >> >> OK, I'll build this too. > >> Regards, >> Eduard >> >> [1] http://www.partha.com/temp/Readme.txt >> [2] >> >> >> >> http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/view/head... >> [3] http://www.documentliberation.org/projects/ >> >> >> Am 17.01.2016 um 20:34 schrieb Partha Bagchi: >> >> Hi Eduard, >> >> I have uploaded the Windows 64bit devlibs here: >> http://www.partha.com/temp/inkscape-devlibs.7z >> >> Can you (or someone) upload it to its final destination? The devlibs >> include potrace 1.13. >> >> Please let me know if you have any questions. >> >> Thanks, >> Partha >> >> >> On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173... >> > >> wrote: >> >> If you have some time this weekend, then adding potrace to the 64bit >> devlibs >> should probably be a high priority. >> Right now it breaks 64bit builds since it seems the logic for >> excluding >> code >> depending on potrace if it's not available does not work for >> btool-based >> builds (at least I was not able to make it work) >> >> Regards, >> Eduard >> >> >> Am 11.01.2016 um 11:42 schrieb Partha Bagchi: >> >> On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> >> wrote: >> ... >> >> To be honest, I'm a bit lost and can't find the best solution for >> us. >> Could anyone (Partha, Johan, Krzysztof, or someone else) give an >> advice? >> Partha, how do you build the 64bit devlibs? >> >> There are some points we need to take into consideration (I probably >> forgot some): >> * The new devlibs must be easier to maintain compared to the current >> ones. >> * It should be possible to use the same steps to update win32 and >> win64 >> devlibs. >> * If both devlibs could provide exactly the same packages versions, >> it >> would greatly help bug tracking (and fixing)... >> * Do we still need to link libstdc++ statically? (Opensuse >> cross-compiled >> packages need a shared library.) >> >> Regards, >> -- >> Nicolas >> >> Nicolas, >> >> I build my 64bit libs from scratch. I use MSYS as my shell if you >> will >> and gcc 5.1.0 as my compiler. >> >> No, I don't think you have to statically link libstdc++. >> >> I'll try to provide a 64bit devlibs build this weekend if that's not >> too >> late. >> >> Thanks, >> Partha >> >> >> >> >> >> ------------------------------------------------------------------------------ >> 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=267308311&iu=/4140 >> _______________________________________________ >> Inkscape-devel mailing list >> Inkscape-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/inkscape-devel >> >> >>
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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Am 26.01.2016 um 02:47 schrieb Partha Bagchi:
Eduard,
The relocation is not necessary. You can set the environment variables to take care of it. I hit segfault after taking care of the loader.cache file.
The environment variable I mentioned or is there a possibility to "fix" it when building? Just asking because we obviously want the devbuilds to be independent of the platformand the final Inkscape build should work without setting environment variables.
In any case, with the new rebuilds you will not have a segfault.
Thanks, Partha
On Mon, Jan 25, 2016 at 7:48 PM, Eduard Braun <Eduard.Braun2@...173... mailto:Eduard.Braun2@...173...> wrote:
Turns out I did *not* hit the gdiplus bug you mentioned before. Instead the error was caused by "gdk-pixbuf" no being able to locate the file "loaders.cache" The path to this file (by default found in "\lib\gdk-pixbuf-2.0\2.10.0\loaders.cache") is hardcoded in the library and by default an absolute path is used (with your compiled version it would be searched in "Z:/opts/opt64-win32-thread/lib" which obviously does not exist on my system). The result is that "gdk-pixbuf" is not able to load the loader for XPM. In the following ugly things in the function "sp_load_handles()" in "select-tool.cpp" are happening: "gdk_pixbuf_new_from_xpm_data()" fails and returns a null pointer which is fed into "gdk_pixbuf_rotate_simple()" where the segmentation fault happens. The good news: This can be fixed by setting the "--enable-relocations" flag when configuring "gdk-pixbuff". Not a nice solution since it needs rebuilding but I wasn't able to find an alternative (except setting the environment variable "GDK_PIXBUF_MODULE_FILE" to point to "loaders.cache", but thats obviously only a workaround). Regards, Eduard Am 25.01.2016 um 15:39 schrieb Partha Bagchi: Hi Eduard, It's that gdiplus bug again and I had forgotten about it!! :( I've re-uploaded the devlibs. You should be OK now. Please check. I think we should use -std=c++11 which is standard don't you think? Thanks, Partha PS: seems like now I have to use inkscape -g to open the gui. :( On Sun, Jan 24, 2016 at 9:14 PM, Eduard Braun <Eduard.Braun2@...173... <mailto:Eduard.Braun2@...173...>> wrote: Hi Partha, thanks for the update! Inkscape compiles (and links!) fine now, also when using btool. When using "-std=gnu++0x" it's not even necessary to modify any files (or might this cause any issues?). However I'm afraid while compiling works, running does not. Inkscape doesn't even open before it closes with an internal error... GDB tells me the error is in gdk_pixbuf_rotate_simple () inlibgdk_pixbuf-2.0-0.dll A quick test shows your "forgotten build" might have the same issue? Running inkscape -g fails with (inkscape.exe:7532): GdkPixbuf-CRITICAL **: gdk_pixbuf_read_pixels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed for me. Did it work for work for you? Good night, Eduard Am 24.01.2016 um 23:07 schrieb Partha Bagchi: Eduard, I have updated the devlibs with the missing libraries. it now includes the Readme.txt in the base folder. Please download from the same place. I didn't have issues with building inkscape-r14615. My command line was: ./configure --prefix=/opt/inkscape --build=x86_64-w64-mingw32 LIBS="-L/opt/lib -L/usr/python/Lib" CPPFLAGS="-I/opt/include -I/usr/python/include" CFLAGS="-w -O3 -ffast-math -ftree-vectorize" CXXFLAGS="-w -std=c++11 -O3 -ffast-math -ftree-vectorize" The boost notes and warnings are annoying and so I suppressed them. :) Since a whole bunch M_PI, M_PI_2, etc are undefined due to using -std=c++11, I modified the source by hand to fix those. Also, couple of files have WIN32 defined as opposed to _WIN32. Please let me know if you have any questions. Thanks, Partha On Sun, Jan 24, 2016 at 10:18 AM, Eduard Braun <Eduard.Braun2@...173... <mailto:Eduard.Braun2@...173...>> wrote: Seems my last mail didn't get through (probably because of pasted text), so here we go again... I can't seem to get the win64 build working. Inkscape is compiling fine but I'm always getting linker errors: https://inkscape.org/de/gallery/item/7421/ Here's the command used by btool: https://inkscape.org/de/gallery/item/7426/ Any idea what's going wrong (and how to fix it)? Regards, Eduard Am 23.01.2016 um 21:22 schrieb Eduard Braun: Am 23.01.2016 um 20:28 schrieb Partha Bagchi: On Sat, Jan 23, 2016 at 1:06 PM, Eduard Braun <Eduard.Braun2@...173... <mailto:Eduard.Braun2@...173...>> wrote: I finally got around to have a look at the 64-bit devlibs Partha provided. I'm afraid however that I didn't succeed to build Inkscape with them yet (this is really not my area of expertise so any help is *very* welcome!). I'll take a look into building it for you if that helps? Obviously you have more experience, so I guess you'd be able to figure out what is going wrong. Probably it's just some stupid error of mine which would be trivial to fix ;-). I don't want you to feel obliged, though, especially with respect to my next comment... What I noticed so far: The new devlibs are based on a MinGW build with win32 threads and SEH exception handling (possibly x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z, see [1]) whereas the old devlibs are based on MinGW with posix threads and SJLJ exception handling (x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z, see [2]). I think the previous 64-bit devlibs were also built with SEH and using 4.9.2. See this thread: http://sourceforge.net/p/inkscape/mailman/message/34099214/ Oh, wow, I didn't know about these... I based my work on the latest 64-bit devlibs available on launchpad (https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk <https://code.launchpad.net/%7Einkscape.dev/inkscape-devlibs64/trunk>) and those date back to 2014 (with the readme stating posix/sjlj was in use, no idea if that's correct). I assume your updated builds never made it into the public repository. So my first question is if this would work with Inkscape in principle? Not that I (or anybody else) try to make something work that can not work to start with... In case win32 threads and SEH exception handling are OK for Inkscape I suppose we'd also need to rebuild all other dependencies with the new compiler? (Again, I have no clue about these things, but from what I got from a quick Internet search the old and new binaries are not compatible?) Which other dependencies need to be built? Only those I listed... some of these are in your package from 2015-05-10, though, so a new built might not be necessary. Libraries that I spotted which are currently not included in the new devlibs-package: gtkmm/gdkmm 2.4 (the package includes only 3.0) gtkmm 2.4 series is out dated. Do we still use it? With the move to GTK3, this should not be needed? As far as I know GTK3 is still experimental, normal builds still use GTK2. aspell aspell is optional. Yes, sorry for not being more specific. We have it i current builds but I assume it's not mandatory. ImageMagick Oops, my bad. I'll update the libs. Thanks, no problem! poppler-data (for eastern-character support) ditto. librevenge (optional if we want to include newer versions of the various import libraries [3]) OK, I'll build this too. Regards, Eduard [1] http://www.partha.com/temp/Readme.txt [2] http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/view/head:/readme.txt <http://bazaar.launchpad.net/%7Einkscape.dev/inkscape-devlibs64/trunk/view/head:/readme.txt> [3] http://www.documentliberation.org/projects/ Am 17.01.2016 um 20:34 schrieb Partha Bagchi: Hi Eduard, I have uploaded the Windows 64bit devlibs here: http://www.partha.com/temp/inkscape-devlibs.7z Can you (or someone) upload it to its final destination? The devlibs include potrace 1.13. Please let me know if you have any questions. Thanks, Partha On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun <Eduard.Braun2@...173... <mailto:Eduard.Braun2@...173...>> wrote: If you have some time this weekend, then adding potrace to the 64bit devlibs should probably be a high priority. Right now it breaks 64bit builds since it seems the logic for excluding code depending on potrace if it's not available does not work for btool-based builds (at least I was not able to make it work) Regards, Eduard Am 11.01.2016 um 11:42 schrieb Partha Bagchi: On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48... <mailto:nicoduf@...48...>> wrote: ... To be honest, I'm a bit lost and can't find the best solution for us. Could anyone (Partha, Johan, Krzysztof, or someone else) give an advice? Partha, how do you build the 64bit devlibs? There are some points we need to take into consideration (I probably forgot some): * The new devlibs must be easier to maintain compared to the current ones. * It should be possible to use the same steps to update win32 and win64 devlibs. * If both devlibs could provide exactly the same packages versions, it would greatly help bug tracking (and fixing)... * Do we still need to link libstdc++ statically? (Opensuse cross-compiled packages need a shared library.) Regards, -- Nicolas Nicolas, I build my 64bit libs from scratch. I use MSYS as my shell if you will and gcc 5.1.0 as my compiler. No, I don't think you have to statically link libstdc++. I'll try to provide a 64bit devlibs build this weekend if that's not too late. Thanks, Partha ------------------------------------------------------------------------------ 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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net <mailto:Inkscape-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/inkscape-devel ------------------------------------------------------------------------------ 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=267308311&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net <mailto:Inkscape-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
The problems is you never know where the user is going to install your software. So, one way is to use environment variables or create a launcher. I create a launcher and modify loader.cache on the fly before loading the software.
On Mon, Jan 25, 2016 at 9:03 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Am 26.01.2016 um 02:47 schrieb Partha Bagchi:
Eduard,
The relocation is not necessary. You can set the environment variables to take care of it. I hit segfault after taking care of the loader.cache file.
The environment variable I mentioned or is there a possibility to "fix" it when building? Just asking because we obviously want the devbuilds to be independent of the platformand the final Inkscape build should work without setting environment variables.
In any case, with the new rebuilds you will not have a segfault.
Thanks, Partha
On Mon, Jan 25, 2016 at 7:48 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Turns out I did *not* hit the gdiplus bug you mentioned before.
Instead the error was caused by "gdk-pixbuf" no being able to locate the file "loaders.cache" The path to this file (by default found in "\lib\gdk-pixbuf-2.0\2.10.0\loaders.cache") is hardcoded in the library and by default an absolute path is used (with your compiled version it would be searched in "Z:/opts/opt64-win32-thread/lib" which obviously does not exist on my system).
The result is that "gdk-pixbuf" is not able to load the loader for XPM. In the following ugly things in the function "sp_load_handles()" in "select-tool.cpp" are happening: "gdk_pixbuf_new_from_xpm_data()" fails and returns a null pointer which is fed into "gdk_pixbuf_rotate_simple()" where the segmentation fault happens.
The good news: This can be fixed by setting the "--enable-relocations" flag when configuring "gdk-pixbuff". Not a nice solution since it needs rebuilding but I wasn't able to find an alternative (except setting the environment variable "GDK_PIXBUF_MODULE_FILE" to point to "loaders.cache", but thats obviously only a workaround).
Regards, Eduard
Am 25.01.2016 um 15:39 schrieb Partha Bagchi:
Hi Eduard,
It's that gdiplus bug again and I had forgotten about it!! :(
I've re-uploaded the devlibs. You should be OK now. Please check.
I think we should use -std=c++11 which is standard don't you think?
Thanks, Partha
PS: seems like now I have to use inkscape -g to open the gui. :(
On Sun, Jan 24, 2016 at 9:14 PM, Eduard Braun < <Eduard.Braun2@...173...> Eduard.Braun2@...173...> wrote:
Hi Partha,
thanks for the update! Inkscape compiles (and links!) fine now, also when using btool. When using "-std=gnu++0x" it's not even necessary to modify any files (or might this cause any issues?).
However I'm afraid while compiling works, running does not. Inkscape doesn't even open before it closes with an internal error... GDB tells me the error is in gdk_pixbuf_rotate_simple () inlibgdk_pixbuf-2.0-0.dll
A quick test shows your "forgotten build" might have the same issue? Running inkscape -g fails with (inkscape.exe:7532): GdkPixbuf-CRITICAL **: gdk_pixbuf_read_pixels: assertion 'GDK_IS_PIXBUF (pixbuf)' failed for me. Did it work for work for you?
Good night, Eduard
Am 24.01.2016 um 23:07 schrieb Partha Bagchi:
Eduard,
I have updated the devlibs with the missing libraries. it now includes the Readme.txt in the base folder. Please download from the same place.
I didn't have issues with building inkscape-r14615. My command line was: ./configure --prefix=/opt/inkscape --build=x86_64-w64-mingw32 LIBS="-L/opt/lib -L/usr/python/Lib" CPPFLAGS="-I/opt/include -I/usr/python/include" CFLAGS="-w -O3 -ffast-math -ftree-vectorize" CXXFLAGS="-w -std=c++11 -O3 -ffast-math -ftree-vectorize"
The boost notes and warnings are annoying and so I suppressed them. :)
Since a whole bunch M_PI, M_PI_2, etc are undefined due to using -std=c++11, I modified the source by hand to fix those. Also, couple of files have WIN32 defined as opposed to _WIN32.
Please let me know if you have any questions.
Thanks, Partha
On Sun, Jan 24, 2016 at 10:18 AM, Eduard Braun <Eduard.Braun2@...173...> wrote:
Seems my last mail didn't get through (probably because of pasted text), so here we go again...
I can't seem to get the win64 build working. Inkscape is compiling fine but I'm always getting linker errors:
https://inkscape.org/de/gallery/item/7421/
Here's the command used by btool:
https://inkscape.org/de/gallery/item/7426/
Any idea what's going wrong (and how to fix it)?
Regards, Eduard
Am 23.01.2016 um 21:22 schrieb Eduard Braun:
> Am 23.01.2016 um 20:28 schrieb Partha Bagchi: > >> On Sat, Jan 23, 2016 at 1:06 PM, Eduard Braun <Eduard.Braun2@...173... >> > >> wrote: >> >>> I finally got around to have a look at the 64-bit devlibs Partha >>> provided. >>> I'm afraid however that I didn't succeed to build Inkscape with >>> them >>> yet >>> (this is really not my area of expertise so any help is *very* >>> welcome!). >>> >>> I'll take a look into building it for you if that helps? >> > Obviously you have more experience, so I guess you'd be able to > figure > out what is going wrong. Probably it's just some stupid error of mine > which would be trivial to fix ;-). I don't want you to feel obliged, > though, especially with respect to my next comment... > >> What I noticed so far: >>> The new devlibs are based on a MinGW build with win32 threads and >>> SEH >>> exception handling (possibly >>> x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z, >>> see [1]) whereas the old devlibs are based on MinGW with posix >>> threads >>> and >>> SJLJ exception handling >>> (x86_64-4.9.0-release-posix-sjlj-rt_v3-rev1.7z, >>> see >>> [2]). >>> >>> I think the previous 64-bit devlibs were also built with SEH and >> using >> 4.9.2. See this thread: >> http://sourceforge.net/p/inkscape/mailman/message/34099214/ >> > Oh, wow, I didn't know about these... I based my work on the latest > 64-bit devlibs available on launchpad > (https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk) > and > those date back to 2014 (with the readme stating posix/sjlj was in > use, > no idea if that's correct). I assume your updated builds never made > it > into the public repository. > >> So my first question is if this would work with Inkscape in >>> principle? >>> Not >>> that I (or anybody else) try to make something work that can not >>> work >>> to >>> start with... >>> >>> In case win32 threads and SEH exception handling are OK for >>> Inkscape I >>> suppose we'd also need to rebuild all other dependencies with the >>> new >>> compiler? (Again, I have no clue about these things, but from what >>> I >>> got >>> from a quick Internet search the old and new binaries are not >>> compatible?) >>> >>> Which other dependencies need to be built? >> > Only those I listed... some of these are in your package from > 2015-05-10, though, so a new built might not be necessary. > >> Libraries that I spotted which are currently not included in the new >>> devlibs-package: >>> >>> gtkmm/gdkmm 2.4 (the package includes only 3.0) >>> >> gtkmm 2.4 series is out dated. Do we still use it? With the move to >> GTK3, this should not be needed? >> > As far as I know GTK3 is still experimental, normal builds still use > GTK2. > >> aspell >>> >> aspell is optional. >> > Yes, sorry for not being more specific. > We have it i current builds but I assume it's not mandatory. > >> ImageMagick >>> >> Oops, my bad. I'll update the libs. >> > Thanks, no problem! > >> poppler-data (for eastern-character support) >>> >> ditto. >> >>> librevenge (optional if we want to include newer versions of the >>> various >>> import libraries [3]) >>> >>> OK, I'll build this too. >> >>> Regards, >>> Eduard >>> >>> [1] http://www.partha.com/temp/Readme.txt >>> [2] >>> >>> >>> >>> http://bazaar.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk/view/head... >>> [3] http://www.documentliberation.org/projects/ >>> >>> >>> Am 17.01.2016 um 20:34 schrieb Partha Bagchi: >>> >>> Hi Eduard, >>> >>> I have uploaded the Windows 64bit devlibs here: >>> http://www.partha.com/temp/inkscape-devlibs.7z >>> >>> Can you (or someone) upload it to its final destination? The >>> devlibs >>> include potrace 1.13. >>> >>> Please let me know if you have any questions. >>> >>> Thanks, >>> Partha >>> >>> >>> On Fri, Jan 15, 2016 at 9:07 PM, Eduard Braun < >>> Eduard.Braun2@...173...> >>> wrote: >>> >>> If you have some time this weekend, then adding potrace to the >>> 64bit >>> devlibs >>> should probably be a high priority. >>> Right now it breaks 64bit builds since it seems the logic for >>> excluding >>> code >>> depending on potrace if it's not available does not work for >>> btool-based >>> builds (at least I was not able to make it work) >>> >>> Regards, >>> Eduard >>> >>> >>> Am 11.01.2016 um 11:42 schrieb Partha Bagchi: >>> >>> On Mon, Jan 11, 2016 at 5:15 AM, Nicolas Dufour <nicoduf@...48...> >>> wrote: >>> ... >>> >>> To be honest, I'm a bit lost and can't find the best solution for >>> us. >>> Could anyone (Partha, Johan, Krzysztof, or someone else) give an >>> advice? >>> Partha, how do you build the 64bit devlibs? >>> >>> There are some points we need to take into consideration (I >>> probably >>> forgot some): >>> * The new devlibs must be easier to maintain compared to the >>> current >>> ones. >>> * It should be possible to use the same steps to update win32 and >>> win64 >>> devlibs. >>> * If both devlibs could provide exactly the same packages >>> versions, it >>> would greatly help bug tracking (and fixing)... >>> * Do we still need to link libstdc++ statically? (Opensuse >>> cross-compiled >>> packages need a shared library.) >>> >>> Regards, >>> -- >>> Nicolas >>> >>> Nicolas, >>> >>> I build my 64bit libs from scratch. I use MSYS as my shell if you >>> will >>> and gcc 5.1.0 as my compiler. >>> >>> No, I don't think you have to statically link libstdc++. >>> >>> I'll try to provide a 64bit devlibs build this weekend if that's >>> not >>> too >>> late. >>> >>> Thanks, >>> Partha >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> 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=267308311&iu=/4140 >>> _______________________________________________ >>> Inkscape-devel mailing list >>> Inkscape-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel >>> >>> >>> > > ------------------------------------------------------------------------------ > 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=267308311&iu=/4140 > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel >
On Fri, Jan 01, 2016 at 07:36:42AM +0000, Nicolas Dufour wrote:
Hi all,
The win32 devlibs have just been updated (rev. 54) to fix the following reports:
- Bug #1530286 "Inkscape fails to build on Window with GC errors",
- Bug #1156664 "Compile against external libpotrace".
The build.xml files also changed in rev. 14559, so don't forget to update the devlibs and run "btool clean" before compiling!
Regards,
Nicolas
Hi Nicolas,
Have you looked into using cmake for building the windows packages?
Bryce
participants (5)
-
Alex Valavanis
-
Bryce Harrington
-
Eduard Braun
-
Nicolas Dufour
-
Partha Bagchi