To test it out, try this: ./do -j10 build cd docs/cookbook/c redo -j10 test It should detect all the compilers on your system and make three separate builds for each one: normal, debug, and optimized. Then it tries to run a test program under each one. If there are windows cross compilers and you also have 'wine' installed, it'll try running the test program under wine as well. redoconf currently has no documentation other than the example program. We'll fix that later.
30 lines
606 B
Text
30 lines
606 B
Text
# This script is run from the output dir,
|
|
# which contains a src/ symlink to the source dir.
|
|
|
|
. ./redoconf.rc
|
|
rc_include all.rc
|
|
|
|
(
|
|
cd "$S"
|
|
echo "main.c"
|
|
echo "monotime.c"
|
|
echo "when.c" # auto-generated source
|
|
echo "flagtest.c" # source with different compiler flags
|
|
|
|
if [ -n "$CXX" ]; then
|
|
echo "slow.cc"
|
|
fi
|
|
|
|
# This is unnecessarily fancy.
|
|
# We're just using it as an example of
|
|
# how to dynamically generate a .list
|
|
# file.
|
|
for d in lib*/*.list lib*/*.list.od; do
|
|
[ -e "$d" ] && echo "${d%%.*}.so"
|
|
done | uniq
|
|
|
|
printf '%s\n' "$LIBGTK2" "$LIBQT4"
|
|
) >$3
|
|
|
|
redo-always
|
|
redo-stamp <$3
|