Is there a way to run/compile residual on ppc Mac G4?

General chat related to ScummVM, adventure gaming, and so on.

Moderator: ScummVM Team

User avatar
somaen
ScummVM Developer
Posts: 376
Joined: Thu Apr 21, 2011 7:31 pm
Location: Trondheim, NO

Post by somaen »

Sorry for double-posting, but:

Saving should be fixed now, as should make bundle. Do tell if it still doesn't work after git pull.
Elowan
Posts: 45
Joined: Tue May 10, 2011 8:05 am

Post by Elowan »

ok, i┬┤ve done the following steps:

deleted the residual directory
run git clone git://github.com/residualvm/residualvm.git
edit configure (changed path to opt/local)
run ./configure
edit config.h (deleting the 3 64bit-related lines)
run make bundle

aaaand taaadaaa: i got an app with icon AND the new Theme (the nice GUI look from ScummVM)

AND loading a savegame works, as far i┬┤ve tested it :D

This is SO GREAT, i┬┤m happy like a child ;)

Thank YOU ALL for the effort, hints and tutoring a total noob to compile RESIDUAL.

Ok, i just got two things left, but i make a new thread, because it┬┤s another issue.


Best Regards,

Elo
User avatar
somaen
ScummVM Developer
Posts: 376
Joined: Thu Apr 21, 2011 7:31 pm
Location: Trondheim, NO

Post by somaen »

Great news. If you'd like to, you could write a guide for doing exactly that yourself, and I'll put it up on the Wiki, to help other PPC-owners with an urge to play Grim.

(I'd like you to do it, since you're the one that knows which parts might be a bit hard to understand).
Elowan
Posts: 45
Joined: Tue May 10, 2011 8:05 am

Post by Elowan »

ja,

sure i will do that! please just give me some time - i promise i make a guide (that noobs like me could understand) ;)

greetings
User avatar
MeddlingMonk
Posts: 221
Joined: Wed Jan 21, 2009 10:06 pm

Post by MeddlingMonk »

It's too bad I wasn't able to be more help. I've played with MacPorts in the past but have always gone back to Fink.

It really would be nice if the two could merge, but as MacPorts is BSD-based and Fink is Debian-based, maybe that's not even possible.
User avatar
somaen
ScummVM Developer
Posts: 376
Joined: Thu Apr 21, 2011 7:31 pm
Location: Trondheim, NO

Post by somaen »

Not really very much to be gained from such a merge, the projects are rather very different, and their approach to packages too.

Macports uses a lot of packages almost directly from upstream, and can do stuff like building universal devel libs, or storing multiple versions of a lib for covering compatibility with other programs that can't be updated.

Fink does a more debian-style approach, and keeps the more well-tested packages. Fink is also a lot faster than Macports.

Diversity is great, why should they merge?
Elowan
Posts: 45
Joined: Tue May 10, 2011 8:05 am

Post by Elowan »

the tutroial is close to be finished. i just want to add a few likns, then i┬┤ll post it here! should be the next 1-2 days i hope.
User avatar
MeddlingMonk
Posts: 221
Joined: Wed Jan 21, 2009 10:06 pm

Post by MeddlingMonk »

einarj wrote:Diversity is great, why should they merge?
Possibly no reason other than each project puts things in different places. Of course, that allows a person to have both, and keeps everything separate from the OS, but it can cause problems when the source looks for a Fink install or a MacPorts install and user has the other. As you say, they are two different approaches, and neither is really better than the other, but it can cause issues. None fatal, but still...

The main reason I sort of wish they could be merged is due to the situation that used to exist with Fedora. At first, there were several third-party repositories with a lot of overlap, and you could cause trouble for yourself if you mixed software from different repositories on your system. Unlike OSX and MacPorts and Fink, these packages aren't segregated from the OS and from each other (so this isn't anything like a 100%-parallel situation). Eventually, the main repositories merged into one and the overlap and the conflicts went away. But I suppose you do lose diversity this way, although it's arguably more convenient for the end-user.
User avatar
somaen
ScummVM Developer
Posts: 376
Joined: Thu Apr 21, 2011 7:31 pm
Location: Trondheim, NO

Post by somaen »

Just a few tips: Step 1 can actually be skipped, as 3.1.4 is a full install (and doesn't require 3.1 to be installed already).

I also think you need to do "sudo port..." in step 6.

Also, this solution also applies to the 10.5 users on Intel, just skip step 8 on Intel.

I propose this gets stickied (preferably with my note on Intel also added, so it helps both PPC-users, and 10.5-intel-users).

Thanks for going through the process and making a tutorial out of it.

Great work.
Elowan
Posts: 45
Joined: Tue May 10, 2011 8:05 am

Post by Elowan »

hi,

macports recommend this:
Ensure that the optional components for command line development are installed ("Unix Development" in the Xcode 3.x installer).
I don┬┤t know, if XCode 3.1.4 has this packages, too?! When installing XCode 3.0 you can select a "full install" or "install without additional components" (something like that).

If you┬┤re sure, that 3.1.4 includes all the stuff, i┬┤ll edit that.

I can┬┤t remember exactly, if step 6 needs "Sudo"... but i┬┤ll edit that, just in case. Guess a sudo can┬┤t be wrong.

I added your hint for Intel users, skipping Step 8

thx for the tips.

greetings
Elo
User avatar
somaen
ScummVM Developer
Posts: 376
Joined: Thu Apr 21, 2011 7:31 pm
Location: Trondheim, NO

Post by somaen »

"Unix Development" is what gives you "make" in the terminal. I haven't installed XCode from the Leopard-disc in a loooong time, but I do have a running system, Like i said, I'm quite sure that the 3.1.4. download is a complete replacement for 3.0. (However, there should of course be no problem, other than extra time)

You MIGHT still need X11 of the CD though. (I can't remember right now if any of the ports-stuff needs it).
Elowan
Posts: 45
Joined: Tue May 10, 2011 8:05 am

Post by Elowan »

Yes, X11 is needed.

Fixed the XCode issue.

Thx
User avatar
somaen
ScummVM Developer
Posts: 376
Joined: Thu Apr 21, 2011 7:31 pm
Location: Trondheim, NO

Post by somaen »

I just split the Tutorial into it's own thread and stickied that, any further issues to that can be discussed there. The post is also still yours, so feel free to edit any new findings into it.
Jon God
Posts: 35
Joined: Sat Oct 27, 2007 9:13 pm

Post by Jon God »

I keep getting this when I try and compile on my PPC 10.4 mac

Code: Select all

Makefile.common:144: no file name for `-include'
    C++      backends/platform/sdl/hardwarekeys.o
    C++      backends/platform/sdl/main.o
    C++      backends/platform/sdl/sdl.o
    C++      backends/platform/sdl/posix/posix-main.o
    C++      backends/platform/sdl/posix/posix.o
    C++      backends/platform/sdl/macosx/macosx-main.o
    C++      backends/platform/sdl/macosx/macosx.o
    C++      base/main.o
    C++      base/commandLine.o
    C++      base/plugins.o
    C++      engines/grim/imuse/imuse.o
    C++      engines/grim/imuse/imuse_mcmp_mgr.o
    C++      engines/grim/imuse/imuse_music.o
    C++      engines/grim/imuse/imuse_script.o
    C++      engines/grim/imuse/imuse_sndmgr.o
    C++      engines/grim/imuse/imuse_tables.o
    C++      engines/grim/imuse/imuse_track.o
    C++      engines/grim/lua/lapi.o
    C++      engines/grim/lua/lauxlib.o
    C++      engines/grim/lua/lbuffer.o
    C++      engines/grim/lua/lbuiltin.o
    C++      engines/grim/lua/ldo.o
    C++      engines/grim/lua/lfunc.o
    C++      engines/grim/lua/lgc.o
    C++      engines/grim/lua/liolib.o
    C++      engines/grim/lua/llex.o
    C++      engines/grim/lua/lmathlib.o
    C++      engines/grim/lua/lmem.o
    C++      engines/grim/lua/lobject.o
    C++      engines/grim/lua/lrestore.o
    C++      engines/grim/lua/lsave.o
    C++      engines/grim/lua/lstate.o
    C++      engines/grim/lua/lstring.o
    C++      engines/grim/lua/lstrlib.o
    C++      engines/grim/lua/lstx.o
    C++      engines/grim/lua/ltable.o
    C++      engines/grim/lua/ltask.o
    C++      engines/grim/lua/ltm.o
    C++      engines/grim/lua/lundump.o
    C++      engines/grim/lua/lvm.o
    C++      engines/grim/lua/lzio.o
    C++      engines/grim/movie/codecs/blocky8.o
    C++      engines/grim/movie/codecs/blocky16.o
    C++      engines/grim/movie/codecs/vima.o
    C++      engines/grim/movie/bink.o
In file included from /usr/include/sys/time.h:235,
                 from /usr/include/sys/select.h:148,
                 from /usr/include/unistd.h:483,
                 from /usr/include/zconf.h:289,
                 from /usr/include/zlib.h:34,
                 from ./engines/grim/movie/movie.h:26,
                 from ./engines/grim/movie/bink.h:34,
                 from engines/grim/movie/bink.cpp:41:
/usr/include/time.h:127:19: error: macro "clock" passed 1 arguments, but takes just 0
/usr/include/time.h:126: error: expected initializer before 'SYMBOL'
/usr/include/time.h:128: error: expected initializer before 'SYMBOL'
/usr/include/time.h:129: error: expected initializer before 'SYMBOL'
/usr/include/time.h:130: error: expected initializer before 'SYMBOL'
/usr/include/time.h:131: error: expected initializer before 'SYMBOL'
/usr/include/time.h:132: error: expected initializer before 'SYMBOL'
/usr/include/time.h:133: error: expected initializer before 'SYMBOL'
/usr/include/time.h:136: error: expected initializer before 'SYMBOL'
make: *** [engines/grim/movie/bink.o] Error 1
any ideas?
User avatar
somaen
ScummVM Developer
Posts: 376
Joined: Thu Apr 21, 2011 7:31 pm
Location: Trondheim, NO

Post by somaen »

How new is your source? try

Code: Select all

git pull origin master
to check that you're updated.
Post Reply