How can we achieve this without creating more work for the packaging team ?
Basically, automating (using TravisCI) to generate full symbol builds for debugging is becoming more essential everyday as we have more people willing to jump in, test and debug. I recently read over on the OSE wiki that ruslan (the creator of the OSE piping WB and contributor to the Flamingo WB) was having issues debugging FC (link) He writes
If it's issues with Travis maybe we can take some of the funds we have in bountysource and purchase a monthly travisCI plan so we get access to extended build times and whatever other amenities come with that...?rus wrote:I tried to find out how to debug FreeCAD. It just does not work . FreeCAD crashed. How I suppose to teach someone to program under these conditions?
We also need a better Debugging tutorial to captivate users to jump in the deep end of development. Right now we provide them with a superficial and tooth-less (no debug symbols) technique.
Paging all participants in the previous thread
Discussion: Framework for Automating Builds (buildbot etc..)