public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@arcor.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: MinGW for windows - creating dlls
Date: Thu, 25 Mar 2010 19:53:29 +0200	[thread overview]
Message-ID: <hog7ud$plc$1@dough.gmane.org> (raw)
In-Reply-To: <201003251343.10723.vapier@gentoo.org>

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
> -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




  reply	other threads:[~2010-03-25 17:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 13:38 [gentoo-dev] MinGW for windows - creating dlls Mansour Al Akeel
2010-03-17 19:17 ` Mike Frysinger
2010-03-25 16:57 ` [gentoo-dev] " Nikos Chantziaras
2010-03-25 17:43   ` Mike Frysinger
2010-03-25 17:53     ` Nikos Chantziaras [this message]
2010-03-25 18:11       ` Mike Frysinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='hog7ud$plc$1@dough.gmane.org' \
    --to=realnc@arcor.de \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox