[question] How to create tool package serving both build and runtime dependencies?

[schwaerz]

What is your question?

We are creating a 'build tools' - like package which will have dependencies to some cross-compiler (i.e. gcc) as well as some include headers and libraries to be used for the cross-compile targets.

You could probably compare to simply depending on a cross-compile gcc toolchain, where pre-built host libraries would be included.

We are wondering what would be the recommended approach?

• Should we create two packages and let the conanfile.pys have a build & runtime/host dependency, as we need to specify the build profile for the build tools and the host profile to choose the correct include headers, libraries, ... ?
• Or is there a way to package everything in the same package (we'd prefer that). However we'd not know how to deal with the build vs host profiles?
• Currently we are not re-packaging everything. But maybe we should?
• Maybe our approach is wrong in the first place?

Have you read the CONTRIBUTING guide?

• [x] I've read the CONTRIBUTING guide