and Things are working ok, however, I am unable to install libraries and
generate dlls. The guide describes setting up the environment to cross
compile for other OSs and Archs, but nothing mentioned about mingw.
Can someone kindly suggest to me what are the variables for :
arch-vendor-OS-libc
I am working under 32 bit env, so I would i686 and "pc" for the vendor,
but what about the Os and libc ?
Do I need /usr/i686-mingw32/etc/make.conf and what to put in it ?
Thank you.
03-17-2010, 06:17 PM
Mike Frysinger
MinGW for windows - creating dlls
On Wednesday 17 March 2010 09:38:31 Mansour Al Akeel wrote:
> I am not sure if this is the best list to ask
On Thursday 25 March 2010 12:57:21 Nikos Chantziaras wrote:
> On 03/17/2010 03:38 PM, Mansour Al Akeel wrote:
> > I am not sure if this is the best list to ask, but I will ask here since
> > it's related to development and cross compilation.
> >
> > I have setup a 32 bit chroot environment to be able to cross develop for
> > windows. I followed this guide:
> >
> > http://www.gentoo.org/proj/en/base/embedded/cross-development.xml
>
> You should be better off using this instead:
>
> http://www.nongnu.org/mingw-cross-env
mingw + dlls + etc... works just fine under crossdev/Gentoo
-mike
03-25-2010, 04:53 PM
Nikos Chantziaras
MinGW for windows - creating dlls
On 03/25/2010 07:43 PM, Mike Frysinger wrote:
On Thursday 25 March 2010 12:57:21 Nikos Chantziaras wrote:
On 03/17/2010 03:38 PM, Mansour Al Akeel wrote:
I am not sure if this is the best list to ask, but I will ask here since
it's related to development and cross compilation.
I have setup a 32 bit chroot environment to be able to cross develop for
windows. I followed this guide:
mingw + dlls + etc... works just fine under crossdev/Gentoo
-mike
It's just a bit difficult to work with. It needs a lot of effort to set
everything up. I recommend mingw-cross-env because it simply works out
of the box and you can even compile stuff like Qt and build Windows Qt
applications without any effort. 64-bit Windows apps also easy to build.
So all things considered, it's the better solution. crossdev of course
has other virtues and is universal. It's really just the MS Windows
special case that makes mingw-cross-env worth looking at, since it's
specialized for just this, while crossdev is a generic solution.
Btw, does anyone intent to put an ebuild of mingw-cross-env in Portage? :P
03-25-2010, 05:11 PM
Mike Frysinger
MinGW for windows - creating dlls
On Thursday 25 March 2010 13:53:29 Nikos Chantziaras wrote:
> On 03/25/2010 07:43 PM, Mike Frysinger wrote:
> > On Thursday 25 March 2010 12:57:21 Nikos Chantziaras wrote:
> >> On 03/17/2010 03:38 PM, Mansour Al Akeel wrote:
> >>> I am not sure if this is the best list to ask, but I will ask here
> >>> since it's related to development and cross compilation.
> >>>
> >>> I have setup a 32 bit chroot environment to be able to cross develop
> >>> for windows. I followed this guide:
> >>>
> >>> http://www.gentoo.org/proj/en/base/embedded/cross-development.xml
> >>
> >> You should be better off using this instead:
> >>
> >> http://www.nongnu.org/mingw-cross-env
> >
> > mingw + dlls + etc... works just fine under crossdev/Gentoo
>
> It's just a bit difficult to work with. It needs a lot of effort to set
> everything up.
it'll stay that way unless someone improves things. it works for my needs, so
i have no vested interest here.
> 64-bit Windows apps also easy to build.
and it's trivial with crossdev too. i build 64bit windows JTAG/USB apps.
> Btw, does anyone intent to put an ebuild of mingw-cross-env in Portage? :P
i only spend time on crossdev. anything else is a waste.
-mike
MinGW for windows - creating dlls
