7 FAQ

Q:	We might want to specify the exact CPU types we want to build a target for. example: watchdog example of l4util. However, this must be linked against the according libraries, which may be not available. Do we have CPU-dependent libraries, that should be linked against other libraries? Or: Do we want to provide libraries that should be used with different CPU types?
A:	No, we have one library for every CPU type.
Q:	We want to build several packages with and without l4api support, such as the l4util package. The parse_cmdline stuff is independent of the binding, l4_sleep is not.
A:	This must be split into two libraries, one with l4api support and one without. Use the system-specific $(TARGET_system) variables to define which library should be built for which system. Then, use the target-specific $(SRC_C_target) variables to define which source-files go into which library.
Q:	I want to use an own CRT0, and use "CRT0=mycrt0.o". But mycrt0.o is not built automatically.
A:	This is right. The CRT0 variable references an external object already built. You probably want to use "SRC_S=mycrt0.S" (if its assembler). Set "CRT0=" to prevent the standard crt0's to be linked.
Q:	I need my own linker to link a specific binary. But BID uses $(CC).
A:	Set the CC variable target-dependent. If your target is mytarget and your favorite linker is mylinker, use "mytarget: CC=mylinker".
Q:	Why is mconfig not supported?
A:	mconfig is another Linux configuration tool. It has no help, and provides only one menu-like user-interface, which is not very handy.