(resending from correct address)
On Mar 13, 2022, at 16:34, Dave Horsfall wrote:
> Smooth as the proverbial baby's bottom on an oldish MacBook Pro, High
> Sierra 10.13.6; well done, all.
>
> I'm quite taken by the progress bar on "cmake"; it keeps changing its
> mind, just like a MacOS upgrade
Smooth as the proverbial baby's bottom on an oldish MacBook Pro, High
Sierra 10.13.6; well done, all.
I'm quite taken by the progress bar on "cmake"; it keeps changing its
mind, just like a MacOS upgrade does :-)
-- Dave
I forgot to ad, the reason, at a unix level, the Finder alias just just another
boring file, not the intended alias. This is similar to how Windows shortcuts
look on Macs, where they come through as a .lnk file that the Mac doesn’t
understand.
--
Richard Smith
xpl...@wak.co.nz
> On 14/03/2
Is it a Mac Alias, or a unix ln ? (i.e. the former is created with a
drag-n-drop of the App holding down the Command & Option keys, while the former
is created with the command ln -s /path/to/app lnfile, and that is a lowercase
L, not an uppercase i). MacPorts will work better with the latter ln
I do have the full Xcode package installed (8.2.1) on the El Capitan system,
although I have it as an alias in the Applications directory (on a smallish
SSD) linking to the actual Xcode files on an internal HD because it requires a
lot of disk real estate and I never use Xcode. Would that confu
Hello,
here is an older concept from 2016 I had written for gdb/lldb as Apple began to
require code-signing for debuggers. This applies to more actions by now, but
with the same requirements. The replies are also relevant and discuss
alternatives.
https://lists.macports.org/pipermail/macports-