00646544107E3D8300183915/* Run Script to Create SDL_config.h */={
isa=PBXShellScriptBuildPhase;
buildActionMask=2147483647;
files=(
);
inputPaths=(
"$(SRCROOT)/../../include/SDL_config.h.default",
);
name="Run Script to Create SDL_config.h";
outputPaths=(
"$(SRCROOT)/../../include/SDL_config.h",
);
runOnlyForDeploymentPostprocessing=0;
shellPath=/bin/sh;
shellScript="# Make sure that include/SDL_config.h is a symlink to SDL_config.h.default.\n# If it exists and is not a symlink, it was probably generated by configure and\n# we move it aside.\nif [ ! -L ../../include/SDL_config.h ]; then\n if [ -e ../../include/SDL_config.h ]; then\n mv ../../include/SDL_config.h ../../include/SDL_config.h.generated\n fi\n ln -s SDL_config.h.default ../../include/SDL_config.h\nfi\n";
};
00646546107E3DB200183915/* Run Script to Create SDL_revision.h */={
isa=PBXShellScriptBuildPhase;
buildActionMask=2147483647;
files=(
);
inputPaths=(
"$(SRCROOT)/../../build-scripts/showrev.sh",
"$(SRCROOT)/../../build-scripts/updaterev.sh",
);
name="Run Script to Create SDL_revision.h";
outputPaths=(
"$(SRCROOT)/../../include/SDL_revision.h",
);
runOnlyForDeploymentPostprocessing=0;
shellPath=/bin/sh;
shellScript="if test -f ~/.bash_profile; then source ~/.bash_profile; fi\nif test -f ~/.bashrc; then source ~/.bashrc; fi\nsh ../../build-scripts/updaterev.sh";
comments="We recommend installing to /Library/Frameworks\nAn alternative is $(HOME)/Library/Frameworks for per-user if permissions are an issue.\n\nAdd the framework to the Groups & Files panel (under Linked Frameworks is a good place) and enable the check box for the targets that need to link to it. You can also manually add \"-framework SDL\" to your linker flags if you don't like the check box system.\n\nAdd /Library/Frameworks/SDL.framework/Headers to your header search path\nAdd /Library/Frameworks to your library search path\n(Adjust the two above if installed in $(HOME)/Library/Frameworks. You can also list both paths if you want robustness.)\n\nWe used to use an exports file. It was becoming a maintenance issue we kept neglecting, so we have removed it. If you need it back, set the \"Exported Symbols File\" option to:\n../../src/main/macosx/exports/SDL.x\n(You may need to regenerate the exports list. There is a Makefile in that directory that you can run from the command line to rebuild it.)\nLong term, we want to utilize gcc 4.0's new visibility feature (analogous to declspec on Windows). Other platforms would benefit from this change too. The downside is that we still use gcc 3.3 for the PowerPC build here so only our x86 builds will cull the symbols if we go down this route (and don't use the exports file).\n\n";
comments="We recommend installing to /Library/Frameworks\nAn alternative is $(HOME)/Library/Frameworks for per-user if permissions are an issue.\n\nAdd the framework to the Groups & Files panel (under Linked Frameworks is a good place) and enable the check box for the targets that need to link to it. You can also manually add \"-framework SDL\" to your linker flags if you don't like the check box system.\n\nAdd /Library/Frameworks/SDL.framework/Headers to your header search path\nAdd /Library/Frameworks to your library search path\n(Adjust the two above if installed in $(HOME)/Library/Frameworks. You can also list both paths if you want robustness.)\n\nWe used to use an exports file. It was becoming a maintenance issue we kept neglecting, so we have removed it. If you need it back, set the \"Exported Symbols File\" option to:\n../../src/main/macosx/exports/SDL.x\n(You may need to regenerate the exports list. There is a Makefile in that directory that you can run from the command line to rebuild it.)\nLong term, we want to utilize gcc 4.0's new visibility feature (analogous to declspec on Windows). Other platforms would benefit from this change too. The downside is that we still use gcc 3.3 for the PowerPC build here so only our x86 builds will cull the symbols if we go down this route (and don't use the exports file).\n\n";
002D2AA5106C190C00BF972E/* Run Script to Create SDL_config.h */={
isa=PBXShellScriptBuildPhase;
buildActionMask=2147483647;
files=(
);
inputPaths=(
"$(SRCROOT)/../../include/SDL_config.h.default",
);
name="Run Script to Create SDL_config.h";
outputPaths=(
"$(SRCROOT)/../../include/SDL_config.h",
);
runOnlyForDeploymentPostprocessing=0;
shellPath=/bin/sh;
shellScript="# Make sure that include/SDL_config.h is a symlink to SDL_config.h.default.\n# If it exists and is not a symlink, it was probably generated by configure and\n# we move it aside.\nif [ ! -L ../../include/SDL_config.h ]; then\n if [ -e ../../include/SDL_config.h ]; then\n mv ../../include/SDL_config.h ../../include/SDL_config.h.generated\n fi\n ln -s SDL_config.h.default ../../include/SDL_config.h\nfi\n";
};
002D2AA7106C194100BF972E/* Run Script to Create SDL_revision.h */={
isa=PBXShellScriptBuildPhase;
buildActionMask=2147483647;
files=(
);
inputPaths=(
"$(SRCROOT)/../../build-scripts/showrev.sh",
"$(SRCROOT)/../../build-scripts/updaterev.sh",
);
name="Run Script to Create SDL_revision.h";
outputPaths=(
"$(SRCROOT)/../../include/SDL_revision.h",
);
runOnlyForDeploymentPostprocessing=0;
shellPath=/bin/sh;
shellScript="# The official HG installer puts the binary in /usr/local/bin, so add that\n# to Xcode's path and see if the hg executable is found. Otherwise, source\n# the user's bash settings file as a last resort.\nPATH=$PATH:/usr/local/bin\nif ! which -s hg ; then\n if test -f ~/.bash_profile; then source ~/.bash_profile; fi\nfi\nsh ../../build-scripts/updaterev.sh\n";
