Duncan Ogilvie

If you manually create a `v1.2.3` tag from the command line the release will be the incorrect version and this breaks things.

Try what happens when you use cmkr without VS

1

- Clean vm - Install CLion (with Mingw) - Use cmkr Supposedly it explodes.

Add offline mode to `cmkr.cmake`

2

Add an option to use `cmkr.exe` from the repository: ```cmake set(CMKR_PREBUILT_PATH "${CMAKE_PROJECT_SOURCE_DIR}") ``` This should use `${CMAKE_PROJECT_SOURCE_DIR}/cmkr.exe` instead of cloning from git. If the prebuilt is not found it should...

Should perhaps be: > Unknown key 'compile-feature', did you mean 'compile-features'

 This could be handled better by redirecting the cmkr stdout and printing with `message(FATAL_ERROR ...)`. Perhaps CLion also recognizes a syntax to link to the `cmake.toml` file?

```toml # Reference: https://build-cpp.github.io/cmkr/cmake-toml [project] name = "ConsoleApplication1" # TODO: define a target for each of your executables/libraries like this: #[target.myexecutable] #type = "executable" # static, shared #sources = ["src/ConsoleApplication1/*.cpp",...

Before calling `source_group` make sure that the files are actually in a subfolder of the repository.

License clarification

1

It looks like the files [upstream](https://github.com/winsiderss/systeminformer/tree/master/phnt/include) are already licensed under MIT. Would it be possible to change the license here as well to match?

Missing function `ZwWow64IsProcessorFeaturePresent` (WOW64-only)

6

According to my research: ``` NTSYSCALLAPI BOOLEAN NTAPI ZwWow64IsProcessorFeaturePresent( _In_ ULONG ProcessorFeature ); ```

There were a bunch of errors related to [`PyFrameObject`](https://docs.python.org/3/c-api/frame.html#c.PyFrameObject). Nothing was changed about the code itself.