[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Automake support for ObjC++
From: |
Ralf Wildenhues |
Subject: |
Re: [PATCH] Automake support for ObjC++ |
Date: |
Tue, 11 Aug 2009 20:40:09 +0200 |
User-agent: |
Mutt/1.5.20 (2009-08-09) |
Hello Peter,
* Peter Breitenlohner wrote on Wed, Aug 05, 2009 at 10:23:37AM CEST:
> On Tue, 28 Jul 2009, Peter Breitenlohner wrote:
>
> >now that autoconf-2.64 is released, here a revised version of the patch I
> >sent you last week.
> >
> >This new version requires autoconf-2.64 (otherwise aclocal fails) and
> >defines AM_PROG_OBJCXX. A hook for AC_PROG_OBJCXX, eventually to be defined
> >by Autoconf, is already in place.
> I have done some more testing of this patch, with and without the
> corresponding patch for Automake-2.64
and I still haven't looked at the patch at all. :-/
> as well as with and without
> Libtool. Doing this I came across this question:
>
> Should the ObjC++ language set --tag=CXX for libtool, i.e. should the ObjC++
> language definition specify 'libtool_tag' => 'CXX' or should it not?
>
> And somewhat related: should ObjC specify 'libtool_tag' => 'CC'?
Both don't really sound right. The Right Thing[tm] would be for Libtool
to introduce new tags for both languages. At least if there is a chance
that the compilers from the C and C++ ones, respectively.
For now, I guess it would be sufficient however to set libtool_tag to CC
and CXX, respectively (can you please test that?). We definitely need
to fix Libtool func_mode_compile to support the .mm .M and maybe also
the .mi .mii extensions however.
Automake should probably not use or discourage .M as that will cause
problems on case-insensitive systems. Your patch doesn't seem to use
it, good.
Cheers,
Ralf