Linux PPC build?

[mwieder]

Richmond- you've got missing directories because the submodules aren't present in the tarball. If you were using git instead of making extra headaches for yourself, this would be easy to fix. Since you don't want to do this the proper way, I can't think of how you are going to get around this other than iteravely tarballing each of the dependent submodules, unarchiving them into the proper place, then trying to make again until it works.

[monte]

There's way too much of a chicken and an egg thing going on with the prebuilts. It would be nice these things could be scripted with something that's likely to already be on the system in question or at least installable. For example: xxd -i for startupstack.cpp.

[mwieder]

Yes, I hate the whole prebuilt / submodule thing.
But that's the hand we've been dealt, at least for the present.

[richmond62]

As each new version of Livecode is made available it would be very nice indeed if a tarball of the complete source code
would be made available: never mind about interim stages and so forth.

For the sake of argument; were I to have a complete tarball I could download the thing on a PPC machine running some sort of PPC Linux
and stand a relatively good chance of getting a version up and running.

As it is, I have to spend quite a bit of time and effort learning GIT, which is not really necessary for what I want to do.

FP7503L.jpg

[LCfraser]

Hi Richmond,

The alternative is to just learn the magic incantations and use them each time:

Code: Select all

git clone --recursive https://github.com/runrev/livecode.git
cd livecode
git submodule update

for the first time. If you already have the source code from the commands above,

Code: Select all

git pull
git submodule update

will update you to the latest version of the code.

[Simon]

Richmond,
You ask a lot for a 6 year old.

Simon

[Klaus]

Richmond,
You ask a lot for a 6 year old.

Simon

[jacque]

Richmond,
You ask a lot for a 6 year old.

LOL! Quote of the day.

[richmond62]

I wonder if I should adopt that as a new masthead to all my posts?

[richmond62]

Fraser, here I am following your "Magic Recipe", and I am beginning to feel fairly foolish as the whole thing is going very smoothly indeed (this on the Dell Optiplex 745
running UbuntuStudio 13.10).

I am downloading the PPC alternate install disk for Xubuntu 12.04 and will dig out my old MacMini at the weekend and install that there.

Then I will try to build a Linux PPC build.

The next question is whether, should it build and work successfully, and how I should pump it back into the system and/or to you lot at RunRev to offer
to any other people daft enough to be running Linux on old Macs.

[mwieder]

Richmond- welcome to the git world.
If you want to contribute the source back once you get things working there are a couple of things to know.

1: if you are going to be making changes to the source (this may involve doing c coding or maybe just fiddling with make files or the like) then I'd advise one step before the original git clone. Make a github account if you haven't done that already, and then fork the original livecode source from the runrev repository. Then clone that one instead of the runrev one. You don't have write access to the runrev repository, so you won't be able to contribute anything back without this step. It may sound daunting, but it's actually pretty easy on github's site.

2: I can't remember the second thing, but I'll get more caffeine and maybe it will come back to me.

Now... I wouldn't be surprised if you find that some libraries required to compile the source are missing on your system, and you'll have to install them. I think most of the required dependencies are listed on the github site, but you're in uncharted territory with linux ppc. Do keep track of any libraries you need that aren't on the list, as these will need to be added to the docs for anyone foolish enough to follow in your footsteps.

[richmond62]

However, I got stuck at this point:

richmond@richmond-OptiPlex-745:~/livecode$ _build/linux/i386/release/engine-community
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
Startup error - /home/richmond/livecode/Toolset/home.rev
richmond@richmond-OptiPlex-745:~/livecode$

[richmond62]

As the baseline Linux system is Ubuntu 6.06 I will install that in VMware player and build there.

[mwieder]

However, I got stuck at this point:

richmond@richmond-OptiPlex-745:~/livecode$ _build/linux/i386/release/engine-community
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading configurations from ~/.fonts.conf is deprecated.
Startup error - /home/richmond/livecode/Toolset/home.rev
richmond@richmond-OptiPlex-745:~/livecode$

Hmmm... that looks to me like you built it properly, but the i386 seems to say that you built an intel version rather than a ppc version.
And then the following warning looks like the system is trying to open the file with gedit.
You may well have to fiddle with the makefiles to get a ppc build going.

[richmond62]

I am trying to build an INTEL version initially, both as a learning experience, and to extract the

engine/src/linuxstubs.cpp
engine/src/startupstack.cpp
engine/src/encodederrors.cpp
engine/src/hashedstrings.cpp
engine/include/revbuild.h
thirdparty/libopenssl/src/sslstubs.cpp

files to transfer over to the Linux PPC setup.