-
Notifications
You must be signed in to change notification settings - Fork 72
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
Building for MacOS should encourage setting an SDK version #120
Comments
* #93 Create placeholder for hidapi win32-aarch64 * #93 Add POM version for local JNA issue 93 support * #93 Add POM version for JNA 5.7.0-SNAPSHOT * #93 Add local library reference for faster JNA turnaround * #93 Re-instate missing DLL and reference JNA-5.7.0-SNAPSHOT * Fix buld-hidapi.sh Closes #114 Make colors easier to read in the shell script * Add win32-aarch64 to dockcross * Fix JNA dependency * Fix unit test Wait 30s for testing as logs indicate * Add darwin-aarch64 to dockcross * Bump JNA to 5.8.0 * Switch darwin to new jna suffix Also adds some sanitization to the build-hidapi.sh * Quality of life improvements :) * Fix missing dollar sign * Remove problematic calls to "make clean" Closes #122 * Add hints for SDKROOT, MACOSX_DEPLOYMENT_TARGET Closes #120 Co-authored-by: Gary Rowe <[email protected]>
Is this still an issue? |
It was merged here ... However, I believe it's missing on the develop branch. |
@gary-rowe which branch is this on? Or did you decide not to add it? Here's an example of how this was done on another branch, but the code was never merged: Lines 330 to 334 in e40bdfe
|
Hi @tresf . Looks like it was missed with all the other changes to the |
@gary-rowe thanks for the attention to detail however I think there may be some overkill items, such as restarting Line 430 in 672f0a7
... in my experience, this was just fine by passing the arch flag to the build system. Line 337 in e40bdfe
I think this approach is cleaner and less confusing. |
HID4Java should be built using an older SDK, such as 10.9.
MacOS x86_64
MacOS aarch64
Configuring the environment must be done in two steps:
otool -l
The text was updated successfully, but these errors were encountered: