-
Notifications
You must be signed in to change notification settings - Fork 48
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
GitHub Actions: Enable conda-forge CI on macOS #513
Conversation
Now we have a macOS failure on YARP:
|
The problem is a good example of the classical messy situation of complex dependencies in C/C++ software. What is happening is that |
Modern version of #504 . Now the gazebo build has been refreshed, so everything should work fine.
8db9a09
to
dee899f
Compare
Now running a sample code generator in YARP that requires ace is failing with:
|
The libuuid problem is solved, while now there is a problem in the ace binary, I opened an issue for it in conda-forge/ace-feedstock#11 . |
This was solved by conda-forge/ace-feedstock#12 . |
The macOS Conda build is finally working. There are a few CI failures that are unrelated. Indeed, they are spurious macOS/Homebrew failures that we could finally distinguish from actual macOS failures thanks to the conda macOS job! |
Thanks @Nicogene for the review. |
Modern version of #504 . Now the gazebo build has been refreshed, so everything should work fine.
For more details on what conda and conda-forge are, and why it useful to have a CI with them, please see #484 (comment) . For the specific case of macOS, having an build that is not using Homebrew should permit us to distinguish the quite frequent Homebrew failures from the actual macOS compilation problems (that should create a failure in both conda and Homebrew macOS jobs).