LiveCode Forums.

Well, I've finally got it working, with a properly built multi-stack deployment. Three stacks, not two, for some reason: one .livecode, one .rev, one with no suffix. Thanks for all the help. Adding some diagnostic 'answer the result' calls did help narrow things down. In case anyone is interested, I...

To save a stack, somewhere in your code you have something like this: save stack "StackName" My app has been correctly saving changes for many months. It stopped doing so when rebuilt for Linux. Whatever is at issue here, it is not my code. I've expressed no opinion about your code. All I suggested...

FourthWorld wrote:To save a stack, somewhere in your code you have something like this:

Code: Select all

save stack "StackName"

My app has been correctly saving changes for many months. It stopped doing so when rebuilt for Linux. Whatever is at issue here, it is not my code.

With my last two questions unanswered it remains unknown if he can still build as he wants on Windows, or what he's getting when he checks "the result" after attempting "save". That information would seem useful to understanding what's happening. There has never been any issue with building or runn...

Here's the actual deployed Windows app, with about 500 books added, in an xz-compressed tar archive:

http://hudson-it.ddns.net/wlml-msw.txz

It's just under 1MB.

At this point I'm getting very close to abandoning LiveCode and trying some other method. No executable made with any language can modify itself. This is a function of the OS itself, consistent across pretty much all modern OSes. You could write your app in Assembler but you still won't be able to ...

Wally- what version of LiveCode are you using to cross-compile the linux binaries? If you're not using a 7.x series then you'll only be generating 32-bit binaries (not that this should have any bearing on the monolithic structure you're seeing). I just created a linux binary from OSX and it seems t...

(It's Phil, not Wally) I've just regenerated the app in both 64- and 32-bit versions for Linux using the original known-good Windows deployed version. Both now create a similar-looking directory tree, with one .livecode and one .rev stack, but *BOTH* fail to persist new cards when run. This is *real...

So for now I'll say the SB settings is how we handle this "currently", and optimistically leave the door open to exploring possible options for the future that make things even clearer. I appreciate your further exposition of the issues around the standalone builder. I'll try to get well-enough inf...

Presumably ??? You are the son of Derek Hudson who my father says used to work in a bank in Botswana. Yes. If you want you can send me your source stack via email or via dropBox and I can try building you a 64 bit Linux standalone on Ubuntu 32 bit, as well as a 32 bit one, and fiddle around with it...

It's all there in the preceding posts. Forget HyperCard; I mentioned it to give a sense of the visual style and index-card metaphor I recalled from HC. That's where the HC influence ends. I only mentioned it so old HC hands would have a clear image of what I had developed (in LiveCode, 100%, start t...

I really wonder why you decided to use a 64 bit version You credit me with too much consideration of the matter. If there was any thinking that went into it at all, it went: "64-bit machine, 64-bit distro, 64-bit libs installed by default, um, 64-bit then." Thanks for your dad's contact number. I'l...

If you live in Wincanton, Somerset you might think of going round to see Donald Mathewson in Church street . . . He has both a laptop that runs Xubuntu and a son who works with both Linux and Livecode :) What? Here in the boondocks? Great news! Thanks. Maybe it's time to start a LLUG. Think I'll tr...

Do on Linux what works on Windows and it'll work on Linux. ... Currently we express our build intentions with the settings in the Standalone Builder. I take the reproof. I thought I had done exactly the same, but I guess I must have toggled something. Now I just have to locate what it was. Thanks a...

since no modern OS allows an executable to save to itself, how does your Windows version work? The listings above show that in the Windows deployment there was indeed an external data stack. I think I may have uncovered a bug in the app builder. It should not be possible even accidentally to build ...