Closed cedricschwyter closed 4 years ago
Wait, somehow this does not work
The thing is, if you export the CC and CXX environment variables in the install script, the clang++ build will be built with g++...
This is exactly how I did it in my project, but it does not seem to work here. Does the scripts/build.sh
somehow export to the environment variables C and CXX?
Shouldn't do as far as I know, it only runs cmake and then make
Alright, apparently that fixed it. The mistake was this: if I export to environment variables from the install script, these updated environment variables will obviously not be updated outside of the shell of the script. So the install scripts gets run once with the --no-build
flag, does thus not run the scripts/build.sh
script. It exits. A new shell gets spawned when scripts/build.sh
is run. That shell will not overtake the updated values of the environment variables as these 'died' with the old shell. It's fixed now.
What you have to take into account though is that by exporting to the compiler environment variables you prohibit GitHub Actions from compiling with a different compiler aka Clang in this case. So, I went ahead and deleted the job for the Clang-compilation because it is rendered obsolete by this export to environment variables. It is an 'unpretty' fix, if you insisted on having a Clang-compilation (which I don't think is really necessary) we would have to come up with another solution.
Having just g++ is probably fine.
Also, just want to say thanks so much for your contributions this project, your additions have been very useful :)
Anytime, it's a pleasure ;)
In response to #174.