Closed SkyLeach closed 5 years ago
PR #13 however glibc configure scripts aren't being found.
Advice appreciated.
Have a look at https://github.com/libyal/libvmdk/wiki/Building#read-first
you're using a developer release not a distribution release.
I realize it's homebrew-centric, but since the vast majority of people who use Mac use homebrew and since it doesn't break any other builds (easy to tweak it to check for homebrew or take a flag) I would think it would be useful anyhow.
Not trying to be a pain, just thought it might be a bit less painful.
Don't get me wrong I appreciate the gesture. However there is a difference between development releases and distribution releases for a reason. Libvmdk is dependent on various other libraries of which their source and testing done as part of different (libyal) projects. This is less painful from the maintainer side (me).
There also can be various issues with the autotools on different platforms, hence I'm hesitant to have non-developers / non-maintainers directly use it and have to troubleshoot these issues. Distribution packages are designed to be self contained.
Also libvmdk-python distribution packages can be found on pypi (https://pypi.python.org/pypi/libvmdk-python/) if you really want it easy.
@joachimmetz 👍 bad habbit mine, testing modules from source before testing pypi
There are a couple of reasons for this. First, autopoint is required to update the macros for autotools before the configure script will be created. The only homebrew package available that has autopoint is gettext, and gettext conflicts with the apple-provided gittext so it doesn't get autolinked. (see: http://arielvb.readthedocs.io/en/latest/docs/mac/commandline.html#gettext)
I am workingn on a pull request for this and will update this issue with the pull request once I finish.