[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Dynamic objects (was: .ONESEHLL not working as expected in 3.82)

From: Eli Zaretskii
Subject: Re: Dynamic objects (was: .ONESEHLL not working as expected in 3.82)
Date: Mon, 29 Apr 2013 23:13:08 +0300

> Date: Mon, 29 Apr 2013 20:40:46 +0100
> From: Tim Murphy <address@hidden>
> Cc: "Paul D. Smith" <address@hidden>, "address@hidden" <address@hidden>
> > How can one deal with them?  The underlying OS is not easily
> > detectable by Make.
> >
> the same way one creates 1 makefile that can build the same code for 2
> operating systems - something done every day.  You make it up. You run
> uname with $(shell) or you pass in an argument from a top level script that
> does know the platform or whatever.   In the end you have a bit of makefile
> that says:
> foo.dll: foo.obj
>    .....
> load foo.dll
> or
> foo.so: foo.o
>    ....
> load foo.so

First, there's no uname on Windows.  You are in fact saying that in
order to run a Makefile one would need something similar to autoconf.

More importantly: this is a lot of trouble we are going to impose on
_users_, just to decide which one of the two extensions to use,
something that Make can know a-priori to begin with.  How does that
make sense?  When users will ask why didn't we teach Make to do that
automatically, what answer will we have for them?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]