Skip to content

Conversation

@bmerkle
Copy link

@bmerkle bmerkle commented Oct 19, 2024

  • python>=3.9
  • cmake>=3.22
  • clang>=18 on windows use the msvc-clang (>=17)

fix #34

- python>=3.9
- cmake>=3.22
- clang>=18 on windows use the msvc-clang (>=17)

fix microsoft#34
@bmerkle
Copy link
Author

bmerkle commented Nov 6, 2024

@potassiummmm can you have a look at this?
IMO checking for prerequisites will avoid a lot of user bug reports 😉.

@bmerkle
Copy link
Author

bmerkle commented Nov 6, 2024

merge conflict resolved

@potassiummmm
Copy link
Collaborator

Thanks for your work! We are working on resolving toolchain dependencies, so the current version limitations may not be mandatory.

@bmerkle
Copy link
Author

bmerkle commented Nov 13, 2024

@potassiummmm I understand. However in our build environment / embedded area we usually check for tool names and also tool versions, so IMO we are on a safer side if we check it (at least the minimal required versions).
And the implementation is already there with this patch/PR :-)
What do you think ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Install/build process should check and assert the requirements (e.g. clang compiler versions)

2 participants