Richard W.M. Jones
rjones at redhat.com
Thu Feb 12 14:16:37 UTC 2009
On Thu, Feb 12, 2009 at 03:08:58PM +0100, Farkas Levente wrote:
> Farkas Levente wrote:
> > Richard W.M. Jones wrote:
> >> Note that the directory layout for mingw64 is somewhat different from
> >> mingw32. I arrived at what I think is the right structure after
> >> extensive discussions and help from members of the mingw-w64 project.
> >> /usr/x86_64-pc-mingw32/sys-root/ (prefix & sysroot)
> >> share
> >> x86_64-pc-mingw32
> >> mingw -> x86_64-pc-mingw32
> >> /usr/x86_64-pc-mingw32/sys-root/x86_64-pc-mingw32 (exec_prefix)
> >> bin (bindir)
> >> include (includedir)
> >> include64 -> include
> >> lib (libdir)
> > can you explain it a bit?
> > why mingw32 and not mingw64?
> > why /usr/x86_64-pc-mingw32/sys-root/x86_64-pc-mingw32 and not
> > /usr/x86_64-pc-mingw32/sys-root/?
> > anyway the same question apply to mingw32 why
> > /usr/i686-pc-mingw32/sys-root/mingw/ and why not
> > /usr/i686-pc-mingw32/sys-root/?
> or why not /usr/i686-pc-mingw32/mingw/ ?
This isn't a matter of guesswork or how we'd like it to be. Upstream
have set up their binutils, compiler, headers etc to work with a
specific directory structure.
We have to replicate that structure.
Otherwise it doesn't work.
Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
More information about the mingw