-
Notifications
You must be signed in to change notification settings - Fork 2
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
zero config #226
zero config #226
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm excited to see movement on this mode of operation. This looks like a good starting point for further development.
# Conflicts: # source/fab/tools.py
Just noticed a todo I'd put at the top, to test with ifort. Will do that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few more bits of tidying up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Time to bring this to trunk.
# Conflicts: # envs/docker/Dockerfile # source/fab/steps/analyse.py # tests/unit_tests/steps/test_compile_fortran.py
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Merge changes as expected.
First version of zero config command line tool.
Usage:
automatically found the following programs to build: second, first
Tested on:
So far, only tested using gfortran. That needs a linker flag,
-lgfortran
. We should try it with ifort, too. There might be a few linker flags we'll want to add to cover a wide variety of use cases.todo: