The information on
MacPorts in section "Contribute" and the page on "Compile for Mac" are quite helpful.
However, IMHO the page
ufoai.org/wiki/Compile_for_Mac needs an update as follows.
(1)Please delete:
Add headerpad_max_install_names LDFLAGS to MacPorts
Modify /opt/local/share/macports/Tcl/port1.0/portconfigure.tcl configure.ldflags to
default configure.ldflags {"-L${prefix}/lib -Wl,-headerpad_max_install_names"}
This change is only needed if you would like to create dmgs.
This information seems to be outdated. More important, with MacPorts 2.3.2 and UFOAI 2.6_dev you can successfully build a DMG without changes to the default MacPorts setup.
(2)Please improve:
Step 2: Install dependencies
sudo port install libsdl-framework libsdl_mixer-framework libsdl_ttf-framework \
jpeg libpng XviD libtheora gtk2 gtkglext gtksourceview2 libtheora XviD git-core \
p7zip python26
The information quoted above seems to be both ambiguous and outdated.
With MacPorts 2.3.2 and UFOAI 2.6_dev you can successfully build a DMG with the following dependencies:
sudo port install libsdl-framework libsdl_mixer-framework libsdl_ttf-framework \
jpeg libpng XviD libtheora gtk2 gtkglext gtksourceview2 git p7zip python27 \
doxygen libsdl2 libsdl2_mixer libsdl2_ttf
The last line contains additional ports which allows more headers to be found appropriately during the configure phase.
(3)Please correct:
Step 3: Compilation
Toward the bottom, substitute this export command:
export PATH=$PATH:/opt/local/bin:opt/local/sbin:opt/local
The a.m. paths are incomplete and would fail. The more correct export command should read:
export PATH=$PATH:/opt/local/bin:/opt/local/sbin:/opt/local
(4)Furthermore, it may help the unaware reader if the text shows more details on the compiling phases.
Change from:
To compile the binaries, just type (after the configure call was successful).
make
to the more explicit text:
Change directory into the main ufoai folder.
cd ufoai
Establish the appropriate configuration for compiling.
configure
To compile the binaries, just type (after the configure call was successful).
make
(5)Furthermore, the information on
Fink might need an update, I presume. Unfortunately, I discontinued with fink and thus cannot provide an improved text.
Hope this helps.
