Did you try to apply the patch?
What’s in MyOwnApplicationImport?
I changed the import to CppApplication and it doesn’t recurse
https://pastebin.com/jKMxpWGe, so I’d say the problem is in
MyOwnApplicationImport.
Ivan
> 12 июля 2024 г., в 23:06, Björn Schäpers написал(а):
>
> No it did not r
My point is: Before just the exporting product needed to depend on the module
which generated the header by a single depends and setting one property on the
module.
Now the product still depends on the module, sets the property, but also has to
state something in its Export section. More (repeti
That’s an interesting use-case you brought.
I replied in the linked issue on how to achieve what you want.
Ivan
> 13 июля 2024 г., в 13:21, Maximilian Hrabowski
> написал(а):
>
>
> Hi all,
>
> i use qbs on macos to combine arm64 and x86_64 library builds into one
> universal library. My
You can add it once to the base item of the products (possibly with some
customisation using a prop). Usually there is already such an item in every
product.
Ivan
> 13 июля 2024 г., в 14:13, Björn Schäpers написал(а):
>
> Am 13.07.2024 um 02:15 schrieb Иван Комиссаров:
>>
>>> 12 июля 2024 г.
Am 13.07.2024 um 02:15 schrieb Иван Комиссаров:
12 июля 2024 г., в 23:24, Björn Schäpers написал(а):
Hi,
I have multiple dynamic libraries in my project tree, and use an export header similar to
your qbs_export.h. Overtime the style of those headers had changed a bit and recently I
replace
Hi all,
i use qbs on macos to combine arm64 and x86_64 library builds into one
universal library. My application compiles and links, but cannot start because
the install names/lib names used when linking the app are not correct – or –
basically they are correct but when combining the builds us
