LiveCode Forums.

Mad as a hatter:

Having used the Metacard 2.3 engine the results of an attempted build seem to be identical: All this tells me is that the stuff about prebuilt engines may be nothing more than a red herring.

Hi Richmond,

I must confess I've been busy and not read the thread thoroughly since I last posted but from what I can gather, you've worked around the problem of the files generated with the prebuilt version of the Revolution engine (so shouldn't need to get a PPC version of it). The problem you are now having is trying to link against the pre-built libraries (libcrypto.a is from OpenSSL and libcurl.a is for URL support).

The easiest solution is to link against the system versions of those libraries rather than prebuilts - the changes to the Linux Makfiles needed to do this are present in my feature-rpi branch on GitHub.

Fraser

runrevfraser wrote: the changes to the Linux Make files needed to do this are present in my feature-rpi branch on GitHub.

OK: and how do I go about getting hold of those changes and rolling them into what I'm doing?

If you want to merge the RPi branch into your current branch:
Or if you just want to use the RPi branch in its clean state:
Merging may or may not work, depending on which branch you are currently on (and how extensive the changes you have made are). I think the feature-rpi branch is currently up-to-date with 6.5.2.

Right: I know where I'll be worshipping this Sunday: right in front of the MacMini.
Thanks, Fraser.

Fraser,

I thought I would take a keek at your code on my Intel Box first {also wonder about cherry-picking bits from it],
BUT, get this:
I'm obviously doing something wrong.

SO: I have just browsed over in merry Firefox to this:

https://github.com/runrevfraser/livecode

and will have a 'poke around' for the /livecode/prebuild/lib/ stuff

and, possibly, the "Revolution.lnx" file as well, even if only to
do every EFL teacher's favourite thing; a Compare and Contrast Exercise

Richmond-

You're not in the main livecode directory when you issue the "git remote add, etc" commands and that's why you're getting the error. There's no harm in cding to the livecode directory and then issuing those, or you can go to any directory, do a "git init" on the directory before the "git remote" stuff and you should be fine.

Here I am, at last:

I've restored the prebuilt 'Revolution.lnx' file that the git downloaded:

Just started a "MODE=release make development" build: going for coffee.

Neither better not worse:
Here's the Terminal guff:

I've gone down with some sort of bug; snuffles and a temperature, so will leave this alone until I get better.

Not putting too fine a point on things: BUT I am getting increasingly cheesed-off as am waiting on a promise which has failed to materialise.

My PPC MacMini is rotting next door with a PPC version of Lubuntu on it [for the sake of argument I could return it to Mac OS 10.4.11 and do something useful with it].

I specifically set that machine up to work on a PPC build, and am completely stymied.

A promise (of sorts) was made, which should have made that possible.