mingw-cross-env-list
[Top][All Lists]
Advanced

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

Re: [Mingw-cross-env-list] output directory names


From: Mark Brand
Subject: Re: [Mingw-cross-env-list] output directory names
Date: Sun, 12 Dec 2010 00:33:49 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101206 SUSE/3.1.7 Thunderbird/3.1.7


Note that the SQLite project fixed this issue recently, naming the
output directory "sqlite-autoconf-3070400". I just fixed our sqlite.mk
accordingly:

http://hg.savannah.gnu.org/hgweb/mingw-cross-env/rev/a0fbbcfafe46

Thanks for pointing that out. Perhaps this was a silent response to my inquiry on the sqlite mailing list. I have expressed my thanks.

I forgot to mention the "easy" option of just using whatever directory
appears in "tmp-sqlite" after unpacking ("cd *").

There is also the complication of archives whose files are not contained
in a new output directory.
I agree that this would be a nice solution, despite that special case.
However, there's currently no pressing need to do that as SQLite fixed
their issue.

However, feel free to start working on that if you're still motivated
to do that. I'd be glad to help out with Make macros, but the most
work would be to get rid of all uses of $(PKG)_SUBDIR in all src/*.mk
files.

It's not a pressing issue, but it would be a welcome simplification to get rid of $(PKG)_SUBDIR.

Was there originally a compelling reason for the strict treatment of the subdir?

Regarding the references, my quick grepping of $(PKG)_SUBDIR shows that it's mostly used to construct $(PKG)_FILE and more rarely $(PKG)_URL. These seem easy to replace.

The exotic cases are gcc, glib, openexr, postgresql and wxwidgets, some of which even have references to other packages' $(PKG)_SUBDIR. Alternative tricks would have to be found.

Mark




reply via email to

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