Alexandr Timofeev
Alexandr Timofeev
That's quite a handy thing! In my case, I thought about a more dynamic approach. The idea is to allow users create, share and use base recipes with some field...
Thanks for the info! I see. It's indeed shaky because the feature is experimental. There are interesting use-cases like this one: https://gitlab.com/grisumbras/conan-b2-helper
We experience the same issue on our Qemu-based build machine with Raspbian 10 with GCC 11 installed. We build through Conan but this is the only similar issue. The line...
Fixed by reconfigurating GCC with `--with-fpu=neon-fp-armv8` flag
It's the issue with GCC configuration it seems. So you either need to fix how Ubuntu configurated the compiler itself for Raspberry or pass an explicit `-mfpu` to compile flags.
That's why I think it could be great to extend the section about runtime linking to help new users with these gotchas. :slightly_smiling_face:
Yes, I don't imply that the advice is wrong, I suggest that it could be useful to extend the point in the material a bit since it's fairly brief now....
I do agree, better would be to say that such use case is underspecified. In my current projects, I use a `qml/` directory alongside the `src/` directory. Mixing it bloats...
I have a question. Let's say I have a QML app entrypoint: `qml.main.cpp`. Where do I put `qml` files for this entrypoint then? It should be designed in a manner...
Conan should probably not pull it up into the flags (if anything at all). The idea is that it's hard to reason about a global flag string if all subprojects...