This is the mail archive of the
mailing list for the newlib project.
Re: Cross compiling Newlib for ARM in Cygwin
- From: Joel Sherrill <joel dot sherrill at oarcorp dot com>
- To: Rob Savoye <rob dot savoye at linaro dot org>, "Schwarz, Konrad" <konrad dot schwarz at siemens dot com>, "newlib at sourceware dot org" <newlib at sourceware dot org>
- Date: Wed, 23 Mar 2016 09:16:23 -0500
- Subject: Re: Cross compiling Newlib for ARM in Cygwin
- Authentication-results: sourceware.org; auth=none
- References: <A45B1767F1002449A37508C2CC6003D72DD106 at DEFTHW99EJ1MSX dot ww902 dot siemens dot net> <56F1691B dot 6050403 at cygwin dot com> <A45B1767F1002449A37508C2CC6003D72DDD95 at DEFTHW99EJ1MSX dot ww902 dot siemens dot net> <56F29C30 dot 3000800 at linaro dot org>
On 3/23/2016 8:37 AM, Rob Savoye wrote:
On 03/23/2016 06:22 AM, Schwarz, Konrad wrote:
Most of us that build cross compilers for Win32 based systems use
Mingw to built it on a Linux host. Mingw is the console version, an
doesn't need any Cygwin libraries at all. They'll run just fine under
Cygwin as well. If you want to be lazy, you can grab my binary tarballs
for Windows from here:
Rob.. we are finalizing having RTEMS cross-tools built under MSYS2
and actually being able to build them natively on Windows.
What do you recommend at the install prefix when they are Mingw/MSYS2
binaries? Do you just put them at a Windows rooted path and use
/cygdrive/c/... to reference them from Cygwin?
FWIW when building natively under Windows, we have hit the maximum
path limit with at least binutils. There are some other flaky issues
we are trying to resolve.
Just curious what the best practice is.