I'm running the LiveCode demo trying to decide if it will work for what I do. I've figured out how to create and call a Library stack, and when I create a Mac executable everything is put into the package like I want it to. However, on Windows my Library stack is separate from the .exe, which I don't want. Our end users are schools with countless people coming and going, and it's not good to rely on the app being in the same folder as anything else.
I suppose I could put the library in a substack, as some have suggested, but then how do I share it among projects? The documentation says very little about this.
Thanks, Mark
Single .exe File
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
Re: Single .exe File
Yes, you are going to want to make your library stack a substack of your mainstack. You'll be putting a copy of the library stack in there, so you'll still have the library stack available to attach to other projects as well.
Here's how I do this with library stacks for standalone apps:
Load the library stack into memory
Load the mainstack into memory
Using the property inspector, change the mainstack of the library stack to be the mainstack
Save the mainstack
Now the original library stack is still in a separate file on the disk, but a copy is attached as a substack of themainstack.
The drawback is that if you update the library stack you have to go through this process again to update the substack.
Here's how I do this with library stacks for standalone apps:
Load the library stack into memory
Load the mainstack into memory
Using the property inspector, change the mainstack of the library stack to be the mainstack
Save the mainstack
Now the original library stack is still in a separate file on the disk, but a copy is attached as a substack of themainstack.
The drawback is that if you update the library stack you have to go through this process again to update the substack.
-
- Posts: 3
- Joined: Thu Feb 16, 2012 5:07 pm
Re: Single .exe File
That's not the answer I was hoping for, but the answer I was half expecting. I suppose in time my library will be as stable as my C++ library, and won't change much. For now, I'll do it as you've suggested.
Thanks a lot,
Mark
Thanks a lot,
Mark