Re: Extending gnustep-tests for .c and .cc files

[Stefan Bidi]

I was specifically trying not to link against the ObjC runtime and gnustep-base.  The reason for that is because I would like to support building corebase without needing all the ObjC stuff for whoever wants to do that, and so I also want to make sure the tests reflect that case.

On Mon, Jun 17, 2013 at 1:46 AM, Richard Frith-Macdonald <address@hidden> wrote:

PS. adding support for .c and .cc files seems a little unnecessary since testing of C and C++ code is already supported (in .m and .mm files).

It's true that when you test C code in a .m file, you do get the ObjC runtime library and the gnustep-base library added to the link command, but if you don't use them that seems harmless, and if you want to link alternative libraries which export the same symbols, you could do so with a little care about the link order you use.

I guess the point is mainly familiarity/clarity ... people might just want to put a .c extension on their files rather than a .m extension.  The patch is good to allow that.