| 1 |
On 03/25/2010 07:43 PM, Mike Frysinger wrote: |
| 2 |
> On Thursday 25 March 2010 12:57:21 Nikos Chantziaras wrote: |
| 3 |
>> On 03/17/2010 03:38 PM, Mansour Al Akeel wrote: |
| 4 |
>>> I am not sure if this is the best list to ask, but I will ask here since |
| 5 |
>>> it's related to development and cross compilation. |
| 6 |
>>> |
| 7 |
>>> I have setup a 32 bit chroot environment to be able to cross develop for |
| 8 |
>>> windows. I followed this guide: |
| 9 |
>>> |
| 10 |
>>> http://www.gentoo.org/proj/en/base/embedded/cross-development.xml |
| 11 |
>> |
| 12 |
>> You should be better off using this instead: |
| 13 |
>> |
| 14 |
>> http://www.nongnu.org/mingw-cross-env |
| 15 |
> |
| 16 |
> mingw + dlls + etc... works just fine under crossdev/Gentoo |
| 17 |
> -mike |
| 18 |
|
| 19 |
It's just a bit difficult to work with. It needs a lot of effort to set |
| 20 |
everything up. I recommend mingw-cross-env because it simply works out |
| 21 |
of the box and you can even compile stuff like Qt and build Windows Qt |
| 22 |
applications without any effort. 64-bit Windows apps also easy to build. |
| 23 |
|
| 24 |
So all things considered, it's the better solution. crossdev of course |
| 25 |
has other virtues and is universal. It's really just the MS Windows |
| 26 |
special case that makes mingw-cross-env worth looking at, since it's |
| 27 |
specialized for just this, while crossdev is a generic solution. |
| 28 |
|
| 29 |
Btw, does anyone intent to put an ebuild of mingw-cross-env in Portage? :P |
Archives