Skip to content
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

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

macOS build: libtool APPLE vs GNU #228

wants to merge 4 commits into from

Conversation

albestro
Copy link

I was building on macOS via spack, which builds from source GNU libtool so it is not what the Makefile was expecting (APPLE libtool, which has a different user interface and set of options).

I don't have experience with libtool and even less about the differences between libtool 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 the case darwin section.

@jgaeddert
Copy link
Owner

I wonder if the check for which libtool is being used would be better put in configure.ac. This is typically where those checks go so that the makefile doesn't have any conditionals. I realize that autoconf is pretty gross and that most people prefer CMake these days, but when using auto tools it probably makes more sense to put that check in configure.ac

@albestro
Copy link
Author

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.

@jgaeddert
Copy link
Owner

I mean, we all just fumble our way through m4 macros don't we? 😬

@albestro
Copy link
Author

As I said, no experience at all on this side. If you have any specific hint, please tell me.

@jgaeddert
Copy link
Owner

I think I have some time this weekend to look into it!

@pfeatherstone
Copy link

I'm getting some issues with libtool on MAC i think. It's not creating a static library, just libliquid.ar and I think there's some issues with libliquid.dylib. For some reason, the linker will link to it. But at runtime, it's looking for libliquid.dylib locally, not system-wide. Odd. I don't know much about MAC, but i think this has something to do with libtool.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants