Re: including a library in a standalone

2015-07-06 Thread J. Landman Gay
On 7/6/2015 6:14 PM, Dr. Hawkins wrote: 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? Unless something has changed since I last heard, the only difference between "start using" and "insert

Re: including a library in a standalone

2015-07-06 Thread Peter Haworth
I've only used the "start using" synonym for "library" but with it you have to include the word library so maybe library stack "dhLib" will work. On Mon, Jul 6, 2015 at 5:08 PM Dr. Hawkins wrote: > On Mon, Jul 6, 2015 at 4:41 PM, Mike Bonner wrote: > > > The library stack is a substack of the m

Re: including a library in a standalone

2015-07-06 Thread Dr. Hawkins
On Mon, Jul 6, 2015 at 4:41 PM, Mike Bonner wrote: > 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 substac

Re: including a library in a standalone

2015-07-06 Thread Mike Bonner
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 mainsta

including a library in a standalone

2015-07-06 Thread Dr. Hawkins
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 e