-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Closed
Milestone
Description
Describe the bug
I use deployer to generate everything necessary for conan-less builds on other machines.
It seems that MSBuildDeps generates props with absolute paths.
Here is what conan_libjpeg_vars_release_x64.props look like for me:
<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup Label="ConanVariables">
<ConanlibjpegRootFolder>D:/StevePrograms/temp3/build/full_deploy/host/libjpeg/9f/Release/x86_64</ConanlibjpegRootFolder>
<ConanlibjpegBinaryDirectories></ConanlibjpegBinaryDirectories>
<ConanlibjpegCompilerFlags></ConanlibjpegCompilerFlags>
<ConanlibjpegLinkerFlags></ConanlibjpegLinkerFlags>
<ConanlibjpegPreprocessorDefinitions>LIBJPEG_STATIC;</ConanlibjpegPreprocessorDefinitions>
<ConanlibjpegIncludeDirectories>$(ConanlibjpegRootFolder)/include;</ConanlibjpegIncludeDirectories>
<ConanlibjpegResourceDirectories>$(ConanlibjpegRootFolder)/res;</ConanlibjpegResourceDirectories>
<ConanlibjpegLibraryDirectories>$(ConanlibjpegRootFolder)/lib;</ConanlibjpegLibraryDirectories>
<ConanlibjpegLibraries>libjpeg.lib;</ConanlibjpegLibraries>
<ConanlibjpegSystemLibs></ConanlibjpegSystemLibs>
</PropertyGroup>
</Project>CMakeDeps generates correct path relative to ${CMAKE_CURRENT_LIST_DIR}.
By the way, if I manually make path relative to $(MSBuildThisFileDirectory), then Visual Studio finds the file properly.
I use conan version is 2.3.1.
How to reproduce it
Create conanfile.txt with MSBuildDeps generator, then execute:
conan install . -of build -s build_type=Release -d full_deploy
Inspect props files in build folder.
Metadata
Metadata
Assignees
Labels
No labels