> but it still wouldn't help with MSVC: first, it *has* an /Fo$object switch that's the problem I just ran into, after adding some extra CPPFLAGS to a library, like libfoo_a_CPPFLAGS=something which leads to the result, that automake starts to compile CL.EXE -c -o libfoo_a_foo.obj foo.c but CL.EXE always ignores the output name and generates foo.obj. Just replacing -o by -Fo does not work because this is only true for the compile step (-c also given) but not for linking. Since we already have our own CL.EXE wrapper script, we can handle this. Of course it we would be nice, if this handling would be already done by compile, but there are many other issues with other compilers (i.a. armcc) which still require own wrappers. Regards, Carsten _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
