From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: Zhenqiang Chen <zhenqiang.chen@linaro.org>
Cc: Ralf Corsepius <ralf.corsepius@rtems.org>, crossgcc@sourceware.org
Subject: Re: [zlib PATCH 1 of 3] complibs/zlib: Add zlib support for binutils and gdb
Date: Thu, 24 Nov 2011 15:41:00 -0000 [thread overview]
Message-ID: <4ECE6509.2060106@rtems.org> (raw)
In-Reply-To: <CACgzC7ALdfvKKr7MKysYR4mBDtc3Zkyxtg3qQFuuNuw8CK_PXA@mail.gmail.com>
On 11/24/2011 08:20 AM, Zhenqiang Chen wrote:
> On 24 November 2011 15:10, Ralf Corsepius<ralf.corsepius@rtems.org> wrote:
>> On 11/24/2011 07:58 AM, Zhenqiang Chen wrote:
>>>
>>> On 24 November 2011 13:45, Ralf Corsepius<ralf.corsepius@rtems.org>
>>> wrote:
>>>>
>>>> On 11/24/2011 06:31 AM, Zhenqiang Chen wrote:
>>>>
>>>>> What's about canadian build for windows host?
>>>>>
>>>>> Do we have window version of zlib, expat and libiconv?
>>>>
>>>> Cygwin has all of these (c.f. ftp://cygwin.com/pub/cygwin/release)
>>>>
>>>> I am using these binaries to Canadian Cross build packages target Cygwin
>>>> on
>>>> Fedora (I am not using crosstools).
>>>>
>>>
>>> Yes. Cygwin has all the libraries. But for the binarytools, users can
>>> install and run on windows, not necessary on cygwin.
>>
>> You asked about Cygwin, ... Just unpackage these binaries into your
>> cross-toolchains sysroot and you're basically done.
>>
>> ... native Windows (or mingw) is a completely different (and much difficult)
>> topic.
>
> We want to support native Windows (or mingw).
Good luck.
The fundmental problem with mingw is it lacking a "complete distribution".
My approach to supplying Mingw packages is to use Fedora's
linux->mingw32 toolchain, which contains most packages/libraries one
needs for building mingw32 hosted cross-compilers Canadian-Cross
(I build mingw32->*-rtems* cross toolchain packages on Fedora).
The problem with this approach is on the Windows side. There one would
need a windows installer which would contain/collect the required dlls
etc. ... This is something I don't have.
Ralf
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2011-11-24 15:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 12:04 Zhenqiang Chen
2011-11-22 17:38 ` Yann E. MORIN
2011-11-23 20:17 ` Khem Raj
2011-11-23 20:54 ` Michael Hope
2011-11-23 21:01 ` Khem Raj
2011-11-23 22:00 ` Yann E. MORIN
2011-11-23 22:20 ` Khem Raj
2011-11-23 22:53 ` Michael Hope
2011-11-24 5:31 ` Zhenqiang Chen
2011-11-24 5:47 ` Ralf Corsepius
2011-11-24 6:59 ` Zhenqiang Chen
2011-11-24 7:13 ` Ralf Corsepius
2011-11-24 7:21 ` Zhenqiang Chen
2011-11-24 15:41 ` Ralf Corsepius [this message]
2011-11-24 20:35 ` Michael Hope
2011-11-22 17:50 ` Yann E. MORIN
[not found] ` <CACgzC7AnOW+umLpoD+Hwv1i1z_WF=rD2hJ7AJkWO-x86fHVMFg@mail.gmail.com>
2011-11-23 7:40 ` Yann E. MORIN
2011-11-23 8:23 ` Zhenqiang Chen
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=4ECE6509.2060106@rtems.org \
--to=ralf.corsepius@rtems.org \
--cc=crossgcc@sourceware.org \
--cc=zhenqiang.chen@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).