Fwd: New batch files in trunk
Hello everyone,
I created these files to simplify building Inkscape on Windows. Originally they were not located in the root of the trunk, but in a separate 'build' folder because it is good practise for CMake to not build in the root/source directory. Somehow they moved when the merge was created. Anyway, there's a reason for these files to be there. In particular:
configure.bat: Deletes the CMake cache and regenerates all the makefiles to be sure that any changes in CMake files are actually applied. I spend hours on trying to solve an issue just to find out that relevant Makefiles were not regenerated by CMake for any reason. Moreover, the trunk version of the file is missing an option to CMake I had to add in order for it to build at all. I do not know why it was removed:
REM Configure using the MinGW compiler chain. cmake -D"CMAKE_SYSTEM_PREFIX_PATH:PATH=C:\MinGW64\mingw64\x86_64-w64-mingw32" -G "MinGW Makefiles" ..
Surely is should use the MINGW_PATH environment variable here, but I had serious issues without this option set. The file could also be used to setup the system environment variables, such as MINGW_PATH if they are not set to a valid value and store them somewhere making the setup somehow more user friendly.
touch.bat: Since there is no such thing as touch on Windows, I created the script to reset the modification dates of all .obj files in case of changes to the CMake configuration which would trigger a full rebuild. This is simply a time and enery saver.
I did not have the chance to check out trunk and try to build it on my machine. But I will do it this week. I saw that the wiki got updated with new instructions for compiling on Windows 64-bit. Wonderful, thanks Adib.
~Sebastian
*Semiodesk GmbH | *Werner-von-Siemens-Str. 6 Geb. 15k, 86159 Augsburg, Germany | Phone: +49 821 8854401 | Fax: +49 821 8854410 | www.semiodesk.com
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Semiodesk GmbH is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.
2016-04-20 8:57 GMT+02:00 Olof Bjarnason <olof.bjarnason@...400...>:
On 20 April 2016 at 08:27, LucaDC <dicappello@...2144...> wrote:
In rev. 14855 ("merge Moritz's branch") two batch files have been added in the root of trunk: configure.bat and touch.bat. Both of them contain a particular system's specific configurations like a fixed path and a reference to some script/program (forfiles) so little chances they are useful for others.
Being them useless and to avoid confusion I think they should be removed from version control.
I believe they were used to get the Windows build working with cmake, so if they improved/corrected they probably would have use for the Windows build maintainer. Is there a subfolder for Windows building to move them to?
Sebastian, Moritz friend did mention some weird for,, syntax to stop cmake from rebuilding "everything" each time he made a change to get Inkscape building on his Windows machine.
Maybe Sebastian and Moritz knows more about this?
-- View this message in context: http://inkscape.13.x6.nabble.com/New-batch-files-in-trunk-tp4976419.html Sent from the Inkscape - Dev mailing list archive at Nabble.com.
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
I see. Well, if they are for public utility it's correct that they are under revision control (hence copied to everybody's folders). But they are so specialized that I think that they are of little public utility: they need mingw64, they need it in a special folder and they need the "forfiles" command which is not present under all Windows OSs. They seem to be too tied to a specific configuration to always work.
I don't know cmake: does the reference to "x86_64-w64-mingw32" mean that the compilation is for 32 bit binaries built in a 64 bit environment?
Sebastian Faubel wrote
Surely is should use the MINGW_PATH environment variable here, but I had serious issues without this option set.
Just a try: doesn't 'cmake -D"CMAKE_SYSTEM_PREFIX_PATH:PATH=%MINGW_PATH%\x86_64-w64-mingw32" -G "MinGW Makefiles" ..' work? Or maybe (better) you should change the MINGW_PATH variable to 'C:\MinGW64\mingw64\x86_64-w64-mingw32' in your mingwenv.bat file (without committing it) and remove that option: actually I can't see any reason to tie a supposedly general script to such a particular need.
-- View this message in context: http://inkscape.13.x6.nabble.com/New-batch-files-in-trunk-tp4976419p4976429.... Sent from the Inkscape - Dev mailing list archive at Nabble.com.
If you are using CMAKE and have Msys and Mingw etc., then simply do the following:
cmake -G "MSYS Makefiles" -DCMAKE etc. in your build folder
On Wed, Apr 20, 2016 at 8:28 AM, LucaDC <dicappello@...2144...> wrote:
I see. Well, if they are for public utility it's correct that they are under revision control (hence copied to everybody's folders). But they are so specialized that I think that they are of little public utility: they need mingw64, they need it in a special folder and they need the "forfiles" command which is not present under all Windows OSs. They seem to be too tied to a specific configuration to always work.
I don't know cmake: does the reference to "x86_64-w64-mingw32" mean that the compilation is for 32 bit binaries built in a 64 bit environment?
Sebastian Faubel wrote
Surely is should use the MINGW_PATH environment variable here, but I had serious issues without this option set.
Just a try: doesn't 'cmake -D"CMAKE_SYSTEM_PREFIX_PATH:PATH=%MINGW_PATH%\x86_64-w64-mingw32" -G "MinGW Makefiles" ..' work? Or maybe (better) you should change the MINGW_PATH variable to 'C:\MinGW64\mingw64\x86_64-w64-mingw32' in your mingwenv.bat file (without committing it) and remove that option: actually I can't see any reason to tie a supposedly general script to such a particular need.
-- View this message in context: http://inkscape.13.x6.nabble.com/New-batch-files-in-trunk-tp4976419p4976429.... Sent from the Inkscape - Dev mailing list archive at Nabble.com.
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 20 April 2016 at 15:00, Partha Bagchi <partha1b@...400...> wrote:
If you are using CMAKE and have Msys and Mingw etc., then simply do the following:
cmake -G "MSYS Makefiles" -DCMAKE etc. in your build folder
Is this documented in the relevant wiki page? I guess building on windows pages ...
On Wed, Apr 20, 2016 at 8:28 AM, LucaDC <dicappello@...2144...> wrote:
I see. Well, if they are for public utility it's correct that they are under revision control (hence copied to everybody's folders). But they are so specialized that I think that they are of little public utility: they need mingw64, they need it in a special folder and they need the "forfiles" command which is not present under all Windows OSs. They seem to be too tied to a specific configuration to always work.
I don't know cmake: does the reference to "x86_64-w64-mingw32" mean that the compilation is for 32 bit binaries built in a 64 bit environment?
Sebastian Faubel wrote
Surely is should use the MINGW_PATH environment variable here, but I had serious issues without this option set.
Just a try: doesn't 'cmake -D"CMAKE_SYSTEM_PREFIX_PATH:PATH=%MINGW_PATH%\x86_64-w64-mingw32" -G "MinGW Makefiles" ..' work? Or maybe (better) you should change the MINGW_PATH variable to 'C:\MinGW64\mingw64\x86_64-w64-mingw32' in your mingwenv.bat file (without committing it) and remove that option: actually I can't see any reason to tie a supposedly general script to such a particular need.
-- View this message in context: http://inkscape.13.x6.nabble.com/New-batch-files-in-trunk-tp4976419p4976429.... Sent from the Inkscape - Dev mailing list archive at Nabble.com.
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hello everybody,
i already said that the files need to be changed to using the environment variables for such as MINGW_PATH to work properly on other installations. This is a bug and i will fix it as soon as i find the time. However that is a simple thing to do and then they are useful for anyone trying to build Inkscape on Windows without MSYS (as it is described in the corresponding wikipages). There's quite some pitfalls when trying to do that and for these reasons there is the configure.bat. I think that we can get rid of the touch.bat file and integrate this functionality in configure.bat as a program option.
The forfiles command has been around since Windows Vista and I honestly do not know if Inkscape will be supporting Windows XP in future. If so, then this part should be rewritten to be compatible.
The path 'C:\MinGW64\mingw64\x86_64-w64-mingw32' refers to the MinGW version for 64-bit OSes that is referenced for download in the wikipages. On 64-bit Windows, the make command is still called 'mingw32-make' for whatever reason. The paths to these files have traditionally been set in mingwenv.bat and should be reused in the new configure script. However, currently the build in trunk fails with linking errors so we should probably focus on making it usable again in the first place. I already spotted some errors which occure as a result of moving the files to the root of the trunk.
The CMake Windows build is still unstable and needs some work.
~Sebastian
*Semiodesk GmbH | *Werner-von-Siemens-Str. 6 Geb. 15k, 86159 Augsburg, Germany | Phone: +49 821 8854401 | Fax: +49 821 8854410 | www.semiodesk.com
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Semiodesk GmbH is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.
2016-04-20 15:12 GMT+02:00 Olof Bjarnason <olof.bjarnason@...400...>:
On 20 April 2016 at 15:00, Partha Bagchi <partha1b@...400...> wrote:
If you are using CMAKE and have Msys and Mingw etc., then simply do the following:
cmake -G "MSYS Makefiles" -DCMAKE etc. in your build folder
Is this documented in the relevant wiki page? I guess building on windows pages ...
On Wed, Apr 20, 2016 at 8:28 AM, LucaDC <dicappello@...2144...> wrote:
I see. Well, if they are for public utility it's correct that they are under revision control (hence copied to everybody's folders). But they are so specialized that I think that they are of little public utility: they need mingw64, they need it in a special folder and they need the "forfiles" command which is not present under all Windows OSs. They seem to be too tied to a specific configuration to always work.
I don't know cmake: does the reference to "x86_64-w64-mingw32" mean that the compilation is for 32 bit binaries built in a 64 bit environment?
Sebastian Faubel wrote
Surely is should use the MINGW_PATH environment variable here, but I
had
serious issues without this option set.
Just a try: doesn't 'cmake -D"CMAKE_SYSTEM_PREFIX_PATH:PATH=%MINGW_PATH%\x86_64-w64-mingw32" -G "MinGW Makefiles" ..' work? Or maybe (better) you should change the MINGW_PATH variable to 'C:\MinGW64\mingw64\x86_64-w64-mingw32' in your mingwenv.bat file (without committing it) and remove that option: actually I can't see any reason to tie a supposedly general script to such a particular need.
-- View this message in context: http://inkscape.13.x6.nabble.com/New-batch-files-in-trunk-tp4976419p4976429.... Sent from the Inkscape - Dev mailing list archive at Nabble.com.
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
You are making it unnecessarily complicated. All this is not needed if you follow the simple advice I provided above for Windows.
On Wed, Apr 20, 2016 at 11:31 AM, Sebastian Faubel <sebastian@...3248...> wrote:
Hello everybody,
i already said that the files need to be changed to using the environment variables for such as MINGW_PATH to work properly on other installations. This is a bug and i will fix it as soon as i find the time. However that is a simple thing to do and then they are useful for anyone trying to build Inkscape on Windows without MSYS (as it is described in the corresponding wikipages). There's quite some pitfalls when trying to do that and for these reasons there is the configure.bat. I think that we can get rid of the touch.bat file and integrate this functionality in configure.bat as a program option.
The forfiles command has been around since Windows Vista and I honestly do not know if Inkscape will be supporting Windows XP in future. If so, then this part should be rewritten to be compatible.
The path 'C:\MinGW64\mingw64\x86_64-w64-mingw32' refers to the MinGW version for 64-bit OSes that is referenced for download in the wikipages. On 64-bit Windows, the make command is still called 'mingw32-make' for whatever reason. The paths to these files have traditionally been set in mingwenv.bat and should be reused in the new configure script. However, currently the build in trunk fails with linking errors so we should probably focus on making it usable again in the first place. I already spotted some errors which occure as a result of moving the files to the root of the trunk.
The CMake Windows build is still unstable and needs some work.
~Sebastian
*Semiodesk GmbH | *Werner-von-Siemens-Str. 6 Geb. 15k, 86159 Augsburg, Germany | Phone: +49 821 8854401 | Fax: +49 821 8854410 | www.semiodesk.com
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Semiodesk GmbH is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.
2016-04-20 15:12 GMT+02:00 Olof Bjarnason <olof.bjarnason@...400...>:
On 20 April 2016 at 15:00, Partha Bagchi <partha1b@...400...> wrote:
If you are using CMAKE and have Msys and Mingw etc., then simply do the following:
cmake -G "MSYS Makefiles" -DCMAKE etc. in your build folder
Is this documented in the relevant wiki page? I guess building on windows pages ...
On Wed, Apr 20, 2016 at 8:28 AM, LucaDC <dicappello@...2144...> wrote:
I see. Well, if they are for public utility it's correct that they are under revision control (hence copied to everybody's folders). But they are so specialized that I think that they are of little public utility: they need mingw64, they need it in a special folder and they need the "forfiles" command which is not present under all Windows OSs. They seem to be too tied to a specific configuration to always work.
I don't know cmake: does the reference to "x86_64-w64-mingw32" mean that the compilation is for 32 bit binaries built in a 64 bit environment?
Sebastian Faubel wrote
Surely is should use the MINGW_PATH environment variable here, but I
had
serious issues without this option set.
Just a try: doesn't 'cmake -D"CMAKE_SYSTEM_PREFIX_PATH:PATH=%MINGW_PATH%\x86_64-w64-mingw32" -G "MinGW Makefiles" ..' work? Or maybe (better) you should change the MINGW_PATH variable to 'C:\MinGW64\mingw64\x86_64-w64-mingw32' in your mingwenv.bat file (without committing it) and remove that option: actually I can't see any reason to tie a supposedly general script to such a particular need.
-- View this message in context: http://inkscape.13.x6.nabble.com/New-batch-files-in-trunk-tp4976419p4976429.... Sent from the Inkscape - Dev mailing list archive at Nabble.com.
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Partha;
Of course ideally we want few or no exceptions for how to build inkscape on different platforms, however currently we seem not to have reached quite zero differences.
Until then we need clear documentation on differences. Are the details of using cmake to build inkscape on windows up to date?
http://wiki.inkscape.org/wiki/index.php/CMake On 20 Apr 2016 15:02, "Partha Bagchi" <partha1b@...400...> wrote:
If you are using CMAKE and have Msys and Mingw etc., then simply do the following:
cmake -G "MSYS Makefiles" -DCMAKE etc. in your build folder
On Wed, Apr 20, 2016 at 8:28 AM, LucaDC <dicappello@...2144...> wrote:
I see. Well, if they are for public utility it's correct that they are under revision control (hence copied to everybody's folders). But they are so specialized that I think that they are of little public utility: they need mingw64, they need it in a special folder and they need the "forfiles" command which is not present under all Windows OSs. They seem to be too tied to a specific configuration to always work.
I don't know cmake: does the reference to "x86_64-w64-mingw32" mean that the compilation is for 32 bit binaries built in a 64 bit environment?
Sebastian Faubel wrote
Surely is should use the MINGW_PATH environment variable here, but I had serious issues without this option set.
Just a try: doesn't 'cmake -D"CMAKE_SYSTEM_PREFIX_PATH:PATH=%MINGW_PATH%\x86_64-w64-mingw32" -G "MinGW Makefiles" ..' work? Or maybe (better) you should change the MINGW_PATH variable to 'C:\MinGW64\mingw64\x86_64-w64-mingw32' in your mingwenv.bat file (without committing it) and remove that option: actually I can't see any reason to tie a supposedly general script to such a particular need.
-- View this message in context: http://inkscape.13.x6.nabble.com/New-batch-files-in-trunk-tp4976419p4976429.... Sent from the Inkscape - Dev mailing list archive at Nabble.com.
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi Olof,
Based on the information provided on that page, I am unable to determine what the CMakeLists.txt looks like. Also, I see nothing about building on Windows. So I would say it's not up to date. :)
Thanks, Partha
On Wed, Apr 20, 2016 at 12:10 PM, Olof Bjarnason <olof.bjarnason@...400...> wrote:
Partha;
Of course ideally we want few or no exceptions for how to build inkscape on different platforms, however currently we seem not to have reached quite zero differences.
Until then we need clear documentation on differences. Are the details of using cmake to build inkscape on windows up to date?
http://wiki.inkscape.org/wiki/index.php/CMake On 20 Apr 2016 15:02, "Partha Bagchi" <partha1b@...400...> wrote:
If you are using CMAKE and have Msys and Mingw etc., then simply do the following:
cmake -G "MSYS Makefiles" -DCMAKE etc. in your build folder
On Wed, Apr 20, 2016 at 8:28 AM, LucaDC <dicappello@...2144...> wrote:
I see. Well, if they are for public utility it's correct that they are under revision control (hence copied to everybody's folders). But they are so specialized that I think that they are of little public utility: they need mingw64, they need it in a special folder and they need the "forfiles" command which is not present under all Windows OSs. They seem to be too tied to a specific configuration to always work.
I don't know cmake: does the reference to "x86_64-w64-mingw32" mean that the compilation is for 32 bit binaries built in a 64 bit environment?
Sebastian Faubel wrote
Surely is should use the MINGW_PATH environment variable here, but I
had
serious issues without this option set.
Just a try: doesn't 'cmake -D"CMAKE_SYSTEM_PREFIX_PATH:PATH=%MINGW_PATH%\x86_64-w64-mingw32" -G "MinGW Makefiles" ..' work? Or maybe (better) you should change the MINGW_PATH variable to 'C:\MinGW64\mingw64\x86_64-w64-mingw32' in your mingwenv.bat file (without committing it) and remove that option: actually I can't see any reason to tie a supposedly general script to such a particular need.
-- View this message in context: http://inkscape.13.x6.nabble.com/New-batch-files-in-trunk-tp4976419p4976429.... Sent from the Inkscape - Dev mailing list archive at Nabble.com.
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 20 April 2016 at 18:37, Partha Bagchi <partha1b@...400...> wrote:
Hi Olof,
Based on the information provided on that page, I am unable to determine what the CMakeLists.txt looks like. Also, I see nothing about building on Windows. So I would say it's not up to date. :)
OK, I found the page that seems most appropriate for building on Windows.
http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows_64-bit
Would you mind updating it, or giving me the details here so I can do it?
Regards,
Thanks, Partha
On Wed, Apr 20, 2016 at 12:10 PM, Olof Bjarnason <olof.bjarnason@...400...
wrote:
Partha;
Of course ideally we want few or no exceptions for how to build inkscape on different platforms, however currently we seem not to have reached quite zero differences.
Until then we need clear documentation on differences. Are the details of using cmake to build inkscape on windows up to date?
http://wiki.inkscape.org/wiki/index.php/CMake On 20 Apr 2016 15:02, "Partha Bagchi" <partha1b@...400...> wrote:
If you are using CMAKE and have Msys and Mingw etc., then simply do the following:
cmake -G "MSYS Makefiles" -DCMAKE etc. in your build folder
On Wed, Apr 20, 2016 at 8:28 AM, LucaDC <dicappello@...2144...> wrote:
I see. Well, if they are for public utility it's correct that they are under revision control (hence copied to everybody's folders). But they are so specialized that I think that they are of little public utility: they need mingw64, they need it in a special folder and they need the "forfiles" command which is not present under all Windows OSs. They seem to be too tied to a specific configuration to always work.
I don't know cmake: does the reference to "x86_64-w64-mingw32" mean that the compilation is for 32 bit binaries built in a 64 bit environment?
Sebastian Faubel wrote
Surely is should use the MINGW_PATH environment variable here, but I
had
serious issues without this option set.
Just a try: doesn't 'cmake -D"CMAKE_SYSTEM_PREFIX_PATH:PATH=%MINGW_PATH%\x86_64-w64-mingw32" -G "MinGW Makefiles" ..' work? Or maybe (better) you should change the MINGW_PATH variable to 'C:\MinGW64\mingw64\x86_64-w64-mingw32' in your mingwenv.bat file (without committing it) and remove that option: actually I can't see any reason to tie a supposedly general script to such a particular need.
-- View this message in context: http://inkscape.13.x6.nabble.com/New-batch-files-in-trunk-tp4976419p4976429.... Sent from the Inkscape - Dev mailing list archive at Nabble.com.
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi Olof,
Yes, this page looks more like it. However, this page asks you to create minGW Makefiles as opposed to MSYS Makefiles I suggested. This is OK as well. I personally prefer the Msys shell to do my various builds.
I think Eduard is managing this page? I have been providing the devlibs for the 64-bit builds while he's been handling the packaging and building. Let's wait for him to respond.
Thanks, Partha
On Wed, Apr 20, 2016 at 2:16 PM, Olof Bjarnason <olof.bjarnason@...400...> wrote:
On 20 April 2016 at 18:37, Partha Bagchi <partha1b@...400...> wrote:
Hi Olof,
Based on the information provided on that page, I am unable to determine what the CMakeLists.txt looks like. Also, I see nothing about building on Windows. So I would say it's not up to date. :)
OK, I found the page that seems most appropriate for building on Windows.
http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows_64-bit
Would you mind updating it, or giving me the details here so I can do it?
Regards,
Thanks, Partha
On Wed, Apr 20, 2016 at 12:10 PM, Olof Bjarnason < olof.bjarnason@...400...> wrote:
Partha;
Of course ideally we want few or no exceptions for how to build inkscape on different platforms, however currently we seem not to have reached quite zero differences.
Until then we need clear documentation on differences. Are the details of using cmake to build inkscape on windows up to date?
http://wiki.inkscape.org/wiki/index.php/CMake On 20 Apr 2016 15:02, "Partha Bagchi" <partha1b@...400...> wrote:
If you are using CMAKE and have Msys and Mingw etc., then simply do the following:
cmake -G "MSYS Makefiles" -DCMAKE etc. in your build folder
On Wed, Apr 20, 2016 at 8:28 AM, LucaDC <dicappello@...2144...
wrote:
I see. Well, if they are for public utility it's correct that they are under revision control (hence copied to everybody's folders). But they are so specialized that I think that they are of little public utility: they need mingw64, they need it in a special folder and they need the "forfiles" command which is not present under all Windows OSs. They seem to be too tied to a specific configuration to always work.
I don't know cmake: does the reference to "x86_64-w64-mingw32" mean that the compilation is for 32 bit binaries built in a 64 bit environment?
Sebastian Faubel wrote
Surely is should use the MINGW_PATH environment variable here, but I
had
serious issues without this option set.
Just a try: doesn't 'cmake -D"CMAKE_SYSTEM_PREFIX_PATH:PATH=%MINGW_PATH%\x86_64-w64-mingw32" -G "MinGW Makefiles" ..' work? Or maybe (better) you should change the MINGW_PATH variable to 'C:\MinGW64\mingw64\x86_64-w64-mingw32' in your mingwenv.bat file (without committing it) and remove that option: actually I can't see any reason to tie a supposedly general script to such a particular need.
-- View this message in context: http://inkscape.13.x6.nabble.com/New-batch-files-in-trunk-tp4976419p4976429.... Sent from the Inkscape - Dev mailing list archive at Nabble.com.
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 20 April 2016 at 21:45, Partha Bagchi <partha1b@...400...> wrote:
Hi Olof,
Yes, this page looks more like it. However, this page asks you to create minGW Makefiles as opposed to MSYS Makefiles I suggested. This is OK as well. I personally prefer the Msys shell to do my various builds.
I think Eduard is managing this page? I have been providing the devlibs for the 64-bit builds while he's been handling the packaging and building. Let's wait for him to respond.
Sounds good,
/Olof
Thanks, Partha
On Wed, Apr 20, 2016 at 2:16 PM, Olof Bjarnason <olof.bjarnason@...400...> wrote:
On 20 April 2016 at 18:37, Partha Bagchi <partha1b@...400...> wrote:
Hi Olof,
Based on the information provided on that page, I am unable to determine what the CMakeLists.txt looks like. Also, I see nothing about building on Windows. So I would say it's not up to date. :)
OK, I found the page that seems most appropriate for building on Windows.
http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows_64-bit
Would you mind updating it, or giving me the details here so I can do it?
Regards,
Thanks, Partha
On Wed, Apr 20, 2016 at 12:10 PM, Olof Bjarnason < olof.bjarnason@...400...> wrote:
Partha;
Of course ideally we want few or no exceptions for how to build inkscape on different platforms, however currently we seem not to have reached quite zero differences.
Until then we need clear documentation on differences. Are the details of using cmake to build inkscape on windows up to date?
http://wiki.inkscape.org/wiki/index.php/CMake On 20 Apr 2016 15:02, "Partha Bagchi" <partha1b@...400...> wrote:
If you are using CMAKE and have Msys and Mingw etc., then simply do the following:
cmake -G "MSYS Makefiles" -DCMAKE etc. in your build folder
On Wed, Apr 20, 2016 at 8:28 AM, LucaDC < dicappello@...2144...> wrote:
I see. Well, if they are for public utility it's correct that they are under revision control (hence copied to everybody's folders). But they are so specialized that I think that they are of little public utility: they need mingw64, they need it in a special folder and they need the "forfiles" command which is not present under all Windows OSs. They seem to be too tied to a specific configuration to always work.
I don't know cmake: does the reference to "x86_64-w64-mingw32" mean that the compilation is for 32 bit binaries built in a 64 bit environment?
Sebastian Faubel wrote > Surely is should use the MINGW_PATH environment variable here, but I had > serious issues without this option set.
Just a try: doesn't 'cmake -D"CMAKE_SYSTEM_PREFIX_PATH:PATH=%MINGW_PATH%\x86_64-w64-mingw32" -G "MinGW Makefiles" ..' work? Or maybe (better) you should change the MINGW_PATH variable to 'C:\MinGW64\mingw64\x86_64-w64-mingw32' in your mingwenv.bat file (without committing it) and remove that option: actually I can't see any reason to tie a supposedly general script to such a particular need.
-- View this message in context: http://inkscape.13.x6.nabble.com/New-batch-files-in-trunk-tp4976419p4976429.... Sent from the Inkscape - Dev mailing list archive at Nabble.com.
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi all,
I was updating the instructions for cmake on win64 build here http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows_64-bit
I found that the cmake scripts do not create the bundle we used to have for running inkscape with all dependent dlls and stuff. I filed a bugreport here https://bugs.launchpad.net/inkscape/+bug/1571897
As we have a wiki, it is free for you to edit and update instructions. I think that "building inkscape on windows using CMake and MSyS" is also an alternative and could be documented. I was not aware of the "CMake" page in our wiki. Please keep the constructive spirit and help improve the CMake files.
Possibly when CMake runs smoothly we can remove the additional helper files.
Currently for me CMake creates an inkscape.exe but this does not run yet. How does it works on your side? Did you tried building? I noticed an massive increase in compiling time. On my laptop btool buils in less than 5min. BUt with CMake it need more than 30min. Make spawns cmake and additional cmd proccesses that might be the bottelneck but I am not an expert.
Regards, Adib. --
On Wed, Apr 20, 2016 at 9:55 PM, Olof Bjarnason <olof.bjarnason@...400...> wrote:
On 20 April 2016 at 21:45, Partha Bagchi <partha1b@...400...> wrote:
Hi Olof,
Yes, this page looks more like it. However, this page asks you to create minGW Makefiles as opposed to MSYS Makefiles I suggested. This is OK as well. I personally prefer the Msys shell to do my various builds.
I think Eduard is managing this page? I have been providing the devlibs for the 64-bit builds while he's been handling the packaging and building. Let's wait for him to respond.
Sounds good,
/Olof
Thanks, Partha
On Wed, Apr 20, 2016 at 2:16 PM, Olof Bjarnason <olof.bjarnason@...400...
wrote:
On 20 April 2016 at 18:37, Partha Bagchi <partha1b@...400...> wrote:
Hi Olof,
Based on the information provided on that page, I am unable to determine what the CMakeLists.txt looks like. Also, I see nothing about building on Windows. So I would say it's not up to date. :)
OK, I found the page that seems most appropriate for building on Windows.
http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows_64-bit
Would you mind updating it, or giving me the details here so I can do it?
Regards,
Thanks, Partha
On Wed, Apr 20, 2016 at 12:10 PM, Olof Bjarnason < olof.bjarnason@...400...> wrote:
Partha;
Of course ideally we want few or no exceptions for how to build inkscape on different platforms, however currently we seem not to have reached quite zero differences.
Until then we need clear documentation on differences. Are the details of using cmake to build inkscape on windows up to date?
http://wiki.inkscape.org/wiki/index.php/CMake On 20 Apr 2016 15:02, "Partha Bagchi" <partha1b@...400...> wrote:
If you are using CMAKE and have Msys and Mingw etc., then simply do the following:
cmake -G "MSYS Makefiles" -DCMAKE etc. in your build folder
On Wed, Apr 20, 2016 at 8:28 AM, LucaDC < dicappello@...2144...> wrote:
> I see. > Well, if they are for public utility it's correct that they are under > revision control (hence copied to everybody's folders). > But they are so specialized that I think that they are of little > public > utility: they need mingw64, they need it in a special folder and > they need > the "forfiles" command which is not present under all Windows OSs. > They seem > to be too tied to a specific configuration to always work. > > I don't know cmake: does the reference to "x86_64-w64-mingw32" mean > that the > compilation is for 32 bit binaries built in a 64 bit environment? > > > Sebastian Faubel wrote > > Surely is should use the MINGW_PATH environment variable here, but > I had > > serious issues without this option set. > > Just a try: doesn't 'cmake > -D"CMAKE_SYSTEM_PREFIX_PATH:PATH=%MINGW_PATH%\x86_64-w64-mingw32" -G > "MinGW > Makefiles" ..' work? > Or maybe (better) you should change the MINGW_PATH variable to > 'C:\MinGW64\mingw64\x86_64-w64-mingw32' in your mingwenv.bat file > (without > committing it) and remove that option: actually I can't see any > reason to > tie a supposedly general script to such a particular need. > > > > > -- > View this message in context: > http://inkscape.13.x6.nabble.com/New-batch-files-in-trunk-tp4976419p4976429.... > Sent from the Inkscape - Dev mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Find and fix application performance issues faster with Applications > Manager > Applications Manager provides deep performance insights into > multiple tiers of > your business applications. It resolves application problems quickly > and > reduces your MTTR. Get your free trial! > https://ad.doubleclick.net/ddm/clk/302982198;130105516;z > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel >
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 20 April 2016 at 21:45, Partha Bagchi <partha1b@...400... mailto:partha1b@...400...> wrote:
Yes, this page looks more like it. However, this page asks you to create minGW Makefiles as opposed to MSYS Makefiles I suggested. This is OK as well. I personally prefer the Msys shell to do my various builds.
I think Eduard is managing this page? I have been providing the devlibs for the 64-bit builds while he's been handling the packaging and building. Let's wait for him to respond.
Sorry guys, I only updated the page to adapt it to the updated devlibs provided by Partha and only with respect to the btool build. I did not have time to look into CMake myself, so I can't help you out with it (yet).
@Partha: What's the advantage of "MSYS Makefiles" compared to "minGW Makefiles"? The problem I see is that we'd probably have to require peole to install MSYS and therefore yet another dependecy which would make it even harder to get started with development on Windows. If we could avoid it that would likely be preferable, but if MSYS offers a large benefit it might be worth a thought.
Regards, Eduard
On Wed, Apr 20, 2016 at 4:20 PM, Eduard Braun <Eduard.Braun2@...173...> wrote:
On 20 April 2016 at 21:45, Partha Bagchi <partha1b@...400...> wrote:
Yes, this page looks more like it. However, this page asks you to create minGW Makefiles as opposed to MSYS Makefiles I suggested. This is OK as well. I personally prefer the Msys shell to do my various builds.
I think Eduard is managing this page? I have been providing the devlibs for the 64-bit builds while he's been handling the packaging and building. Let's wait for him to respond.
Sorry guys, I only updated the page to adapt it to the updated devlibs provided by Partha and only with respect to the btool build. I did not have time to look into CMake myself, so I can't help you out with it (yet).
I have not tried to build Inkscape with cmake and I'll be able to help out when I have some time to git clone and build.
@Partha: What's the advantage of "MSYS Makefiles" compared to "minGW Makefiles"?
Well, as I said, I prefer Msys since I've been using it for a long time. It provides a very familiar bash like shell on Windows for me and that's all I use it for. So, it should not be a hardship for anyone, I think. :)
The problem I see is that we'd probably have to require peole to install MSYS and therefore yet another dependecy which would make it even harder to get started with development on Windows. If we could avoid it that would likely be preferable, but if MSYS offers a large benefit it might be worth a thought.
Well to me, Msys is "install it and forget it", but ymmv.
Regards, Eduard
On 21 Apr 2016 00:30, "Partha Bagchi" <partha1b@...400...> wrote:
On Wed, Apr 20, 2016 at 4:20 PM, Eduard Braun <Eduard.Braun2@...173...>
wrote:
On 20 April 2016 at 21:45, Partha Bagchi <partha1b@...400...> wrote:
Yes, this page looks more like it. However, this page asks you to
create minGW Makefiles as opposed to MSYS Makefiles I suggested. This is OK as well. I personally prefer the Msys shell to do my various builds.
I think Eduard is managing this page? I have been providing the devlibs
for the 64-bit builds while he's been handling the packaging and building. Let's wait for him to respond.
Sorry guys, I only updated the page to adapt it to the updated devlibs
provided by Partha and only with respect to the btool build.
I did not have time to look into CMake myself, so I can't help you out
with it (yet).
I have not tried to build Inkscape with cmake and I'll be able to help
out when I have some time to git clone and build.
@Partha: What's the advantage of "MSYS Makefiles" compared to "minGW
Makefiles"?
Well, as I said, I prefer Msys since I've been using it for a long time.
It provides a very familiar bash like shell on Windows for me and that's all I use it for. So, it should not be a hardship for anyone, I think. :)
Because of gits popularity whatever is included in the git for windows installation is likely to be the choice that gains most developer traction:
https://git-scm.com/download/win
The problem I see is that we'd probably have to require peole to install
MSYS and therefore yet another dependecy which would make it even harder to get started with development on Windows. If we could avoid it that would likely be preferable, but if MSYS offers a large benefit it might be worth a thought.
Well to me, Msys is "install it and forget it", but ymmv.
Regards, Eduard
Am 21.04.2016 um 07:18 schrieb Olof Bjarnason:
Because of gits popularity whatever is included in the git for windows installation is likely to be the choice that gains most developer traction:
It's not an an "either / or" decision (MinGW and MSYS are complimentary, MSYS is installed as a part of the original MinGW nowadays, which we can't use for 64-bit builds though). MinGW is always needed since it contains the GNU Compiler Collection and therefore is mandatory.
MSYS provides a small subset of *nix tools that might be useful while developing but typically are not needed. It's included in GIT, but normally not added to the PATH, so it would complicate setup instructions even more (also you're quickly in incompatibility hell if any program adds itself to the PATH variable - e.g. the python included in Bazaar messed up my Inkscape plugin system once)
I'll see if I find some time to check out the CMake build myself in the coming weeks (since I should receive a new machine these days and hopefully don't need an hour for a full compile of Inkscape anymore it might increase my motivation to play around with the build infrastructure. ;-) ). I guess I can then tell better what advantages MSYS might offer.
Regards, Eduard
On 21 April 2016 at 10:46, Eduard Braun <Eduard.Braun2@...173...> wrote:
Am 21.04.2016 um 07:18 schrieb Olof Bjarnason:
Because of gits popularity whatever is included in the git for windows installation is likely to be the choice that gains most developer traction:
It's not an an "either / or" decision (MinGW and MSYS are complimentary, MSYS is installed as a part of the original MinGW nowadays, which we can't use for 64-bit builds though). MinGW is always needed since it contains the GNU Compiler Collection and therefore is mandatory.
MSYS provides a small subset of *nix tools that might be useful while developing but typically are not needed. It's included in GIT, but normally not added to the PATH, so it would complicate setup instructions even more (also you're quickly in incompatibility hell if any program adds itself to the PATH variable - e.g. the python included in Bazaar messed up my Inkscape plugin system once)
I'll see if I find some time to check out the CMake build myself in the coming weeks (since I should receive a new machine these days and hopefully don't need an hour for a full compile of Inkscape anymore it might increase my motivation to play around with the build infrastructure. ;-) ). I guess I can then tell better what advantages MSYS might offer.
Sounds great. I think getting Inkscape building with cmake on Windows & OSX is two of the last few items left on the todo-list for release 0.92, however I don't quite understand why as I believe 0.92 will be the last release built with autotools.
Can someone clarify on this?
Regards, Eduard
On Thu, Apr 21, 2016, at 01:46 AM, Eduard Braun wrote:
I'll see if I find some time to check out the CMake build myself in the coming weeks (since I should receive a new machine these days and hopefully don't need an hour for a full compile of Inkscape anymore it might increase my motivation to play around with the build infrastructure. ;-) ). I guess I can then tell better what advantages MSYS might offer.
BTW, I'm up and running on a new laptop, so I started checking out the build instructions on the wiki to see how it goes. Should get to the compiling phase tonight.
So we'll see how the pages currently hold up.
Hello Sebastian,
I am trying to composit a new shipable inkscape folder containing all depending dll and stuff.
I am struggeling on crashes as I copy more files into that directory.
Could you have a look at https://bugs.launchpad.net/inkscape/+bug/1571897
Regards, Adib. --
On Wed, Apr 20, 2016 at 11:01 AM, Sebastian Faubel <sebastian@...3248...> wrote:
Hello everyone,
I created these files to simplify building Inkscape on Windows. Originally they were not located in the root of the trunk, but in a separate 'build' folder because it is good practise for CMake to not build in the root/source directory. Somehow they moved when the merge was created. Anyway, there's a reason for these files to be there. In particular:
configure.bat: Deletes the CMake cache and regenerates all the makefiles to be sure that any changes in CMake files are actually applied. I spend hours on trying to solve an issue just to find out that relevant Makefiles were not regenerated by CMake for any reason. Moreover, the trunk version of the file is missing an option to CMake I had to add in order for it to build at all. I do not know why it was removed:
REM Configure using the MinGW compiler chain. cmake -D"CMAKE_SYSTEM_PREFIX_PATH:PATH=C:\MinGW64\mingw64\x86_64-w64-mingw32" -G "MinGW Makefiles" ..
Surely is should use the MINGW_PATH environment variable here, but I had serious issues without this option set. The file could also be used to setup the system environment variables, such as MINGW_PATH if they are not set to a valid value and store them somewhere making the setup somehow more user friendly.
touch.bat: Since there is no such thing as touch on Windows, I created the script to reset the modification dates of all .obj files in case of changes to the CMake configuration which would trigger a full rebuild. This is simply a time and enery saver.
I did not have the chance to check out trunk and try to build it on my machine. But I will do it this week. I saw that the wiki got updated with new instructions for compiling on Windows 64-bit. Wonderful, thanks Adib.
~Sebastian
*Semiodesk GmbH | *Werner-von-Siemens-Str. 6 Geb. 15k, 86159 Augsburg, Germany | Phone: +49 821 8854401 | Fax: +49 821 8854410 | www.semiodesk.com
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Semiodesk GmbH is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.
2016-04-20 8:57 GMT+02:00 Olof Bjarnason <olof.bjarnason@...400...>:
On 20 April 2016 at 08:27, LucaDC <dicappello@...2144...> wrote:
In rev. 14855 ("merge Moritz's branch") two batch files have been added in the root of trunk: configure.bat and touch.bat. Both of them contain a particular system's specific configurations like a fixed path and a reference to some script/program (forfiles) so little chances they are useful for others.
Being them useless and to avoid confusion I think they should be removed from version control.
I believe they were used to get the Windows build working with cmake, so if they improved/corrected they probably would have use for the Windows build maintainer. Is there a subfolder for Windows building to move them to?
Sebastian, Moritz friend did mention some weird for,, syntax to stop cmake from rebuilding "everything" each time he made a change to get Inkscape building on his Windows machine.
Maybe Sebastian and Moritz knows more about this?
-- View this message in context: http://inkscape.13.x6.nabble.com/New-batch-files-in-trunk-tp4976419.html Sent from the Inkscape - Dev mailing list archive at Nabble.com.
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi Adib,
i'll have a look at it today. First I will try to make a clean build on my machine and then try to reproduce the dll loading issue you mentioned in launchpad.
Cheers,
~Sebastian
*Semiodesk GmbH | *Werner-von-Siemens-Str. 6 Geb. 15k, 86159 Augsburg, Germany | Phone: +49 821 8854401 | Fax: +49 821 8854410 | www.semiodesk.com
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Semiodesk GmbH is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.
2016-04-24 0:22 GMT+02:00 the Adib <theadib@...400...>:
Hello Sebastian,
I am trying to composit a new shipable inkscape folder containing all depending dll and stuff.
I am struggeling on crashes as I copy more files into that directory.
Could you have a look at https://bugs.launchpad.net/inkscape/+bug/1571897
Regards, Adib.
On Wed, Apr 20, 2016 at 11:01 AM, Sebastian Faubel < sebastian@...3248...> wrote:
Hello everyone,
I created these files to simplify building Inkscape on Windows. Originally they were not located in the root of the trunk, but in a separate 'build' folder because it is good practise for CMake to not build in the root/source directory. Somehow they moved when the merge was created. Anyway, there's a reason for these files to be there. In particular:
configure.bat: Deletes the CMake cache and regenerates all the makefiles to be sure that any changes in CMake files are actually applied. I spend hours on trying to solve an issue just to find out that relevant Makefiles were not regenerated by CMake for any reason. Moreover, the trunk version of the file is missing an option to CMake I had to add in order for it to build at all. I do not know why it was removed:
REM Configure using the MinGW compiler chain. cmake -D"CMAKE_SYSTEM_PREFIX_PATH:PATH=C:\MinGW64\mingw64\x86_64-w64-mingw32" -G "MinGW Makefiles" ..
Surely is should use the MINGW_PATH environment variable here, but I had serious issues without this option set. The file could also be used to setup the system environment variables, such as MINGW_PATH if they are not set to a valid value and store them somewhere making the setup somehow more user friendly.
touch.bat: Since there is no such thing as touch on Windows, I created the script to reset the modification dates of all .obj files in case of changes to the CMake configuration which would trigger a full rebuild. This is simply a time and enery saver.
I did not have the chance to check out trunk and try to build it on my machine. But I will do it this week. I saw that the wiki got updated with new instructions for compiling on Windows 64-bit. Wonderful, thanks Adib.
~Sebastian
*Semiodesk GmbH | *Werner-von-Siemens-Str. 6 Geb. 15k, 86159 Augsburg, Germany | Phone: +49 821 8854401 | Fax: +49 821 8854410 | www.semiodesk.com
This e-mail message may contain confidential or legally privileged information and is intended only for the use of the intended recipient(s). Any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is prohibited. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, or contain viruses. Anyone who communicates with us by e-mail is deemed to have accepted these risks. Semiodesk GmbH is not responsible for errors or omissions in this message and denies any responsibility for any damage arising from the use of e-mail. Any opinion and other statement contained in this message and any attachment are solely those of the author and do not necessarily represent those of the company.
2016-04-20 8:57 GMT+02:00 Olof Bjarnason <olof.bjarnason@...400...>:
On 20 April 2016 at 08:27, LucaDC <dicappello@...2144...> wrote:
In rev. 14855 ("merge Moritz's branch") two batch files have been added in the root of trunk: configure.bat and touch.bat. Both of them contain a particular system's specific configurations like a fixed path and a reference to some script/program (forfiles) so little chances they are useful for others.
Being them useless and to avoid confusion I think they should be removed from version control.
I believe they were used to get the Windows build working with cmake, so if they improved/corrected they probably would have use for the Windows build maintainer. Is there a subfolder for Windows building to move them to?
Sebastian, Moritz friend did mention some weird for,, syntax to stop cmake from rebuilding "everything" each time he made a change to get Inkscape building on his Windows machine.
Maybe Sebastian and Moritz knows more about this?
-- View this message in context: http://inkscape.13.x6.nabble.com/New-batch-files-in-trunk-tp4976419.html Sent from the Inkscape - Dev mailing list archive at Nabble.com.
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Mon, Apr 25, 2016, at 12:02 AM, Sebastian Faubel wrote:
Hi Adib,
i'll have a look at it today. First I will try to make a clean build on my machine and then try to reproduce the dll loading issue you mentioned in launchpad.
Cheers,
~Sebastian
I've got a little more progress happening, including resolving a few CMake issues to allow for shared UNIX/win32 install lines.
The next step was to spin a btool build. That works for me. So I'm now on to replicating the whole staging setup.
-- Jon A. Cruz jon@...18...
participants (7)
-
Eduard Braun -
Jon A. Cruz -
LucaDC -
Olof Bjarnason -
Partha Bagchi -
Sebastian Faubel -
the Adib