Closed Ju1He1 closed 1 day ago
is it possible to print the actual compiler and liker flags used by conan?
Sorry this was not responded back then @Ju1He1, sometimes the team is too busy and some tickets fall through the cracks.
This seems now outdated, with a new cmake-conan
integration, and also new CMakeDeps
and other generators.
I am closing this as outdated, please create new tickets if necessary, thanks for your feedback.
I'm trying to cross build on windows for an embedded target (arm-none-eabi). To achieve this, I'm using a cross compiling profile. Each embedded target has it's own specific compiler and linker flags
My cross compiling profile looks like this
the workflow is the recommended workflow from https://github.com/conan-io/cmake-conan. it's basically a
The workflow is not the issue, I can see that the embedded compiler (in my case gcc 10) is properly recognised. Include paths etc. are set properly. However I'm suspecting that my provided compiler and/or linker flags are ommitted. I would have expected a little more output from the conan build especially after adding a -v to the compiler and linker flags
Now compiling my project works fine however the linking fails
error : bin\foo.elf uses VFP register arguments, C:/Users/xxx/.conan/data/tinyxml/2.6.2/_/_/package/11b38960141478715841df824e568735e33d702c/lib/libtinyxml.a(tinyxml.cpp.obj) does not
=>In my case, I'd like to use the Hardware FPU of my embedded controller. However it looks like conan ignores my Compiler and/or linker flags.
=>how can i pass specify compiler or linker flags to conan?
Thx for your help :)