Thanks Erich, that's sort of what I had in mind, but it looks like that setting to build all configurations applies to all the project configurations in the project scope. The top level project has many configurations, but one of its configurations needs this lib compiled with a different option. I think I have a workaround; the different lib build generates a different name for the lib, so the project that needs that specific lib configuration looks only for that name. If the whole project is built and that lib doesn't exist, it will fail and you'll just have to switch the lib to the alternate configuration.