Debug builds would be nice to have. But I invest already too much time into updating the builds to the new compilers, so I don't see much chance that I work on debug builds.
Code: Select all
- Fork the feedstock: https://github.com/conda-forge/qt-feedstock - change to "debug" unix: - https://github.com/conda-forge/qt-feedstock/blob/master/recipe/build.sh#L95 - https://github.com/conda-forge/qt-feedstock/blob/master/recipe/build.sh#L153 windows: - https://github.com/conda-forge/qt-feedstock/blob/master/recipe/bld.bat#L148 ? - https://github.com/conda-forge/qt-feedstock/blob/master/recipe/bld.bat#L157 - increase build-number: - https://github.com/conda-forge/qt-feedstock/blob/master/recipe/meta.yaml#L26 - remove windows-skipping: - https://github.com/conda-forge/qt-feedstock/blob/master/recipe/meta.yaml#L27 - install miniconda: - install conda-build - install anaconda-client - install compilers (windows) - https://conda-forge.org/docs/buildwin.html#local-testing - run conda-build - fix all build-errors - upload to "freecad/label/debug"
Never heard of it before. What exactly is it good for and what are its benefits? Just by looking at their website I could not figure out that.Right now I handle the packages with Conan (https://conan.io)
Yes, debug libs are important for me, too. Does conan support a way to build the boost.python debug library with the debug version of Python? In the past this was one of the most challenging stuff when building the libpack.Also for me it is very important to have the debug libs....
I think it is time to move to VS2015 because of these reasons:Manuel and I started this discussion on PM, but it's better here.
What do you think is the best strategy?
You never should do this because usually this makes your application to crash. The behaviour is similar to what we had recently with two different Coin3d versions under Linux.My problem is also that I don't understand how debug-builds can be mixed with release builds.
If i want to change the OCC version i just have to update the name of the package."include(conan.cmake)
Ok, I understand. So if we build qt in debug mode, we also have to rebuild every library which freecad or deps link to and which depends on qt. Most-likely in the end we have to recompile every library in debug-mode which is a huge task.wmayer wrote:You never should do this because usually this makes your application to crash. The behaviour is similar to what we had recently with two different Coin3d versions under Linux.
Does this mean that it download pre-built binaries of the requested library? Or do you still have to build the libraries locally?If it is already local it will use this, if not it will be downloaded and then used.
I think the task is the same for all approaches; build the whole FreeCAD dependency stack in debug mode, ideally x32/x34, release/debug, 4X4 build matrix.