Multiple versions of the same subproject required for different build targets in the same project

[georgev93]

BLUF: I need different versions of a subproject in the same meson project. Those different versions do not get linked together.

I am working on an embedded C project that has many subprojects (drivers for various ICs, CODECs, peripheral libraries, etc.). One of those subprojects is an I2C library, and I'm using a particular major version of that library. The output of the overall project is a *.hex that gets flashed to a microcontroller.

I would also like to add a bootloader to this project, which involves a separate *.hex file that gets flashed as the bootloader as well as a modified version of the application *.hex. This bootloader also depends on some of the same libraries as the application code, but I would like to use a different major version of the I2C subproject to create the bootloader *.hex file.

The subprojects are wrap-git files with different branches for different major versions, so I'm able to specify my major version with the "revision" option in the wrap-git file.

Is there some way that I can tell meson to build one of my executables with one version (branch) of a subproject, and another executable with another version?

As a bonus, I would like to enforce that some subprojects are a common version beween the application .hex and the bootloader .hex. Is there some way to both enforce a common subproject dependency and allow different versions of a different subproject dependency?

[xclaesse]

You can have foo-1.0.wrap with directory=foo-1.0 and foo-2.0.wrap with directory=foo-2.0. You can then use them as dependency('foo-1.0', fallback: ['foo-1.0', 'foo_dep']) and dependency('foo-2.0', fallback: ['foo-2.0', 'foo_dep']). So basically, add the version into the wrap, directory and dependency names.

[georgev93]

For some reason I thought the wrap file name needed to match the project name, but I see that I was mistaken. Your solution will work quite nicely. Thanks a bunch @xclaesse!