-
Notifications
You must be signed in to change notification settings - Fork 447
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
macOS build: libtool APPLE vs GNU #228
base: master
Are you sure you want to change the base?
Conversation
I wonder if the check for which libtool is being used would be better put in |
Thank you for the comment, it's a good point. Unfortunately I'm proficient with CMake, but absolutely no experience with m4 and autotools...however, I tried to do what you suggested. Looking forward for your feedback/comment. |
I mean, we all just fumble our way through m4 macros don't we? 😬 |
As I said, no experience at all on this side. If you have any specific hint, please tell me. |
I think I have some time this weekend to look into it! |
I'm getting some issues with libtool on MAC i think. It's not creating a static library, just |
I was building on macOS via spack, which builds from source GNU
libtool
so it is not what the Makefile was expecting (APPLElibtool
, which has a different user interface and set of options).I don't have experience with
libtool
and even less about the differences betweenlibtool
APPLE vs GNU, I just checked the man pages and the documentation, and I came up with the two variants.This would open to build on OSX using any
libtool
built from source on macOS.Looking online it seems that also MacPort/Homebrew can provide the GNU
libtool
, but they install it with a different name (i.e.glibtool
). For the moment this use case is not addressed, but if in the future there will be the need, it will be enough to manage the selection of the correct${LIBTOOL}
name in thecase darwin
section.