Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Support out-of-source builds #309
When testing multiple configurations, it sucks having to check out new source code for every time as it makes it hard to quickly test against e.g. debug vs. release and old versions of libraries.
Out of source build works fine, but things like finding MCAD doesn't as it assumes that the library path is relative to the executable. This would need to be configured compile-time instead. There are probably other issues, but this would be a start.
Next step could be to write scripts to compile against misc. permutations of library dependencies and build settings. It would be cool to have something which would be trivial to set up on the misc. linux build services, gcc compile farm, as well as personal infrastructure. Basically light-weight distributed continuous integration using whatever is out there of resources.
This comment has been minimized.
This comment has been minimized.Show comment Hide comment
to fix the MCAD in out-of-source test build runs, i have been setting the OPENSCADPATH environment variable
i have worked on various parts of scripts to select build versions etc, but never actually got a polished 'finished' setup going.
i have always wondered if the VTK people would be willing to help us get test-uploads from the gcc farm to work with their CDash system... i have never asked though. i am not sure when they start charging money for access either.
we can auto-upload test results to sourceforge's website without to much trouble from the gcc compile farm, the main problem i have is how do you secure the ssh passphrase key? use 'screen' & detach? i know some people use keys without passphrases for this sort of thing but that doesnt feel good to me. but i know other people do things differently.