Was invoking LFC from make / cmake a good idea?

[LasseRosenow]

For now we implemented these features to enhance development so that the lfc gets executed whenever we compile our project.

This comes with a few downsides (at least for make):

• The implementation is very hacky and could always have unexpected issues such as make clean should also clean the src-gen directory lf-riot-uc-template#6
• Make buffers the output of LFC until the command has completed lf-riot-uc-template#3 is still unresolved and I am not sure if it is even possible
• We now have a somewhat strange workflow, that we first invoce LFC to generate our federate configurations manually and then invoke it automatically from then on.

Maybe it is better to just keep things separate and safe us a lot of headache in the future:

• We can still execute them in parallel: lfc src/CoapFederatedLF && make all term
• This way we also don't have the issue anymore that the LFC needs to finish before we will see its terminal output (make)
• We can generate a lfc.sh file for each federate to make the usage extremely easy such as ./lfc.sh && make all

@erlingrj @tanneberger

[erlingrj]

You raise good points and I dont have a good answer now. A brittle or confusing solution is worse than no solution. I am open to experimenting with a different approach e.g. a build script as you propose.

[LasseRosenow]

Okay I made a proposal in #215 :)