including a library in a standalone

Mike Bonner bonnmike at gmail.com
Tue Jul 7 01:41:09 CEST 2015


The library stack is a substack of the mainstack I assume?  If so, make
sure you haven''t set things so that it breaks out substacks into separate
stackfiles.  (at which point its no longer monolithic) If the library stack
isn't a substack, you should make it so that it is.(in code, set the
mainstack of stack "librarystack" to "NameOfTheMainstack")

On Mon, Jul 6, 2015 at 5:14 PM, Dr. Hawkins <dochawk at gmail.com> wrote:

> I happily managed to get the library stack working for shared routines in
> pretty much a matter of minutes.
>
> I've got my routine to prepare for compile copying the library stack to the
> project stack.
>
> However, I assumed "library stack libStackName" would work in a standalone,
> but it creates errors error 91 and 568 (can't find stack).
>
> I very much do not want to have a stack hanging around to potentially have
> its routine's called, password protected or not; I want a monolithic app.
>
> Is inserting as a back script there way to go?  And if so, would I be
> better off doing the same in the IDE rather than as a library?
>
> --
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>


More information about the use-livecode mailing list