Replies: 3 comments 3 replies
-
I think main problem is that you don't have setup WATCOM and PATH environment variables properly for you OW installation (must be configured for current host system). |
Beta Was this translation helpful? Give feedback.
-
I added OW tools usage with VSCode to the Wiki. Does anyone have any ideas on what needs to happen to eliminate the need to force the cmake generator to Watcom WMake in the workspace settings.json? {
"cmake.configureArgs": [
"-DCMAKE_CXX_COMPILER_WORKS=1",
"-DCMAKE_C_COMPILER_WORKS=1"
],
"cmake.generator": "Watcom WMake", // <-- FORCED Comment this if you aren't using OpenWatcom compiler.
"C_Cpp.default.configurationProvider": "ms-vscode.cmake-tools",
} |
Beta Was this translation helpful? Give feedback.
-
Hi there, I work on the CMake Tools extension and this was brought to our attention yesterday. Pre-release version 1.11.10 fixes the bug with |
Beta Was this translation helpful? Give feedback.
-
Since i'm working for a 32-bit DOS project, i wanted to work with VSCode which is my favorite IDE (Next to Qt Creator and KDevelop) to develop C/C++, but seems like the CMake Tools extension doesn't handle well the OpenWatcom toolchain despite CMake supports it, so i thought a custom Kit entry for workspace level it would work:
(Update the C/CXX entries with your installation path
Despite all environment variables needed for OpenWatcom are set, VSCode extension reports: "Unable to determine what CMake generator to use" everytime you try to configure using the user kit, until now:
in your workspace
.vscode/settings.json
forcing the setting:"cmake.generator": "Watcom WMake"
does the trick but if you got that error before, you may need to restart VSCode to make it work, or the "CMake: Reset CMake Tools Extension State" option.Not sure if there's a suggest how to improve it, for me this is mostly a hack
Beta Was this translation helpful? Give feedback.
All reactions