Updating repository to follow calng-format-wheel

[CalebFuster]

Updated repository to follow ssciwr/clang-format-wheel to ease maintenance.

Update include:

Moving from legacy setup.py to pyproject.toml
    Removing Manifest
CMakeList update to follow updates on clang-format-wheel
    Renaming clang-tidy_version.cmake to clang-tidy_version.txt
        Changing version to vX.X.X.X

[CalebFuster]

The PR is unfinished as GitHub action requires some changes, but there are some minor doubts about the code as it is.

Header files added to the wheel.

Why are they necessary for the wheel? Probably I'm overseeing something there.

install(
  DIRECTORY
    ${CMAKE_BINARY_DIR}/llvm/lib/clang/${CLANG_TIDY_VERSION_MAJOR}/include
  DESTINATION clang_tidy/data/lib/clang/${CLANG_TIDY_VERSION_MAJOR}
)

Visual Studio

I don't use VS, but I assume this is useful here for whom uses it.

set(config-subfolder "")
if(CMAKE_GENERATOR MATCHES "Visual Studio")
  set(config-subfolder "Release")
endif()
set(clang-tidy-executable ${CMAKE_BINARY_DIR}/llvm/${config-subfolder}/bin/clang-tidy${CMAKE_EXECUTABLE_SUFFIX})

[CalebFuster]

About GitHub action for release. I have some experience, but I prefer to ask

Minor improvements

OS runners

Clang-format-wheel uses Ubuntu:latest but not latest versions for macOS and windows. I would suggest (at least for this repo) moving all them to use latest, so deprecation OS runners don't affect. MacOS-12 is part of the workflows of this repo, and it's deprecated Issue. However, as you compile for Intel and Arm64 macOS, it will require maintenance sooner rather than later.

Automatic workflow updates with dependent bot.

There are a couple of PR from dependent bot #84 #85 #86. I can modify them manually in the PR, or you merge them and I pull them.

Excluded OS compilations

Some of the combinations are commented, but we can use the strategy of clang-format-wheel repo. Additionally, modify the default answer to the simulation to false, so we skip them by default.

About this PR

This part will take some time to be finished as there are a lot of small changes to test, running act with this workflow release leads to BSOD (expected as there are like 6 different targets to compile). I can add any of the previous modifications if you find them useful. Once the PR is merged, I would do a final test with a release of 19.1.6 for example.

[renefritze]

Looking good so far @CalebFuster, thanks!
I wasn't even aware the clang-format wheel moved on to scikit-build-core :)

Why are they necessary for the wheel?

Don't remember. If you're keen to know, have you looked at the git blame of the file? Maybe the adding commit has some notes.

OS runners

Agree on moving to what is currently latest. I just generally try to avoid using the X-latest tag

Automatic workflow updates with dependent bot.

I was hesitant to merge #86 since that potential for needing changes in the workflow.

Same with #76, this has a very low compat score.

So it would be great if you can trial those changes in your fork.

Excluded OS compilations
Some of the combinations are commented, but we can use the strategy of clang-format-wheel repo.

Not quite sure what you're saying here. Do you want to try to re-enable some currently commented combinations?

[CalebFuster]

Don't remember. If you're keen to know, have you looked at the git blame of the file? Maybe the adding commit has some notes.

I found the reason the headers are need for some of the checks.

Do you want to try to re-enable some currently commented combinations?

I wanted to remove the comment on the qemu combinadtion and run them conditionally as (clang-format workflow). However, the workflow was not conditional and it triggered all the combinations.

About dependant bot, qemu is not use anyway so we can remove it in the meantime. About pypi upload, I will try tomorrow to test it against test pypi, but quite confident on it.

[CalebFuster]

I removed the qemu with the commented combination