-
Notifications
You must be signed in to change notification settings - Fork 35
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
output settings ignored #4
Comments
Hi Tomas, |
Hi Tomas, I have just uploaded the new documentation with correct syntax of fobos file. Please, note also two other differences with respect older versions:
This is because i like to perform test on-the-fly, thus to a baseline fobos options of compilation flags I often sum some particular options by the command line, without the necessity of write a new fobos file. I you do not like such a behavior I can make this optional... |
Hi Stefano, So I would like it if you could add the long name for output back into the config files. I don't have a strong opinion about appending command line flags to the configuration file flags, the only case where this would give unexpected results is if you give flags to the compiler by accident. But that seems hard to do, why would you put flags there if you don't want them? |
Hi Tomas, As the possibility to overload config file options is concerned, I just think that it can be useful. Let us suppose we have made a basic fobos where cflags=-O2 among other options. Now we want to compile in debug mode but we are so lazy that we do not like to write another fobos file. To this purpose, overload cflags rather than override is useful because typing FoBoS.py build -clfags '-C -g' (with the orginal fobos) we finally obtain cflags=-C -g -O2... However, I have already planned to make this feature optional (or to remove it). Thank you for your help |
This seems fine |
Hello Stefano,
I just realized that the latest FoBis names the final executable with the name of the source file being compiled, whereas previously you could specify the name of the executable in the configuration file and have that respected.
Now I would have to rename the builds manually if I want several different versions built with different preprocessing flags.
The text was updated successfully, but these errors were encountered: