> > Has anyone tested gnustep-make with ObjC++ files? Is it possible to > > simply have an ObjC++ file in the makefile and expect it to compile once > > we have gcc 4.1 changes into base/gui? > > chuck:cbv :0> gmake > Making all for tool ObjC++Test... > gmake[1]: *** No rule to make target `shared_obj/Test.mm', needed by > `shared_obj/ObjC++Test'. Stop. > gmake: *** [ObjC++Test.all.tool.variables] Error 2 > chuck:cbv :2>
Thanks ... I quickly added the missing rule, but ... 1. I don't have an ObjC++ compiler at the moment so can't test it properly 2. I didn't add the the ./configure options to detect if ObjC++ is supported by the compiler or not yet. So if you try to use it and the compiler doesn't support it, you'll get some confusing error messages (this needs fixing). :-P Anyway, if you have a compiler that supports ObjC++, have a look at CVS and see if it works for you :-) You need to list ObjC++ files in xxx_OBJCC_FILES .mm files should be recognized and compiled. :-) I didn't automatically add in the additional user-specified C++ or ObjC flags, in the assumption that end-users might need the flexibility of specifying some flags for C++ or ObjC or ObjC++ only. :-) I automatically added in the internal/system ObjC flags (eg, -fconstant-string-class=NSConstantString) though, I assume that's required to compile ObjC++. ;-) If you want to pass special flags to ObjC++ file compilation, you can use xxx_OBJCCFLAGS for a single program, or ADDITIONAL_OBJCCFLAGS for everything. (and obviously, you can still use yyy_FILE_FLAGS where yyy is the file name to specify flags to use only for a single file, and similar yyy_FILE_FILTER_OUT_FLAGS to filter out flags for a single file only). ;-) Comments and suggestions welcome. Let's get it right before it's used as once people start using it, it will be difficult to change it ;-) Thanks _______________________________________________ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev