| > This is doable within .foo.bar rule, I was referring to the fact that | > your suggestion needs an explicit rule for each object file. | | Not really. This should be enough: | | .$(CXXEXT).o: ; $(CXX) $(CXXFLAGS) -c $< -o $@ | .cc.cpp: ; $(LN_S) $@ $< | .cc.cxx: ; $(LN_S) $@ $< | .cc.C: ; $(LN_S) $@ $< Really, I have mixed feelings wrt this issue. Sometimes I think Autoconf should do its best to assist the end user, sometimes I believe the end user should learn to use his tools and should ./configure CXX='vc++ --enable-standard-c++-extensions' or whatever. The more time passes, the more I'm inclined to prefer the last option. What do you people think? Of course the bad thing in this approach is that people might use an extension in their package which *is* supported by the compiler, but not the extension used by Autoconf.
- Re: aclang.m4 problem (Cygwin + VC++) Alexandre Oliva
- Re: aclang.m4 problem (Cygwin + VC++) Akim Demaille
- Re: aclang.m4 problem (Cygwin + VC++) Alexandre Oliva
- Re: aclang.m4 problem (Cygwin + VC++) Akim Demaille
- Re: aclang.m4 problem (Cygwin + VC++) Alexandre Oliva
- Re: aclang.m4 problem (Cygwin + VC++) Martin Wilck
- Re: aclang.m4 problem (Cygwin + VC++) Alexandre Oliva
- Re: aclang.m4 problem (Cygwin + VC++) Martin Wilck
- Re: aclang.m4 problem (Cygwin + VC++) Paul D. Smith
- Re: aclang.m4 problem (Cygwin + VC++) Martin Wilck
- Re: aclang.m4 problem (Cygwin + VC++) Akim Demaille
- Re: aclang.m4 problem (Cygwin + VC++) Alexandre Oliva
- Re: aclang.m4 problem (Cygwin + VC++) Akim Demaille
- Re: aclang.m4 problem (Cygwin + VC++) Alexandre Oliva
- Re: aclang.m4 problem (Cygwin + VC++) Akim Demaille
- Re: aclang.m4 problem (Cygwin + VC++) Alexandre Oliva
- Re: aclang.m4 problem (Cygwin + VC++) Martin Wilck
- Re: aclang.m4 problem (Cygwin + VC++) Alexandre Oliva
- Re: aclang.m4 problem (Cygwin + VC++) Martin Wilck
- Re: aclang.m4 problem (Cygwin + VC++) Thomas E. Dickey
- Re: aclang.m4 problem (Cygwin + VC++) Akim Demaille