Hi everyone,
I’m deploying a LiveCode stack on multiple Linux distributions (Ubuntu, Debian, CentOS) and running into recurring issues:
File permission errors after packaging
Missing or mismatched shared libraries (.so)
Different behaviors across distros
Has anyone developed a reliable method or checklist for packaging and running LiveCode apps consistently across Linux systems?
Thanks in advance for your insights.
Issues Deploying LiveCode Stacks on Linux (File Permissions & Library Dependencies)
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
takeokismet
- Posts: 1
- Joined: Thu Nov 13, 2025 3:54 am
- Contact:
-
FourthWorld
- VIP Livecode Opensource Backer

- Posts: 10070
- Joined: Sat Apr 08, 2006 7:05 am
- Contact:
Re: Issues Deploying LiveCode Stacks on Linux (File Permissions & Library Dependencies)
The general guidance that a system configured to run a browser can usually run LC is often sufficient, but if you're running into specific errors on a system that has a working browser installed we'll need to see details to help with those.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
-
richmond62
- Livecode Opensource Backer

- Posts: 10248
- Joined: Fri Feb 19, 2010 10:17 am
Re: Issues Deploying LiveCode Stacks on Linux (File Permissions & Library Dependencies)
Are you deploying a LiveCode stack, or a standalone built for Linux?