Re: [Mingw-cross-env-list] Questions / Bugs?

[Thomas Dineen]

Volker:

    Thank You for the kindly responses and help. After reading
your responses below I tend to agree: Just build everything in the
cross compile environment.

Thomas Dineen


"Note that I'm not saying it is impossible to do what you are
trying to do. However, mingw-cross-env has never been designed
to be used that way. And to be honest, I also don't see any
sense in what you are trying to do. Why do you want to do that?
Am I missing something? Is there another good use case of
mingw-cross-env which we aren't aware of, and which we should
add support for?"




On 8/12/2011 4:30 AM, Volker Grabsch wrote:
> Hello Thomas,
>
> I think I should clarify what this project is all about, as
> there seems to be some fundamental misunderstanding.
>
> Thomas Dineen schrieb:
> > I think there is come confusion here:
> > 1) My first cross compile environment is currently running on Fedora 14.
> > Where I build the tree as indicated by the provided make scripts.
> > With the goal of producing a number of tools and a large number of
> > libraries.
> The typical goal is to build your application. And yes, there
> are some *.exe files in i686-pc-mingw32/bin/ that are created
> as a side-product, such as psql.exe and gdb.exe. However, those
> should be stand-along (statically linked), so you can simply copy
> over exactly those *.exe files you need on your Windows system.
> No need to copy any library, let alone the whole i686-pc-mingw32/
> sub directory.
>
> > 2) I then tar the entire tree at the i686-pc-mingw32 Root to move it
> > to the windows Windows / MinGW machine.
> This subtree is not meant to be moved anywhere. It may not even
> be relocatable within your Unix system. Supporting that kind of
> flexibility would be a major additional effort, and I wonder why
> anybody would want to do that.
>
> > 3) Then on the Windows / MinGW machine the directory tree is untarred.
> > I assume everyone pretty much dose this?
> No, definitely not!
>
> The typical use case for mingw-cross-env is to cross-compile an
> application. That is, the whole build process happens on the Unix
> system, and the result is a big *.exe file, or maybe a bunch of
> *.exe and *.dll files, depending on your project at hand. Even
> the installer *.exe can be produced unter Unix, e.g. via NSIS.
> The idea of cross-compiling is that you don't have to start
> Windows at all!
>
>
> Note that I'm not saying it is impossible to do what you are
> trying to do. However, mingw-cross-env has never been designed
> to be used that way. And to be honest, I also don't see any
> sense in what you are trying to do. Why do you want to do that?
> Am I missing something? Is there another good use case of
> mingw-cross-env which we aren't aware of, and which we should
> add support for?
>
>
> Greets,
> Volker