[Coco] Anyone built toolshed for macOS X lately?

[Allen Huffman]

> On Feb 19, 2025, at 9:27 PM, David Ladd via Coco <coco at maltedmedia.com> wrote:
> 
> From the old repo, did you make sure to do a clean before you updated from
> the hg pull?
> 
> make -C build/unix clean
> make -C build/unix
> 
> Some times make misses changes and it could be trying to link from old
> builds or possibly changes from X-Code.
> 
> It is always best to make sure you do a make clean before ever updating
> files from the repo so lingering built files don't cause conflicts.

I did not — I did not have that in my build notes from the times I’ve done this in the past. I’ll add that note for “next time.” I’m sure I’ll run into this again down the line ;-)

NitrOS9 still can’t be built if you are on a system that has a space anywhere in the path. This can be the default on any new Windows machine if the user accepts defaults and it places files on OneDrive. You can at least make usernames and such to get a OneDrive path without spaces.

But on macOS, putting something on iCloud (which looks like a top level user directory) ends up being in a path like this:

/Users/allenh/Library/Mobile Documents/com~apple~CloudDocs/Others/CoCo

That space in “Mobile Documents” breaks stuff.

I mean, I know we are using something that is an offspring of 1970s Unix on modern Linux or Mac systems, but I am still stunned in 2025 we have software that cannot handle a space in a directory name ;-)

At least it works with files that have names longer than 8 characters ;-)

--
Allen Huffman - PO Box 7634 - Urbandale IA 50323 - 515-999-0227 (vmail/TXT only)
http://www.subethasoftware.com - https://www.facebook.com/subethasoftware