> 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
b
On November, 15, 2009 Ralf wrote:
> I'm not sure about the best way to proceed here, or what level of
> emulation to add to `compile', but going just one step seems less
> attractive than the current status quo or going even further.
It's not clear to me how to proceed either. My goal is to wor
Hi David, and sorry for the long delay,
* David Byron wrote on Fri, Nov 13, 2009 at 08:18:35PM CET:
> On Friday September 4th, 2009, Eric Blake wrote:
> > According to David Byron on 8/14/2009 1:57 PM:
> > > I'm not sure whether this is something I'm doing wrong
> > > or something wrong with auto
On Fri, Sep 4, 2009 at 10:27 PM, Eric Blake wrote:
>> I'm not sure whether this is something I'm doing wrong or something wrong
>> with automake, autoconf or libtool. At the moment I'm leaning to autoconf +
>> automake.
>
> compile is maintained by automake, so I've redirected your patch there.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[adding bug-automake]
According to David Byron on 8/14/2009 1:57 PM:
Hi David,
Thanks for the report, and sorry for the delayed reply...
> I'm not sure whether this is something I'm doing wrong or something wrong
> with automake, autoconf or libtoo
