xTIMEComposer / build tools with Mac OS Catalina (10.15)

Technical questions regarding the XTC tools and programming with XMOS.
Post Reply
sparky
New User
Posts: 3
Joined: Mon Nov 11, 2019 1:07 am

xTIMEComposer / build tools with Mac OS Catalina (10.15)

Post by sparky »

Hi,

It looks like the latest tooling no longer works on Mac OS Catalina since 32-bit apps are no longer supported as well as legacy Java SE 6 support being dropped.

I don't really care personally about xTIMEComposer, but at least the binary build tools.

Has anyone figured out how to make it work? Is there are 64-bit version or a workaround available anywhere?


Redeye
XCore Addict
Posts: 131
Joined: Wed Aug 03, 2011 9:13 am

Post by Redeye »

I've run into exactly the same issue. I have got around it, but it is a fairly major PITA.

You can install the legacy Java runtime with a bit of hacking based on the info in this thread :

https://forums.macrumors.com/threads/ja ... a.2195954/

That'll get it "running" but you'll have several dozen modules/DLLs used by xTimeComposer which will bring up security dialogs, then you'll need to give permission in System Preferences->Security. Eventually, it does run without any security warnings. You might actually be best off running xTimeComposer as I'm not sure if the security dialogs will appear if you run from the command line.

The other thing you might need to know is that if you use xflash and have problems is that you'll probably need to disable SIP (this was true for older versions of the tools, not sure if it's still a problem).

Hopefully XMOS will sort this out in the very near future - both the 64-bit and signed binary requirements for macOS have been known about for at least 2 years so it's not exactly a surprise.
sparky
New User
Posts: 3
Joined: Mon Nov 11, 2019 1:07 am

Post by sparky »

Thanks for the reply and the tip about installing legacy Java.

Yes my original comment about 32/64bit was wrong, it's a question of gatekeeper (and maybe SIP but I haven't run into that yet). In Catalina it no longer tells you to go into "System Preferences->Security" when running from CLI which threw me off.

You can also add the security exceptions to gatekeeper (for the most part) from the CLI using "spctl". See theses links or "man spctl"
http://osxdaily.com/2015/07/15/add-remo ... -mac-os-x/
https://www.cnet.com/news/how-to-manage ... mand-line/

The tools now seem to run although I haven't actually had a chance to test with a board yet
sparky
New User
Posts: 3
Joined: Mon Nov 11, 2019 1:07 am

Post by sparky »

In addition it looks like you can use `spctl developer-mode enable-terminal` + enable the terminal in "System Preferences->Security & Privacy->Privacy->Developer Tools" to allow the terminal to run any dev tools.
Post Reply