Getting saucy

Brian Milby brian at
Sun Sep 10 19:57:03 EDT 2017

I'll add that it did not take that much to get it up and running on Linux.
I had an Ubuntu 16.04 ISO already so I built a VM and updated everything.
I used the commands on the file to get all of the dev
software installed.  The only package missing was java... (sudo apt-get
install default-jdk).  Once I had cloned the repo I did the make commands
to config and compile.

On Sun, Sep 10, 2017 at 3:29 PM, Monte Goulding via use-livecode <
use-livecode at> wrote:

> > On 11 Sep 2017, at 12:54 am, Richmond Mathewson via use-livecode <
> use-livecode at> wrote:
> >
> > I did that sort of thing about 3-4 years ago in a rather feeble attempt
> to build a Livecode
> > version to run on Linux PPC . . .
> >
> > Most open source efforts supply a folder with the build files inside it
> rather
> > than forcing people down the slightly recherché route of git-hub.
> Hmm… most open source efforts? Would be interested in stats. My
> expectation would be most just use GitHub. Regardless I think we all have
> more helpful things to do rather than replicate GitHub functionality.
> Having said that it’s open source so anyone can feel free to maintain some
> other means of access to the source. It would be a hefty task because it’s
> constantly changing. You can download as a folder from GitHub I think
> although as Brian said our build tools run some git commands for various
> things.. probably only the current commit hash is required so you could
> work around that.
> If you are interested in building LiveCode from source then I’d suggest
> the simplest route is to follow our documented instructions that Brian
> pointed to. They include the few git commands required to get the source.
> Cheers
> Monte
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:

More information about the Use-livecode mailing list