[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Please find attached a note on binary compatibility for the Mac. Let me know
if it's not clear.
Pete
Index: docs/src/abi._tx
===================================================================
RCS file: /cvsroot/alleg/allegro/docs/src/abi._tx,v
retrieving revision 1.11
diff -u -r1.11 abi._tx
--- docs/src/abi._tx 19 Aug 2005 15:26:59 -0000 1.11
+++ docs/src/abi._tx 25 Aug 2005 17:13:27 -0000
@@ -109,14 +109,29 @@
your copy of Allegro must NOT have assembly routines enabled (it
wouldn't work anyhow).
-
-
@heading
MacOS X notes
- XXX fill this in
-
-
+ On OSX there are two 'styles' of linking - Unix style and Mac style.
+ For the Unix style linking, you would use `allegro-config --libs`
+ on the link line. For versioning, follow the advice given in the
+ 'Linux on x86' section above, using the command otool -L instead
+ of ldd.
+
+ For example, otool -L <mybinary> should give
+
+ liballeg-4.2.dylib (compatibility version 4.2.0, current version 4.2.0)
+
+ For the Mac style, use `allegro-config --frameworks` on the link
+ line, or add Allegro.framework to your project if you are using
+ XCode. In this case, the versioning is done inside the framework
+ itself.
+
+ Apple recommends that an application should be entirely self-
+ contained. To achieve this in Allegro, static-link the executable
+ and use fixbundle to bind all its resources together. In this
+ way, you will not need to worry about incompatible versions of
+ the library. This is useful if you are distributing an application.
@heading
Final notes