File structure on Linux

[richmond62]

While the Macintosh LC/OXT apps are 'simple' directories disguised as monolithic files, with EVERYTHING needed to run
inside them, the Linux LC/OXT apps are not like that at all.

I should be most grateful if someone can direct me as to find components I can locate quite easily on Mac in a Linux install
of LC / OXT.

[tergolap]

While the Macintosh LC/OXT apps are 'simple' directories disguised as monolithic files, with EVERYTHING needed to run
inside them, the Linux LC/OXT apps are not like that at all.

In fact, this is not quite true. However, due to Apple's restrictive strategy, all the libraries are in a distinct place so that you don't have to deal with them. Furthermore, components (like kernel, network libs, GUI ...) are prebuilt and provided by Apple. So your application expects exactly one network library in one location.

Linux is quite different here. Basically, you could set up a minimal command line Linux with a few megabytes of size. Then it's up to you, which additional technologies you use and from which open-source project you take the components. So you have different libraries (= different name of the library or binary) and they even-wider can live in different places, depending on the Linux distribution you use.
This can be confusing and one might end up in a so-called "dependency hell".

I should be most grateful if someone can direct me as to find components, I can locate easily on Mac in a Linux install
of LC / OXT.

What OXT expects on a Linux machine is key here.
On one hand, we have the installation of OXT itself. As it's an AppImage, all libs and dependencies (gfx, read-mes, basic configs) should live inside this.
For you program: If you e. g. know that for the GUI OXT uses GTK 3.x, then you know which libs are included with GTK 3.x and depending on your distribution (e. g. Ubuntu, Debian, Arch, Red Hat ...) you know where they are located.
Debian has a good documentation and AFAIR, years ago it hat a good description of which directories exist and what file-structure it expects.

Which of the components you look for?

[richmond62]

Mark Waddingham, bless him, posted this "over there":

"In the message box try:

Code: Select all

put the filename of stack "com.livecode.library.drawing"

"

which seems relatively straightforward.