forks/apenwarr-redo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
apenwarr-redo/docs/cookbook/c/all.rc.od

23 lines
403 B
Text
Raw Normal View History

Experimental new redoconf C/C++ build/autoconfiguration system. 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.
2019-02-03 01:14:51 -05:00
. ./redoconf.rc
rc_include \
redoconf: better handling of required vs optional detectors. CC.rc was the only "mandatory" detection, which was weird and inconsistent. Instead, make it optional like the others, and have it set a HAVE_CC variable appropriately (and have CXX.rc work the same way). Then, add a default.required.rc.od that checks the HAVE_* for any variable and aborts if it is not available. This allows us to fix confusing behaviour in allconfig.do, which would try every compiler on the system, but redo would print a (non-fatal) error message (and prevent redo-stamp optimization) when CC.rc failed for any non-working compilers. Now CC.rc just politely reports that it didn't find a compiler. Then we change all.rc.od to make CC.rc mandatory. Reported-by: Nathaniel Filardo <nwfilardo@gmail.com>
2019-02-23 16:45:08 -05:00
rc/CC.required.rc \
Experimental new redoconf C/C++ build/autoconfiguration system. 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.
2019-02-03 01:14:51 -05:00
rc/CXX.rc \
rc/libqt4.rc \
rc/libgtk2.rc \
rc/Wextra.rc \
rc/Wall.rc \
rc/libm.rc \
rc/rt.autolib.rc \
rc/libpng.rc \
redoconf: clock_gettime() detection needs to depend on -lrt. More generally, default.func.rc.od wasn't super useful because you couldn't specify either a header file or library dependencies. Drop it and make an explicit clock_gettime.rc.od. As a bonus, this also checks that CLOCK_MONOTONIC exists as expected. Reported-by: Wayne Scott <wsc9tt@gmail.com>
2019-02-23 15:51:30 -05:00
rc/clock_gettime.rc \
Experimental new redoconf C/C++ build/autoconfiguration system. 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.
2019-02-03 01:14:51 -05:00
rc/mach_time.h.rc \
rc/windows.h.rc \
rc/posix.rc \
rc/printf_lld.rc \
rc/extra.rc \
rc/all.h.precompiled.rc \
rc/all.hpp.precompiled.rc
rc_appendln LIBS "$LIBRT"
rc_appendln LIBS "$LIBM"
rc_save
Reference in a new issue Copy permalink