Allegro 4.4 on Snow Leopard

Allegro 4.4 on Snow Leopard

Felix-The-Ghost

Member #9,729

April 2008

I have this link... with an expired page and a members-only page...so I'm forced to refer to this link...

Honestly most of the stuff on that page means nothing to me -- I pretty much require a step-by-step approach for this, and it's not clear (to me, at least) what to do.

I see involvement with Xcode, the Terminal, Cocoa, and QuickTime. Someone had told me XCode came with Cocoa already...I don't know about QuickTime. And then I have the 4.4 source...but I really don't know what to do with it.

Anyone have a step-by-step guide to this?
I saw some Terminal commands on the linked page, but it doesn't say where to put the code initially and if I need to seek to that directory or whatever ('cd'in Windows)

I'm pretty much lost on installation.
I've quite content with this style of guides.

==========================
<--- The ghost with the most!
---------------------------
[Website] [Youtube]

Evert

Member #794

November 2000

For Allegro 4 you don't need any libraries that don't come with the OS.
You'll need cmake, there's an OS X version for download on their home page.

In a terminal, go to the directory where you downloaded the Allegro, type "cmake" followed by "make". That's really all there is to it.

Your first two links are for using Allegro with xcode, and with build instructions that are not up-to-date for 4.4.

Felix-The-Ghost

Member #9,729

April 2008

Evert said:

For Allegro 4 you don't need any libraries that don't come with the OS.
You mean like Quicktime / Cocoa, right?
You'll need cmake, there's an OS X version for download on their home page.
Downloading right now. Don't fully understand what it is though.

In a terminal, go to the directory where you downloaded the Allegro, type "cmake" followed by "make". That's really all there is to it.
How do I 'go to' in Mac? In Windows it's 'cd...' is it the same?

Your first two links are for using Allegro with xcode, and with build instructions that are not up-to-date for 4.4.
Um ok...so I just do what you said right

==========================
<--- The ghost with the most!
---------------------------
[Website] [Youtube]

Arthur Kalliokoski

Second in Command

February 2005

Assuming OSX console is Unix-like, cd <dir> will work

[EDIT]

The MS-DOS prompt 'cd' was based on Unix...

They all watch too much MSNBC... they get ideas.

Felix-The-Ghost

Member #9,729

April 2008

Yeah, I found out it is indeed 'cd'
Unfortunatley I have somehow messed up something. A variable was not set, it claims.

Quote:

Last login: Mon Feb 22 08:09:10 on console
D60-MAC-07:~ sstutzman$ cd /Users/sstutzman/Desktop/Allegro/allegro-4.4
D60-MAC-07:allegro-4.4 sstutzman$ cmake
cmake version 2.8.0
Usage

cmake [options] <path-to-source>
cmake [options] <path-to-existing-build>

Options
-C <initial-cache> = Pre-load a script to populate the cache.
-D <var>:<type>=<value> = Create a cmake cache entry.
-U <globbing_expr> = Remove matching entries from CMake cache.
-G <generator-name> = Specify a makefile generator.
-Wno-dev = Suppress developer warnings.
-Wdev = Enable developer warnings.
-E = CMake command mode.
-i = Run in wizard mode.
-L[A][H] = List non-advanced cached variables.
--build <dir> = Build a CMake-generated project binary tree.
-N = View mode only.
-P <file> = Process script mode.
--graphviz=[file] = Generate graphviz of dependencies.
--system-information [file] = Dump information about this system.
--debug-trycompile = Do not delete the try compile directories..
--debug-output = Put cmake in a debug mode.
--trace = Put cmake in trace mode.
--help-command cmd [file] = Print help for a single command and exit.
--help-command-list [file] = List available listfile commands and exit.
--help-commands [file] = Print help for all commands and exit.
--help-compatcommands [file]= Print help for compatibility commands.
--help-module module [file] = Print help for a single module and exit.
--help-module-list [file] = List available modules and exit.
--help-modules [file] = Print help for all modules and exit.
--help-custom-modules [file]= Print help for all custom modules and exit.
--help-policy cmp [file] = Print help for a single policy and exit.
--help-policies [file] = Print help for all policies and exit.
--help-property prop [file] = Print help for a single property and exit.
--help-property-list [file] = List available properties and exit.
--help-properties [file] = Print help for all properties and exit.
--help-variable var [file] = Print help for a single variable and exit.
--help-variable-list [file] = List documented variables and exit.
--help-variables [file] = Print help for all variables and exit.
--copyright [file] = Print the CMake copyright and exit.
--help = Print usage information and exit.
--help-full [file] = Print full help and exit.
--help-html [file] = Print full help in HTML format.
--help-man [file] = Print full help as a UNIX man page and exit.
--version [file] = Show program name/version banner and exit.

Generators

The following generators are available on this platform:
Unix Makefiles = Generates standard UNIX makefiles.
Xcode = Generate XCode project files.
CodeBlocks - Unix Makefiles = Generates CodeBlocks project files.
Eclipse CDT4 - Unix Makefiles
= Generates Eclipse CDT 4.0 project files.
KDevelop3 = Generates KDevelop 3 project files.
KDevelop3 - Unix Makefiles = Generates KDevelop 3 project files.

D60-MAC-07:allegro-4.4 sstutzman$ make
Your DJGPP environment variable is not set correctly! It should
point to the djgpp.env file: see the djgpp readme.1st for details.
D60-MAC-07:allegro-4.4 sstutzman$ cmake make
CMake Error: The source directory "/Users/sstutzman/Desktop/Allegro/allegro-4.4/make" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
D60-MAC-07:allegro-4.4 sstutzman$

==========================
<--- The ghost with the most!
---------------------------
[Website] [Youtube]

Evert

Member #794

November 2000

Arthur Kalliokoski said:

Assuming OSX console is Unix-like, cd <dir> will work

It runs bash.

Felix-The-Ghost said:

Downloading right now. Don't fully understand what it is though.

Cmake is a "configurator" that detects how your system is set up, where dependent libraries are and which compiler you have. It then creates a makefile for you to use.

Quote:

How do I 'go to' in Mac? In Windows it's 'cd...' is it the same?

Ok, you may want to read up on some basic BASH terminal commands. If you're even vaguely familiar with Linux, it's exactly the same. Or you could wait for someone who is less of a commandline user than I am to explain how to do things differently.

Alternatively, there is a way to run a CMake GUI application (I think you just run CMake.app). There you select the directory where you downloaded Allegro, and follow the on-screen instructions for configuring. You can also set it to write an XCode project file rather than a Makefile. The XCode project file you can then open in XCode, and compile Allegro through that. I've never used it though, so you'll be a little more on your own there.

EDIT:
ok, try "cmake ." to make it clear that it should use the current directory. I figured that'd be the default, but maybe not.

Felix-The-Ghost

Member #9,729

April 2008

...

Felix-The-Ghost said:

Last login: Mon Feb 22 13:22:33 on ttys000
D60-MAC-07:~ sstutzman$ cd /Users/sstutzman/Desktop/Allegro/allegro-4.4
D60-MAC-07:allegro-4.4 sstutzman$ cmake .
CMake Error: The source directory "/Users/sstutzman/Desktop/Allegro/allegro-4.4" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.
D60-MAC-07:allegro-4.4 sstutzman$

==========================
<--- The ghost with the most!
---------------------------
[Website] [Youtube]

Evert

Member #794

November 2000

Felix-The-Ghost said:

The source directory "/Users/sstutzman/Desktop/Allegro/allegro-4.4" does not appear to contain CMakeLists.txt.

Well, where is it then?
What is in that directory?

Felix-The-Ghost

Member #9,729

April 2008

...there isn't one.
There is a cmakecache.txt but it might be from cmake itself.
Maybe I'll try extracting Allegro again.
edit: nope. I don't know what I'm doing.

==========================
<--- The ghost with the most!
---------------------------
[Website] [Youtube]

Evert

Member #794

November 2000

Ok, so:
1. Which link did you use to download the sources?
2. Where and how did you unpack them?
3. What is the content of the source directory?

For the last one, you can either (1) run "ls" from a terminal in the directory where you unpacked the sources and post the result here, or (2) open the directory in the Finder, press command-A (select all), command-C (copy) and then hit command-V (paste) in the reply box here.

Felix-The-Ghost

Member #9,729

April 2008

src said:

allegro.c
amd64
beos
blit.c
bmp.c
c
clip3d.c
clip3df.c
colblend.c
color.c
config.c
datafile.c
dataregi.c
digmid.c
dispsw.c
dither.c
dos
drvlist.c
file.c
fli.c
flood.c
font.c
fontbios.c
fontbmp.c
fontdat.c
fontgrx.c
fonttxt.c
fsel.c
gfx.c
glyph.c
graphics.c
gsprite.c
gui.c
guiproc.c
i386
inline.c
joystick.c
keyboard.c
lbm.c
libc.c
linux
lzss.c
mac
macosx
math.c
math3d.c
midi.c
misc
mixer.c
modesel.c
mouse.c
pcx.c
poly3d.c
polygon.c
ppc
psp
qnx
quantize.c
quat.c
readbmp.c
readfont.c
readsmp.c
rle.c
rotate.c
scene3d.c
sound.c
spline.c
stream.c
text.c
tga.c
timer.c
unicode.c
unix
vtable.c
vtable8.c
vtable15.c
vtable16.c
vtable24.c
vtable32.c
win
x

When I extract from the original .zip...there is no 'src'
I had a whole directory though with everything.
Where should I get 4.4?

Extracted the .zip to the desktop as 'allegro-4.4'

Edit: Re-downloaded 4.4 from here and did the same commands. It's compiling. It says a lot of it is deprecated though...should I be concerned? Also where is that pastebin thing so I can post it.

==========================
<--- The ghost with the most!
---------------------------
[Website] [Youtube]

Evert

Member #794

November 2000

Ok, that's messed up - that's literally just the Allegro source, which is only a part of what's supposed to be in the archive. Where did you get it?
Get latest stable source from http://alleg.sourceforge.net/wip.html, either the zip file or the .tar.gz file (I guess the latter is what you're supposed to get as it's 'UNIX friendly', but it really doesn't matter).
Unpack that, and then follow the instructions I posted above (you can use the GUI version of CMake if you prefer, it should be under Applications in the Finder).

EDIT

Quote:

Edit: Re-downloaded 4.4 from here [www.strangesoft.net] and did the same commands. It's compiling.

Ok, good.

Felix-The-Ghost said:

It says a lot of it is deprecated though...should I be concerned?

No. Yes. Maybe.
The OS X port of Allegro 4 sits on top of the QuickDraw API, which has been deprecated for a while now. It should be updated, if someone who knows how to do that cares enough to do it. Apart from the warning though, things will work with one caveat: the APIs haven't been ported to 64 bit (since they're deprecated) and therefore Allegro cannot be compiled as 64 bit on Snow Leopard. The same goes for programs using Allegro; they'll need to be compiled as 32 bit binaries. The compiler flag (for gcc) you're looking for is "-m32", I don't know how to set that option from XCode, but there should be an option for it somewhere.

Quote:

Also where is that pastebin thing so I can post it.

Sorry, what?

Felix-The-Ghost

Member #9,729

April 2008

See above edit.
Don't know what to do though. :-/
Wait maybe is your link more stable with less deprecated things?

==========================
<--- The ghost with the most!
---------------------------
[Website] [Youtube]

Evert

Member #794

November 2000

Edited my post as well.

If you want a version of Allegro that compiles on Snow Leopard without deprecation warnings, you'll have to get 4.9 current SVN - which isn't much help if you're working on an Allegro 4.2/4.4 project.

Felix-The-Ghost

Member #9,729

April 2008

I'm planning on using Code::Blocks for development...or would Xcode be better?
I wouldn't know all of the linker settings for Mac.

About pastebin -- there's a link to it on the IRC channel I believe. It's where you put long amounts of text and supply a link so as not to post too much that stretches the page.

==========================
<--- The ghost with the most!
---------------------------
[Website] [Youtube]

OnlineCop

Member #7,919

October 2006

I haven't read very much of this thread.

But I just downloaded and installed allegro 4.4 on my Mac today, and got a project working with XCode, so figured I'd discuss what I did.

Download the .tar.gz version (not the .zip version)
Extract the file
Terminal: cd into the directory with the unpacked allegro sources
mkdir Build/
cd Build/
cmake -DWANT_FRAMEWORKS=yes ..
make all
sudo make install

The first time I installed allegro, there was no /usr/local/ directory, so I had to create them (I had to use sudo because the /usr/ directory required higher privileges):

sudo mkdir /usr/local/
sudo mkdir /usr/local/bin/
sudo mkdir /usr/local/lib/
sudo mkdir /usr/local/include/

For my XCode project, I added the framework, but it laughed and didn't compile correctly. So I had to right-click on the Linker and "Add existing files...". Since the "/usr/" directory is a hidden one, the Finder doesn't show it by default. Start typing the "/" for the "/usr/" directory, and Finder opens a "Go to the folder..." pane where I could type it in. Browse to "/usr/local/lib/" and select BOTH liballeg-main.a and liballeg.dylib.

(My project also included Lua, DUmB, and a few others, and I linked to them in the same way.)

Does this help anything?

Evert

Member #794

November 2000

Felix-The-Ghost said:

I'm planning on using Code::Blocks for development...or would Xcode be better?

Don't know, I use neither. Xcode is the standard development environment on OS X, so you'll find lots of information about it.
It's probably best to stick with something you know and feel comfortable with though.

Quote:

I wouldn't know all of the linker settings for Mac.

You don't have to.
Unless I misunderstand what you meant?

Quote:

About pastebin -- there's a link to it on the IRC channel I believe.

I never use IRC.

Quote:

It's where you put long amounts of text and supply a link so as not to post too much that stretches the page.

The code tags on the forum provide scrollbars within the post. I'd just abuse that.

Anyway, I take it everything has no compiled? Do things run properly now?

Felix-The-Ghost

Member #9,729

April 2008

OnlineCop: I might try that. Supposedly though its made somewhere right now? I guess bin or whatever.

I tried to use <code> tags...

Quote:

Your post of 262.28KB is too long. The maximum size is 64K.

Pastebin truly is miraculous.
Errmm....

==========================
<--- The ghost with the most!
---------------------------
[Website] [Youtube]

Evert

Member #794

November 2000

Felix-The-Ghost said:

Supposedly though its made somewhere right now? I guess bin or whatever.

The build reached "100%", meaning it's done. Everything compiled.
Libraries should be under lib/macosx/, executables under examples/ (by the way - these aren't in application bundles, so you can't run them by double clicking in the Finder, you can run them from the command line though, or by right clicking on tehm in Finder and saying "open in Terminal").

Not to sound rude, but you do know how to browse through a directory structure to find files, right?

Felix-The-Ghost

Member #9,729

April 2008

Oh, you mean how I casually guess at where files are at?
Yeah. I usually post a guess before I actually find out stuff.
Goes for other things too, just so it's logged in case I'm crazy.
Like how I wasn't sure if change directory (cd) was in Mac -- I obviously could've Googled it in the first place, or just tried it.
But I do get lost as to what to do with this...file I made. Especially when nothing is set in stone the wy the Windows guide was seems like there's a bajillion ways to do stuff now.

Also, by linker settings I meant like how in Windows I have to do -WI --subsystem,windows or something...are there any more things for Mac?

Edit: Examples were compiled succesfully...unless they were already there. Exlights is cooler than I remember...but lib/macosx only has source files...

#SelectExpand
  1cadigi.m
  2camidi.m
  3drivers.m
  4hidjoy.m
  5hidman.m
  6keybd.m
  7main.m
  8pcpu.m
  9qtmidi.m
 10quartz.m
 11qzfull.m
 12qzmouse.m
 13qzwindow.m
 14soundman.m
 15system.m

Unless my terminology / vocabulary is completely screwed up and that somehow is this 'library'.

==========================
<--- The ghost with the most!
---------------------------
[Website] [Youtube]

Evert

Member #794

November 2000

Felix-The-Ghost said:

Oh, you mean how I casually guess at where files are at?
Yeah. I usually post a guess before I actually find out stuff.

Yup, that's what I meant. It's fine, but when it's not clear if someone knows how to do something simple, or (more importantly) knows how to find out how to do that, it becomes more difficult to help them because it's not clear how much help they need.
That, and sometimes you run across people who can look things up, but won't, and I usually step back from helping such people because I would just be wasting my time. As long as that's not you, that's fine though.

Quote:

Also, by linker settings I meant like how in Windows I have to do -WI --subsystem,windows or something...are there any more things for Mac?

Ah, ok. No, only Windows needs something like that.

That said, you do need to do some extra work to make an "application bundle", but Allegro comes with a "fixbundle" utility that should help you there.
All systems have their curious perks, it seems.

Except Linux

Quote:

lib/macosx only has source files...

I think you accidentally clicked on src/macosx there.

Felix-The-Ghost

Member #9,729

April 2008

Oh ok It sure was src/macosx.

But lib/macosx only has a tmpfile.txt or something useless (to me)

Quote:

bcc32
beos
djgpp
dmc
libaldat.a
liballeg-main.a
liballeg.4.4.0.dylib
liballeg.4.4.dylib
liballeg.dylib
liballeggl.a
libjpgalleg.a
libloadpng.a
macosx
*tmpfile.txt
mingw32
msvc
psp
qnx
unix
watcom

There are some *.a and *.dylib though in lib itself...are those it?

==========================
<--- The ghost with the most!
---------------------------
[Website] [Youtube]

OnlineCop

Member #7,919

October 2006

Yes, the *.a and *.dylib are your library files (compiled). Those are what get copied (or should be copied) into the /usr/local/lib directory.

Felix-The-Ghost

Member #9,729

April 2008

Hmm, doesn't appear to have been copied...
Plus I could only find usr/lib by searching for it

I guess just copy+paste it huh.

Here's its current contents:

#SelectExpand
   1bundle1.o
   2crt1.o
   3dylib1.o
   4gcc
   5gcrt1.o
   6i686-apple-darwin10
   7java
   8libalias.A.dylib
   9libalias.dylib
  10libamber.a
  11libatlas.dylib
  12libauto.dylib
  13libblas.dylib
  14libBSDPClient.A.dylib
  15libBSDPClient.dylib
  16libbsm.dylib
  17libbz2.1.0.2.dylib
  18libbz2.1.0.dylib
  19libbz2.dylib
  20libc.dylib
  21libcblas.dylib
  22libcharset.1.0.0.dylib
  23libcharset.1.dylib
  24libcharset.dylib
  25libclapack.dylib
  26libcom_err.dylib
  27libcpp_kext.a
  28libcrypto.0.9.7.dylib
  29libcrypto.0.9.dylib
  30libcrypto.dylib
  31libcups.2.dylib
  32libcups.dylib
  33libcupsimage.2.dylib
  34libcupsimage.dylib
  35libcurl.2.dylib
  36libcurl.3.0.0.dylib
  37libcurl.3.dylib
  38libcurl.dylib
  39libcurses.dylib
  40libdbm.dylib
  41libdes425.dylib
  42libDHCPServer.A.dylib
  43libDHCPServer.dylib
  44libdl.dylib
  45libedit.2.dylib
  46libedit.dylib
  47libexslt.0.dylib
  48libexslt.dylib
  49libf77lapack.dylib
  50libform.5.4.dylib
  51libform.5.dylib
  52libform.dylib
  53libgcc_s_ppc64.1.dylib
  54libgcc_s_x86_64.1.dylib
  55libgcc_s.1.dylib
  56libgcc_s.10.4.dylib
  57libgcc_s.10.5.dylib
  58libgimpprint.7.0.0.dylib
  59libgimpprint.7.dylib
  60libgimpprint.dylib
  61libgmalloc.B.dylib
  62libgmalloc.dylib
  63libgssapi_krb5.dylib
  64libiconv.2.2.0.dylib
  65libiconv.2.dylib
  66libiconv.dylib
  67libicucore.A.dylib
  68libicucore.dylib
  69libinfo.dylib
  70libiodbc.2.1.6.dylib
  71libiodbc.2.1.10.dylib
  72libiodbc.2.dylib
  73libiodbc.a
  74libiodbc.dylib
  75libiodbcinst.2.1.6.dylib
  76libiodbcinst.2.1.10.dylib
  77libiodbcinst.2.dylib
  78libiodbcinst.a
  79libiodbcinst.dylib
  80libIOKit.A.dylib
  81libIOKit.dylib
  82libipsec.A.dylib
  83libipsec.dylib
  84libk5crypto.dylib
  85libkmod.a
  86libkmodc++.a
  87libkrb4.dylib
  88libkrb5.dylib
  89libkrb5support.dylib
  90libkrb524.dylib
  91libkvm.dylib
  92libl.a
  93liblapack.dylib
  94liblber.dylib
  95libldap_r.dylib
  96libldap.dylib
  97libltdl.3.1.0.dylib
  98libltdl.3.dylib
  99libltdl.a
 100libltdl.dylib
 101libm.dylib
 102libMallocDebug.a
 103libMallocDebug.A.dylib
 104libmenu.5.4.dylib
 105libmenu.5.dylib
 106libmenu.dylib
 107libmx_debug.dylib
 108libmx_profile.dylib
 109libmx.A_debug.dylib
 110libmx.A_profile.dylib
 111libmx.A.dylib
 112libmx.dylib
 113libncurses.5.4.dylib
 114libncurses.5.dylib
 115libncurses.dylib
 116libnetsnmp.5.2.1.dylib
 117libnetsnmp.5.dylib
 118libnetsnmp.dylib
 119libnetsnmpagent.5.2.1.dylib
 120libnetsnmpagent.5.dylib
 121libnetsnmpagent.dylib
 122libnetsnmphelpers.5.2.1.dylib
 123libnetsnmphelpers.5.dylib
 124libnetsnmphelpers.dylib
 125libnetsnmpmibs.5.2.1.dylib
 126libnetsnmpmibs.5.dylib
 127libnetsnmpmibs.dylib
 128libobjc_profile.A.dylib
 129libobjc_profile.dylib
 130libobjc.A_profile.dylib
 131libobjc.A.dylib
 132libobjc.dylib
 133libpam_misc.1.dylib
 134libpam_misc.dylib
 135libpam.1.0.dylib
 136libpam.1.dylib
 137libpam.dylib
 138libpamc.1.dylib
 139libpamc.dylib
 140libpanel.5.4.dylib
 141libpanel.5.dylib
 142libpanel.dylib
 143libpcap.A.dylib
 144libpcap.dylib
 145libpoll.dylib
 146libPrintServiceQuota.1.dylib
 147libPrintServiceQuota.dylib
 148libproc.dylib
 149libpthread.dylib
 150libpython.dylib
 151libpython2.3.dylib
 152libpython2.dylib
 153libreadline.dylib
 154libresolv.9.dylib
 155libresolv.dylib
 156librpcsvc.dylib
 157libruby.1.dylib
 158libruby.dylib
 159libsasl2.2.0.1.dylib
 160libsasl2.2.0.15.dylib
 161libsasl2.2.dylib
 162libsasl2.dylib
 163libSaturn.dylib
 164libSaturnFE.dylib
 165libsqlite3.0.8.6.dylib
 166libsqlite3.0.dylib
 167libsqlite3.dylib
 168libssl.0.9.7.dylib
 169libssl.0.9.dylib
 170libssl.dylib
 171libstdc++-static.a
 172libstdc++.6.0.4.dylib
 173libstdc++.6.dylib
 174libstmalloc.a
 175libsupc++.a
 176libSystem_debug.dylib
 177libSystem_profile.dylib
 178libSystem.B_debug.dylib
 179libSystem.B_profile.dylib
 180libSystem.B.dylib
 181libSystem.dylib
 182libSystemStubs_debug.a
 183libSystemStubs_profile.a
 184libSystemStubs.a
 185libtcl.dylib
 186libtcl8.3.dylib
 187libtcl8.4.dylib
 188libtermcap.dylib
 189libtidy.A.dylib
 190libtidy.dylib
 191libtk.dylib
 192libtk8.4.dylib
 193libwrap.7.6.dylib
 194libwrap.7.dylib
 195libwrap.a
 196libwrap.dylib
 197libwx_macud_gizmos-2.5.3.0.0.dylib
 198libwx_macud_gizmos-2.5.3.dylib
 199libwx_macud_gizmos-2.5.dylib
 200libwx_macud_gl-2.5.3.0.0.dylib
 201libwx_macud_gl-2.5.3.dylib
 202libwx_macud_gl-2.5.dylib
 203libwx_macud_ogl-2.5.3.0.0.dylib
 204libwx_macud_ogl-2.5.3.dylib
 205libwx_macud_ogl-2.5.dylib
 206libwx_macud_stc-2.5.3.0.0.dylib
 207libwx_macud_stc-2.5.3.dylib
 208libwx_macud_stc-2.5.dylib
 209libwx_macud-2.5.3.0.0.dylib
 210libwx_macud-2.5.3.dylib
 211libwx_macud-2.5.dylib
 212libxml2.2.dylib
 213libxml2.dylib
 214libXplugin.1.0.dylib
 215libXplugin.1.dylib
 216libXplugin.dylib
 217libxslt.1.dylib
 218libxslt.dylib
 219liby.a
 220libz.1.1.3.dylib
 221libz.1.2.3.dylib
 222libz.1.dylib
 223libz.dylib
 224powerpc-apple-darwin10
 225sqlite3
 226system

Nothing for Allegro or the other stuff in there. :-/

==========================
<--- The ghost with the most!
---------------------------
[Website] [Youtube]

Evert

Member #794

November 2000

Felix-The-Ghost said:

Hmm, doesn't appear to have been copied...

Did you run "make install"?