qf/quakeforge
0
0
Fork 0
mirror of https://git.code.sf.net/p/quake/quakeforge synced 2025-06-01 09:02:08 +00:00
Code Issues Projects Releases Packages Wiki Activity
quakeforge/tools/cross/ps3-elf/cross-make.sh

16 lines
409 B
Bash
Raw Normal View History

Cross configure/make scripts for ps3toolchain based builds.
2012-08-18 21:33:58 +09:00
#!/bin/sh -x
Make all the cross-compiling scripts consistent. Now all cross builds automatically build qfcc and pak, bail on error, and use pkg-config correctly.
2012-11-29 11:19:09 +09:00
set -e
Make the ps3 cross-build self-contained. More or less. This is a bit of an experiment (which seems to work nicely) in that qfcc and pak are build natively in one build tree, then the full system is cross-built in another tree using the natively build qfcc and pak. Both trees are created by cross-configure.sh as sub-directories of the current directory. However, cross-configure.sh still assumes it is being run in a subdirectory of the main quakeforge directory. cross-make.sh checks if the native tree is in the current directory and if so, builds it, otherwise it just runs make for the cross-build tree (this allows for running cross-make in a sub-directory for things like sorting out build issues).
2012-08-20 10:56:09 +09:00
if test -d native; then
cd native
Make all the cross-compiling scripts consistent. Now all cross builds automatically build qfcc and pak, bail on error, and use pkg-config correctly.
2012-11-29 11:19:09 +09:00
make $*
Make the ps3 cross-build self-contained. More or less. This is a bit of an experiment (which seems to work nicely) in that qfcc and pak are build natively in one build tree, then the full system is cross-built in another tree using the natively build qfcc and pak. Both trees are created by cross-configure.sh as sub-directories of the current directory. However, cross-configure.sh still assumes it is being run in a subdirectory of the main quakeforge directory. cross-make.sh checks if the native tree is in the current directory and if so, builds it, otherwise it just runs make for the cross-build tree (this allows for running cross-make in a sub-directory for things like sorting out build issues).
2012-08-20 10:56:09 +09:00
cd ../powerpc64-ps3-elf
ln -fs ../native/tools/qfcc/source/qfcc .
ln -fs ../native/tools/pak/pak .
fi
Cross configure/make scripts for ps3toolchain based builds.
2012-08-18 21:33:58 +09:00
export PS3DEV=/usr/local/ps3dev
export PSL1GHT=$PS3DEV
export PKG_CONFIG_LIBDIR=$PS3DEV/portlibs/ppu/lib/pkgconfig
export PATH=$PS3DEV/spu/bin:$PS3DEV/ppu/bin:$PS3DEV/bin:$PATH
Make the ps3 cross-build self-contained. More or less. This is a bit of an experiment (which seems to work nicely) in that qfcc and pak are build natively in one build tree, then the full system is cross-built in another tree using the natively build qfcc and pak. Both trees are created by cross-configure.sh as sub-directories of the current directory. However, cross-configure.sh still assumes it is being run in a subdirectory of the main quakeforge directory. cross-make.sh checks if the native tree is in the current directory and if so, builds it, otherwise it just runs make for the cross-build tree (this allows for running cross-make in a sub-directory for things like sorting out build issues).
2012-08-20 10:56:09 +09:00
make PAK='$(top_builddir)/pak' QFCC='$(top_builddir)/qfcc' $*
Reference in a new issue Copy permalink