Profile include statement

I would like to make it possible to include one profile in the other. There is several reasons for this:

1. linux-x86_64 and linux-x86 could share several CFLAGS and it would be unnecessary with a lot of code duplication there
2. With the suggested #1141 it would be hugely beneficial to be able to include the whole part that handles buildtools and centralize that into one file

I think a simple pre-processor include before parsing the file is the simplest and most straight-forward way. Another possible solution would be able to use some kind of templating in the profiles and then have config file where you specify the keys.

The second one is more powerful for sure it could do something like this:

include(BuildTools)
[settings]
compiler={build_tools_compiler}

[env]
CC={build_tools_compiler_path}
CFLAGS={common_cflags} -DFOO

but I am not picky 😃

[memsharded]

Agree. Most likely we should move forward this feature request to 0.23, and wait until the new [build_requires] are released, tested and get more feedback about usage. Being mostly UX rather than functional, no big issue to postpone it.

[lasote]

What I’ve been doing with settings it to declare a general profile with the common settings and then use -s for the variations. In the Android Studio use case with a loop of architectures and a declared api_level has been more than enough so, for me, it’s not needed yet. Any other experience is welcome.