> On Sep 20, 2015, at 8:36 AM, Thibaut Paumard wrote:
> Unless the project decides on one
> over the other,
https://guide.macports.org/chunked/porthier.html
"libexec/
System daemons and system utilities (executed by other programs)."
—
Daniel J. Luke
Le 19/09/2015 13:16, Andrew L. Moore a écrit :
> Guys,
> Macports appears to install qt5-mac, llvm-3.5 and llvm-3.7 wholesale under
> libexec. This is not a traditional destination. Is there a reason for
> choosing libexec over lib?
>
Hi,
In the Linux world, libexec is an optional directory i
Jeremy Huddleston Sequoia wrote:
>> Macports appears to install qt5-mac, llvm-3.5 and llvm-3.7 wholesale under
^^^^
Actually, that's a recent decision that ignored months of work I did on the Qt5
port; I used ${prefix}/libexec/qt
.
Where such a script should be installed?
Perhaps, share?
It would be great if the differences of libexec vs lib are sorted out.
Regards,
Takeshi
-
Takeshi Enomoto
take...@macports.org
___
macports-dev mailing list
macports-dev@lists.macosforge.org
Your question suggests you don’t really understand what lib and libexec are
for. They serve rather different purposes. There are plenty of resources on the
web explaining the difference.
> On 19 Sep 2015, at 5:16pm, Andrew L. Moore wrote:
>
> Guys,
> Macports appears to install qt5-mac, llvm-3
> On Sep 19, 2015, at 09:16, Andrew L. Moore wrote:
>
> Guys,
> Macports appears to install qt5-mac, llvm-3.5 and llvm-3.7 wholesale under
> libexec. This is not a traditional destination. Is there a reason for
> choosing libexec over lib?
lib isn't the right place either. It's not all libr
Guys,
Macports appears to install qt5-mac, llvm-3.5 and llvm-3.7 wholesale under
libexec. This is not a traditional destination. Is there a reason for choosing
libexec over lib?
smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev
