thanks, I guess I will need this for the next release for conda-forge. Or is the version.h already filled for the source of a FreeCAD-release?
triplus wrote: ↑Sat Sep 08, 2018 7:43 am
Still wondering on why couldn't git be used directly again? And do everything in an automated way on Circle CI. Compared to now doing everything manually?
Ok I somehow managed to upload packages from circle-ci to the freecad-channel (osx and linux) for now. This means that I am able to use git directly and the version.h should be correctly setup (hopefully). Originally I only wanted to see the error report generated by circle-ci, but somehow all the token-stuff was setup in a right way from a previous attempt. So I am still confused how this could work out of the box.
I could try to setup the same for windows, but I am not sure if it makes much sense to do so, as you do the builds manually.
HOWTO change the upload channel (reminder for myself):
- changing the channels in ci_support/[linux_.yaml, win_.yaml, osx_.yaml]
- using label dev instead of main to make sure user can select explicitly which build to install (in case both channels are in the config)
- these changes will be removed by rerendering the feedstock, so better to avoid rerendering and rebase on rerendered conda-forge-feedstock.