New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meson support #410
Meson support #410
Conversation
As a wrapepr over CMake.
# Conflicts: # .github/workflows/builds.yml
From IRC:
I would add WrapDB support if possible. Something like
|
Samples please. I've tried standalone builds and a subproject dependencies - all compiles and runs just fine.
Please elaborate.
Ultimately you need to specify sources + compilation flags + link flags per-platform. And if those are going to change - meson will be another full-scale build system which needs to be supported/updated, and that's not something I'm looking forward to. CMake is introduced for HIDAPI as a long-term replacement for autotools+MSVC build scripts, which (CMake) provides all the same functionality as autotools and a bit more (e.g. convenience for CMake users). Having full-scale Meson build system for HIDAPI only for Meson users - not something I vote for. If that is ultimately not accepted by Meson users/community - someone needs to volunteer and support a separate build system. Possibly as it is done by cython-hidapi or node-hid - in a separate repository. |
The sandbox violation was before ceb5e43 . Now all files are copied. |
That I don't like either... |
wrapdb now has a libusb wrap. might as well use it here. |
No idea about meson. But the branch does not seem to work.
|
Are you sure this is the latest commit of the branch? |
Maybe the build directory has to be outside of the sourse tree? E.g.: |
That is it. Thanks.
|
@Youw |
There is no way right now. |
I see. Test of latest version under MSYS2 mingw64.
|
As a wrapepr over CMake.
Still experimental support and definitely not a primary build system.