search

conan-io / conan-vs-extension

Conan Extension for Visual Studio
https://marketplace.visualstudio.com/items?itemName=conan-io.conan-vs-extension
MIT License
59 stars 34 forks source link

conanbuildinfo.props is not generated for the multi-project solution #175

Closed Tadeusz-Okuljar closed 8 months ago

Tadeusz-Okuljar commented 4 years ago

I use Visual Studio 2017 with the conan extension. Conan extension adds a path to conanbuildinfo.props in vcxproj file, for example:

`

`

conanbuildinfo.props by default is placed in the build directory because it shouldn't be committed to the repository. When an user clones a repository and opens a solution conanbuildinfo.props should be generated. For a single-project solution it works fine.

Unfortunately it doesn't work for a multi-project solution where only one project has defined conanfile.txt. That project can't be loaded because vcxproj has a path to the conanbuildinfo.props which is not generated for the multi-project solution.

Each project in the single-project solution and multi-project solution has defined the following Output Directory:

$(SolutionDir)build\$(PlatformShortName)-$(Configuration)\

and Intermediate Directory:

$(SolutionDir)build\$(PlatformShortName)-$(Configuration)\$(TargetName)\

Is it known issue ? Do you know any workaround ?

identify3d-joe commented 4 years ago

I am having this same issue. What would a possible work-around be?