In the process I have learned lots of ways to configure that I was unaware of (thanks!), and the last of which would have been ideal except for the escaping problem. That may be because I provided my own layout or am not using editable packages at present. Which was the point of this highlighted that I could end up with problems not providing the eventual CMake generator information to Conan - although I presently don't appear to have a problem as the actual property value is irrelevant. My point was being technically correct using "NMake Makefiles" is broken on the IDE/plugin, while giving "anything" works because the actual property value is irrelevant to Conan because it is also broken in a different way as it needs something/anything to literally trick it into not setting a property that should not be set. While I can get it to work from the command line where I can control the quoting, as mentioned the IDE/Conan plugin is escaping and I don't have control over that. With -build missing -c :generator="NMake Makefiles"Ĭonan install C:/Users/drmacdon/Development/test -if=C:\Users\drmacdon\Development\test\cmake-build-debug -pr=default-debug-2019 -build missing -c :generator=\"NMake Makefiles\"Ĭonan install: error: unrecognized arguments: Makefiles" It is technically broken somewhere (IDE Conan plugin?) due to escaping logic. build # Want imports to go to present build as they used to build, "conan") # Expect to be relative to build location self. build = build_path # Required to build from arbitrary command line location self. This allows the VS Code Conan Plugin to # define it's JSON profiles like so, # "installArg": "-build missing -install-folder $". ![]() The build_type is left as-is instead of # dropping to lowercase because VS Code treats it as an environment variable when building # paths which would be impossible to match case. The best way to do this # is to anchor relative to this conanfile. Cmake_layout( self) # Something to start with in case I miss something # The default cmake_layout uses "." to identify the source location but when using VS Code # the "." is where VS Code was launch from which is problematic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |