EINVALIDTAGNAME with custom CMake options
See original GitHub issueI am trying to give a custom CMake option using the npm command npm install -- --CDMyCustomLib_DIR:PATH=directory
{
"scripts": {
"install": "cmake-js compile"
},
...
}
I got this error:
npm ERR! code EINVALIDTAGNAME
npm ERR! Invalid tag name "--CDMyCustomLib_DIR:PATH=directory": Tags may not have any characters that encodeURIComponent encodes.
Any idea how to solve this? Thanks for your help!
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
CMake 3.25.1 Documentation
When CMake is first run in an empty build tree, it creates a CMakeCache.txt file and populates it with customizable settings for the...
Read more >How to set a CMake option() at command line - Stack Overflow
Delete the CMakeCache.txt file and try this: cmake -G %1 -DBUILD_SHARED_LIBS=ON -DBUILD_STATIC_LIBS=ON -DBUILD_TESTS=ON .. You have to enter all your ...
Read more >Customize CMake build settings in Visual Studio
To create a custom environment, choose the Edit JSON link in the upper right ... Specifies any more command-line options passed to CMake....
Read more >CMake | CLion Documentation - JetBrains
In this field, specify additional CMake options, separated by spaces. For example, here you can specify a custom CMake generator via -G ....
Read more >CMake — conan 1.43.4 documentation
Specifies a custom CMake generator to use, see also cmake-generators ... It indicates the generator, the Conan definitions and the flags converted from...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
As far I know yes, you should. But you can use environment variables or npm config values to configure you build process. https://github.com/cmake-js/cmake-js#npm-config-integration
Because on the time of development CMake was case insensitive. It would be a breaking change to address it. It might worth the effort and a semver major release, but you should open up an issue about it, when we can discuss more.