output settings ignored

[Tobychev]

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.

[szaghi]

Hi Tomas,
I have forgotten to update the documentation and the fobos example. For improve "fobos" features, some of its item have been renamed. In the earliest version of fobos you rename the target with "output=..."; in the last version this item has been renamed in "o=...". I am sorry, I update the documentation immediately.

[szaghi]

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:

1. the default value of "cflags" has been eliminated;
2. the fobos definition of "cflags", "lflags" and "preproc" overload (sum to) rather than override the value passed by means of the command line.

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...

[Tobychev]

Hi Stefano,
I understand the convenience of having short names for command line use, but I think there should also be verbose names for use in configuration files. Because configuration files are (in part) intended to make it possible to modify a certain build long after it was first was configured (and when the poor-fortran-man has forgotten all the details), it is pretty important that the meaning of the config options are clear from their names.

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?

[szaghi]

Hi Tomas,
you are right: for the fobos file it is better to have verbose (clear and meaningful) names... tomorrow I will fix this issue.

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

[Tobychev]

This seems fine