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

Mike Kerner MikeKerner at
Fri Jul 20 17:41:54 CEST 2018

A couple of thoughts:
1) There might be cases where symlinks should not be traversed, so there
probably should be an option to traverse or not
2) There are probably going to be cases where the symlinks are recursive.
I think there should definitely be an option to resolve those.

On Fri, Jul 20, 2018 at 10:58 AM Trevor DeVore via use-livecode <
use-livecode at> wrote:

> 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:
> 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]
> [2]
> [3]
> --
> Trevor DeVore
> ScreenSteps
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."

More information about the use-livecode mailing list