Help with Bug #19550: Add support for symlinks to standalone builder

Trevor DeVore lists at mangomultimedia.com
Fri Jul 20 10:57:49 EDT 2018


Hi everyone,

I’m writing this email to see if there is someone who can pitch in and
implement a fix for bug 19550 [1]. The issue is that the the copy folder
command that the LC standalone builder uses does not support symlinks.
While this hasn’t been a significant problem in the past, it has now become
one because LiveCode Builder (LCB) code can link to .frameworks on macOS
using the Foreign Function Interface (FFI) feature in LiveCode 9.

As an example, I’ve been working on an LCB wrapper around Sparkle [2] and
on another around MASShortcut [3]. In both cases the .framework needs to be
distributed with the LCB library. The Standalone Builder does not create a
proper copy of the .framework and the code will fail in a standalone.

Here is a link to the source code on GitHub that needs to be updated:

https://github.com/livecode/livecode/blob/e6955bb9dc517ba4c5c2da422deb5e16627ebf1f/ide-support/revsblibrary.livecodescript#L215

If someone is able to step in and modify the existing code to support
symlinks then others would be able to start distributing extensions that
use .frameworks on macOS. I haven’t verified whether or not this affects
iOS but it may.

[1] https://quality.livecode.com/show_bug.cgi?id=19550
[2] https://github.com/trevordevore/lc-sparkle
[3] https://github.com/trevordevore/lc-masshortcut

-- 
Trevor DeVore
ScreenSteps
www.screensteps.com



More information about the Use-livecode mailing list