-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need to improve Fortran compiler finding for Windows/Mac Slicer extension build #55
Comments
This error seems to also be on the mac build: http://slicer.cdash.org/viewBuildError.php?buildid=1896073 It has a similar fortran environment variable set in the extensions driver script. Perhaps we can just set the environment variables on the system for those two machines? That would allow these to build while we sort out the rest. |
Looking into this, the compiler is found as expected: From http://slicer.cdash.org/buildSummary.php?buildid=2009360:
|
Using the CMake option
Context:
|
Seems to be related to AnacondaRecipes/aggregate#112 |
Running the following command also report an error
|
Since the issue is missing
then
|
Proper solution seems to be available at https://github.com/conda-forge/ambertools-feedstock/blob/04e4327e6a3cffdfda36158755ffe00c565fe08c/recipe/fake-bin/cc1 References: |
Using cc1 script referenced above allows the command to complete:
|
Problem solved using the following scripts also referenced from https://www.slicer.org/wiki/Documentation/Nightly/Developers/Fortran#macOS
|
Since packages for both macOS and Windows are now available, I am closing this issue. QA of the generated packages may reveal other issues but these should be tracked in separate issues. cc: @bpaniagua @allemangD |
The current method used on the Slicer factory machine to find the Fortran compiler needs some work.
This line:
https://github.com/Slicer/DashboardScripts/blob/af76712f7afd0e82f489f3f29ff64fd8569afb3f/overload-vs2015-slicerextensions_preview_nightly.cmake#L55
should set the environment variable, but this doesn't seem to be picked up by the extension build
The text was updated successfully, but these errors were encountered: