Building a standalone warns about duplicate stacks

Devin Asay devin_asay at
Thu May 7 11:44:34 EDT 2020


I’ve seen this when building standalones with stacks that are using library stacks, and the same library stackflles are included in the standalone build. Apparently the included stacks are opened during the build process, thus colliding with the library stacks already in memory. If this is the problem, I suppose a workaround would be to stop using the library stacks before running the build process.

Hope this helps.


> On May 6, 2020, at 6:07 PM, J. Landman Gay via use-livecode <use-livecode at> wrote:
> When building a standalone (for mobile in this case) I'm getting repeated messages about stacks already being in memory and asking me what to do with them. Since I have a lot of included stacks I need to make a decision a dozen times. This is different from all the "open*" messages, so that workaround won't help.
> It doesn't happen when I use the Test button to install directly to my phone. I think this is new behavior. Bug?
> -- 
> Jacqueline Landman Gay         |     jacque at
> HyperActive Software           |
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

Devin Asay
Office of Digital Humanities
Brigham Young University

More information about the use-livecode mailing list