I'm currently writing a portfile for re-alpine. I have cctools installed, so
re-alpine's configure script picks up cctools' nm and ar, and its build process
calls cctools' ar and ranlib.
Is it advisable in this case to declare a build dependency (probably a
bin-style one) on cctools? I
That's not necessary unless you absolutely need *our* version of cctools.
On Feb 8, 2013, at 1:47 AM, Lawrence Velázquez lar...@macports.org wrote:
I'm currently writing a portfile for re-alpine. I have cctools installed, so
re-alpine's configure script picks up cctools' nm and ar, and its
On Feb 8, 2013, at 03:47, Lawrence Velázquez wrote:
I'm currently writing a portfile for re-alpine. I have cctools installed, so
re-alpine's configure script picks up cctools' nm and ar, and its build
process calls cctools' ar and ranlib.
Is it advisable in this case to declare a build
ar and ranlib and the like are utilities most ports use to compile, and
they're expected to be provided by Xcode's command line tools, so we don't
declare dependencies on them, just like we don't declare dependencies on gcc,
sed, awk, grep, gawk, etc. cctools happens to provide (newer
