On 30 Mar 2008, at 14:55, Blake Nicholson wrote:
Nicola,
Unfortunately, I think the sample output I sent was not a good
representation. Sorry about that. I went ahead and built base
under apple-apple-apple and redirected stderr to a file. I've
attached the file so you can see all the error messages (many, many
duplicates). Most of the error messages are from things in objc-
gnu2next.h and GSObjCRuntime.h.
Thanks ... OK, so we need to add the -Wno-deprecated everywhere in
apple-gnu-gnu (and presumably, if you're compiling the gnustep-base
Additions, also on apple-apple-apple).
The right fix still seems to be to update the Apple runtime code in
gnustep-base to work with the new runtime if available, but in the
meanwhile
if we add the -Wno-deprecated flag, we should probably add it inside
gnustep-base so that when support for the new runtime is available, we
can remove it in sync. :-)
So I think that the right approach is:
* have core/base/configure.ac detect that we're using the "new"
Apple runtime [this test will be good in the future as well for when
we actually
add support for the new runtime ;-)]
* in that case, have core/base/configure.ac add -Wno-deprecated to
some autoconf output variable (eg, let's call it
WNO_DEPRECATED_OBJCFLAGS),
else leave it empty
* have base.make.in set AUXILIARY_OBJFLAGS +=
@WNO_DEPRECATED_OBJCFLAGS@ when running with the Apple runtime
Does that make any sense to you ?
Thanks for your help
_______________________________________________
Gnustep-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnustep-dev
