[openbeos] building not so custom targets
- From: Jérôme Duval <korli@xxxxxxxx>
- To: openbeos <openbeos@xxxxxxxxxxxxx>
- Date: Wed, 24 Dec 2003 12:13:16 +0100
Hello,
1/ i need to build two targets with the same files.
Should i do something like this ? Am i sure it'll CC two times the file.c and
not reuse the first one ? Is it the way to do this ?
{
SubDirCcFlags -DPROG1 -Wall -Wno-multichar ;
SubDirC++Flags -DPROG1 -Wall -Wno-multichar ;
}
R5KernelAddon prog1 : bin :
file.c ;
{
SubDirCcFlags -DPROG2 -Wall -Wno-multichar ;
SubDirC++Flags -DPROG2 -Wall -Wno-multichar ;
}
R5KernelAddon prog2 : bin :
file.c ;
2/ How can i extend the #include search to subdirectories ?
#include "file.h" // file.h is in a subdirectory
3/ How can i extend source search to subdirectories or a subdirectory of the
parent directory ?
R5KernelAddon prog1 : bin :
file.c ; # file.c is in a subdirectory
4/ Is it mandatory to use locked memory (not with malloc) in interrupt handlers
?
5/ Using cpp in kernel drivers seems possible. Is it just including
kernel_cpp.h
and linking kernel_cpp.cpp ? are there some issues i should know (virtual
functions, exporting compliant drivers symbols in a cpp file... ) ?
R5KernelAddon udf : bin :
kernel_cpp.cpp
file.cpp
SEARCH on [ FGristFiles
kernel_cpp.cpp
] = [ FDirName $(OBOS_TOP) src kernel core util ] ;
Thanks for all,
Jerome
- Follow-Ups:
- [openbeos] Re: building not so custom targets
- From: Axel Dörfler
- [openbeos] Re: building not so custom targets
- From: Andrew Bachmann
Other related posts:
- » [openbeos] building not so custom targets
- » [openbeos] Re: building not so custom targets
- » [openbeos] Re: building not so custom targets
- » [openbeos] Re: building not so custom targets
- » [openbeos] Re: building not so custom targets
- » [openbeos] Re: building not so custom targets
- [openbeos] Re: building not so custom targets
- From: Axel Dörfler
- [openbeos] Re: building not so custom targets
- From: Andrew Bachmann