Hello!
I had the following issue, which I was not able to resolve elegantly.
For a mock, I needed to link lssl and lcrypto. I tried adding these compiler flags to the :flags section, but that did not quite work. For a successful compilation, these flags need to be given at the end of the command, something like this: gcc {in} -i {out} -lssl -lcrypto. When using the :flags section, those flags will always be placed directly after gcc, which leads to a failed compilation.
My workaround was to manually set up the linker under the :tools section, where I could place the crpyto flags last, which then compiled successfully.
I'd prefer using the :flags section, as I would not have to mess with the default linker settings, which for me are not immediately clear. It would also make the project setup simpler.
Am I missing an option or is this currently not possible?
Thanks and best regards!
Hello!
I had the following issue, which I was not able to resolve elegantly.
For a mock, I needed to link
lsslandlcrypto. I tried adding these compiler flags to the:flagssection, but that did not quite work. For a successful compilation, these flags need to be given at the end of the command, something like this:gcc {in} -i {out} -lssl -lcrypto. When using the:flagssection, those flags will always be placed directly aftergcc, which leads to a failed compilation.My workaround was to manually set up the linker under the
:toolssection, where I could place the crpyto flags last, which then compiled successfully.I'd prefer using the
:flagssection, as I would not have to mess with the default linker settings, which for me are not immediately clear. It would also make the project setup simpler.Am I missing an option or is this currently not possible?
Thanks and best regards!