Hi, On Mon, Apr 03, 2006 at 02:49:44PM +0100, Reuben Thomas wrote: > Package: mingw32 > Version: 3.4.2.20040916.1-2 > Severity: wishlist > > Please could you link all the binaries into /usr/i586-mingw32msvc/bin, > e.g. /usr/bin/i586mingw32msvc-gcc --> /usr/i586-mingw32msvc/bin/gcc? > > This would make it easier to use some build systems by just setting a > prefix for all paths (/usr --> /usr/i586-mingw32msvc), so that systems > that do something like: > > BINPATH = $prefix/bin > LIBPATH = $prefix/lib > INCPATH = $prefix/include > > &c. The rest of the mingw32 package is nicely set up for this to work,
This comes up from time to time, but I'm still not totally convinced that this is an idiom we should be encouraging. The upstream install does not do this, and it is not what is recommended by autoconf. What I'd really like to see before I go messing with it like this, is some sort of documentation that clearly defines where and how various cross tools should be installed -- so that whatever we do is likely to work for any cross variant, not just this one. I'm a little loathe to blaze out on our own if this may be a source of future migration trouble, but I would also like to see this settled once and for all before the end of time ;-) > and indeed some of the binaries are already hard linked as I'd like > (e.g. strip and dlltool). These are from the -binutils... but I agree that just makes it more confusing. Nikita, can you throw any light on the direction we should be taking here? It seems to share some context with the recent discussion re dpkg-cross. cheers, Ron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
