On Tue, 15 Aug 2023, Jason Liu wrote:
Yes, you're right that clearing the build phase doesn't prove anything, but
I'm not sure I'm following your other point. Are you saying that "make
install" will compile the source code? I was under the impression that you
need to manually run "make" in
Yes, you're right that clearing the build phase doesn't prove anything, but
I'm not sure I'm following your other point. Are you saying that "make
install" will compile the source code? I was under the impression that you
need to manually run "make" in order to actually compile the source code,
On 16/8/2023 04:29, Jason Liu wrote:
Hi everyone,
I'm working on a Portfile that uses the xcode PortGroup, and I've
noticed something that surprised me: It seems that the MacPorts build is
compiling the source code during the build phase, and then compiling the
source code AGAIN during the
Hi everyone,
I'm working on a Portfile that uses the xcode PortGroup, and I've noticed
something that surprised me: It seems that the MacPorts build is compiling
the source code during the build phase, and then compiling the source code
AGAIN during the destroot phase? Is this correct, or am I
Hi,
Is there a way to get the path to MacPort's tclsh interpreter from within a
Portfile, other than by using a `glob` to find it in
$prefix/libexec/macports/bin ?
(not to do anything naughty, just to run a Tcl test/benchmark.)
Hi,
Thanks, eventually I figured that out for myself as well. I didn’t appreciate
that if a port indicated it didn’t support arm, the x86_64 would be installed
instead and used via rosetta etc. nice.
I have though already found a number of ports I use indicate they only support
x86_64 but