You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
doesn't seem to work for me in either of the conan build or conan create cases.
Here's the error for conan build:
C:\dev\src\nx\platform\build>conan build ..
[...]
----Running------
> call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC/vcvarsall.bat" amd64 && msbuild "C:\dev\src\nx\platform\Platform.sln" /p:Configuration="Debug" /p:UseEnv=true /p:Platform="x64" /m:8 /p:PlatformToolset="v140" /verbosity:normal /p:ForceImportBeforeCppTargets="C:\dev\src\nx\platform\build\conan_build.props;C:\dev\src\nx\platform\build\conanbuildinfo.props"
-----------------
Microsoft (R) Build Engine version 14.0.25420.1
[...]
20>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Current.targets(14,11): error MSB4115: The "exists" function only accepts a scalar value, but its argument "$(ForceImportBeforeCppTargets)" evaluates to "C:\dev\src\nx\platform\build\conan_build.props;C:\dev\src\nx\platform\build\conanbuildinfo.props" which is not a scalar value. [C:\dev\src\nx\platform\SolutionPlatformCommonTasks\SolutionPlatformCommonTasks.vcxproj]
and here's the error for conan create:
C:\dev\src\nx\platform>conan create . PORT/stable
[...]
----Running------
> call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC/vcvarsall.bat" amd64 && msbuild "C:\dev\conan\platform\0.0.1\PORT\stable\build\0b258a3cc8a011fb233dfdd231934614cdc10438\Platform.sln" /p:Configuration="Debug" /p:UseEnv=true /p:Platform="x64" /m:8 /p:PlatformToolset="v140" /verbosity:normal /p:ForceImportBeforeCppTargets="C:\dev\conan\platform\0.0.1\PORT\stable\build\0b258a3cc8a011fb233dfdd231934614cdc10438\conan_build.props;C:\dev\conan\platform\0.0.1\PORT\stable\build\0b258a3cc8a011fb233dfdd231934614cdc10438\conanbuildinfo.props"
-----------------
Microsoft (R) Build Engine version 14.0.25420.1
[...]
20>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Current.targets(14,11): error MSB4115: The "exists" function only accepts a scalar value, but its argument "$(ForceImportBeforeCppTargets)" evaluates to "C:\dev\conan\platform\0.0.1\PORT\stable\build\0b258a3cc8a011fb233dfdd231934614cdc10438\conan_build.props;C:\dev\conan\platform\0.0.1\PORT\stable\build\0b258a3cc8a011fb233dfdd231934614cdc10438\conanbuildinfo.props" which is not a scalar value. [C:\dev\conan\platform\0.0.1\PORT\stable\build\0b258a3cc8a011fb233dfdd231934614cdc10438\SolutionPlatformCommonTasks\SolutionPlatformCommonTasks.vcxproj]
In both cases I can confirm it's setting the right directory for conanbuildinfo.props, but doesn't seem to like a semi-colon separated list of items for $(ForceImportBeforeCppTargets). Maybe a vs2015 issue?
( Note: I understand from discussion in #7805 (comment) that it's probably suboptimal to try to inject conanbuildinfo.props this way, but nevertheless I wouldn't have expected this error, which would also impede setting any other .props file )
Logs (Executed commands with output) (Include/Attach if Applicable)
The text was updated successfully, but these errors were encountered:
The behavior is tested in user_properties_multifile_test test, with a full integration test, which is run in VS2017, so it totally seems that it is VS2015.
Do you know if VS2015 allows multiple ForceImportBeforeCppTargets properties in the command line, instead of a single one with multiple values separated by ";"?
Environment Details (include every applicable attribute)
Using
user_property_file_name
as follows in my conanfile.py:doesn't seem to work for me in either of the
conan build
orconan create
cases.Here's the error for
conan build
:and here's the error for
conan create
:In both cases I can confirm it's setting the right directory for
conanbuildinfo.props
, but doesn't seem to like a semi-colon separated list of items for$(ForceImportBeforeCppTargets)
. Maybe a vs2015 issue?( Note: I understand from discussion in #7805 (comment) that it's probably suboptimal to try to inject
conanbuildinfo.props
this way, but nevertheless I wouldn't have expected this error, which would also impede setting any other .props file )Logs (Executed commands with output) (Include/Attach if Applicable)
The text was updated successfully, but these errors were encountered: