On Sun, Apr 29, 2018 at 12:57:29PM +0100, Stuart Henderson wrote:
> On 2018/04/29 12:43, Landry Breuil wrote:
> > The rationale is to not explicitely adding libtool from ports (the gnu
> > one) unless its really needed, ie delete ports libtool, figure out if
> > the port is fine with the base libtool, and then set USE_LIBTOOL=yes
> > which will set LIBTOOL in the env during build. If you set it to 'gnu'
> > it will also add devel/libtool to the build depends.
>
> I know Landry already knows, but getting it into the thread:
Well i tend to forget the gory details so that's a nice reminder; thanks :)
> libtool's m4 files are often needed for autoconf/automake regeneration,
> in that case (where gnu libtool itself isn't needed) then devel/libtool
> must be listed as a BUILD_DEPENDS.
>
> USE_LIBTOOL=gnu should not be used unless base libtool doesn't work
> with the port (and in that case it should come with agood explanation).
>
USE_LIBTOOL
Defaults to 'Yes'. Set to 'gnu' if the base libtool(1) is
insufficient and GNU libtool is required. Set to 'No' to disable
the use of libtool(1) entirely; this should not be set under
normal circumstances. Adds dependencies if necessary, and passes
LIBTOOL environment variable to scripts invocations.
Could be improved to mention the only reason to manually add libtool to
BDEP ?
No comments:
Post a Comment