How to detect compiler flag changes?

Hello,

I’m using Conan 1.0.4.

I’ve built a lot of dependencies with my darwin-toolchain as a build_requirement.

I had to add Bitcode support, so I’ve added the corresponding compiler flags -fembed-bitcode.

However, that had no impact on the package ID, and running conan install still installed the non-Bitcode binaries.

I thought about adding an option to my darwin-toolchain, but since this is a build_requirement it would have been discarded as soon as binary packages would have been created.

Is there a good way to prevent this issue? Apart from adding the option in every recipe I got?

Should the package ID depend on other things? Having a Gentoo-like flag handling might not be appropriate for Conan.

I did not dig a lot on that, but that seems like a tough problem!

EDIT: In this specific case, maybe bitcode should become a conan setting, it is specific to iOS (maybe watchOS and tvOS as well) but from my understanding it’s becoming widely used by iOS apps.

To help us debug your issue please explain:

• I’ve read the CONTRIBUTING guide.
• I’ve specified the Conan version, operating system version and any tool that can be relevant.
• I’ve explained the steps to reproduce the error or the motivation/use case of the question/suggestion.

[paulocoutinhox]

Hi,

Forgot, i create my own toolchain: https://github.com/ezored/conan-darwin-toolchain

We are using in our products without problems.

I put:

• bitcode
• arc
• visibility

Thanks.

[theodelrieu]

It seems the -fembed-bitcode-marker only places an empty bitcode at the end of the binary.

See this SO post for more detail.

I wonder how it is useful in any way then…