LiveCode Forums.

@monte: I was looking at my old Quartam JVM External project, created with the good old externalsenvironment3 for desktop externals.
When I opened it with the latest Xcode, it wasn't too happy and mangled my build settings.
So I was wondering if you had a magic recipe

Jan Schenkel.

Oh... I am so keeping my old XCode version unning as long as I can...

Okay - have spent some time on lcidlc and externals in general today. I've now got Windows, Mac and Linux working with the 'lcidlc' system for external generation. Still a little bit more to do, but there is now a revtestexternal in the livecode repo on my externals feature branch that compiles and runs on the Desktop platforms. Anyone who wants to poke around can find it here: https://github.com/runrevmark/livecode/ ... als_api_v5

On it.

Your message contains 6 characters. The minimum number of characters you need to enter is 10.

@mwieder: One word of warning - the derived files (EncodedSupport / EncodedJavaSupport) don't make properly on Linux so you might have to invoke those rules manually before lcidlc builds.

That's interesting.

I did a 'make development' after pulling your branch and it compiled with no problems. I haven't taken it farther yet. Did I miss something?

@mwieder: 'lcidlc' isn't tied into the global make script, nor is 'revtestexternal'... The fun starts when you try and build those

Great stuff! And thanks for merging in master... was having merge issues cherry picking last night and decided to watch game of thrones instead Hodor!

Hmm... it looks like this stuff isn't going to make 6.1 or is there a chance it can be squeezed in? Perhaps cherry-pick just the stuff to get notify playing with threads nicely? I have a project that really needs this in commercial asap.

@monte: It's okay - I hadn't forgotten I pulled out the changes for getting LCObjectPost working on desktop and have merged those into develop and release-6.1.0 (via the feature-desktop_ping_wait branch in runrev/livecode). So hopefully you should be good to go with LCObjectPost with 6.1.0.

whew... thanks!