-
Notifications
You must be signed in to change notification settings - Fork 53
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
CI: add Xcode 15.1 #384
CI: add Xcode 15.1 #384
Conversation
It may be the same issue I was facing when building locally with
This is after I compiled when excluding the InterSense trackers. For that library, the same thing happens. Curiously, this works, and the library is found, in my case,
I have yet to find out how to fix this during compilation. Afterward, it can be fixed by Apologies if this is not the issue with |
2bf78d5
to
0dd3cce
Compare
It looks like it's indeed the same problem. I have added some debugging output and I'm getting very similar messages in https://github.com/SoundScapeRenderer/ssr/actions/runs/7302083802/job/19900033809:
Contrary to your report, it also doesn't work here:
This is the result of
I find it interesting that you said you get the error with It looks like the error isn't related to the library itself, but just to the first library that happens to be in the list. |
No, not in my case. When I include
|
I don't know. You can try experimenting with
Yeah. But the file is really old and there don't seem to be any more recent releases: https://www.intersense.com/dev-tools Maybe it simply doesn't work with newer versions, maybe we should disable it in CI? I have tried it without |
Yeah, I've seen those optional paths mentioned before. I have yet to try to fix it this way since setting paths would require an additional step after building. Ideally, we can find a solution by modifying the build process. I will keep investigating how to mitigate the issue. Hopefully, that will work for
I assume most people would be fine without the InterSense integration. However, it seems like a fix for the loading issue cannot be far since executing the binary from its parent directory does not cause the error and since it can be "easily" fixed with |
I diffed the CI
This probably hints at the issue we encounter later when not loading the library correctly? |
The loader seems to find the libraries if setting
Curiously, the segfault does not occur when omitting the GUI with To omit the segfault, the former Do you have any idea why this happens and how to investigate further? |
Nevermind, https://stackoverflow.com/questions/3146274/is-it-ok-to-use-dyld-library-path-on-mac-os-x-and-whats-the-dynamic-library-s explained well why To summarize, invoking However, setting The current solution fixes at least my local build environment. Since I'm still new to the build process, I'd rather wait for input from a more experienced macOS developer to help resolve the issue during build time. Do you have any ideas, anyone? |
I'm out of ideas. The changes in linking behavior with I tried this before I know that the supplied "names" for the libraries are not according to current conventions. However, versions before |
How should we proceed with this? I suggest simply disabling the Intersense tracker in CI for macOS. @HaHeho Do you still have problems with libmysofa? |
I agree with disabling the Intersense tracker. I have never seen any audio person using other than ourselves. And the last time that we used it was probably around the year 2011. |
Yes, that is a good compromise. Merging this is fine ...
... however, the problem of specific libraries (like Removing the Intersense integration for I suspect the issue may arise if any dependencies are built locally with |
This is stacked on top of #383.