From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6627 invoked by alias); 27 Apr 2009 11:48:57 -0000 Received: (qmail 6617 invoked by uid 22791); 27 Apr 2009 11:48:57 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mail-fx0-f162.google.com (HELO mail-fx0-f162.google.com) (209.85.220.162) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 27 Apr 2009 11:48:52 +0000 Received: by fxm6 with SMTP id 6so2699493fxm.24 for ; Mon, 27 Apr 2009 04:48:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.240.5 with SMTP id s5mr3103696mur.106.1240832928422; Mon, 27 Apr 2009 04:48:48 -0700 (PDT) In-Reply-To: <200904262303.34489.yann.morin.1998@anciens.enib.fr> References: <3efb10970904261357j316e15abp726d7dac52f8710e@mail.gmail.com> <200904262303.34489.yann.morin.1998@anciens.enib.fr> Date: Mon, 27 Apr 2009 11:48:00 -0000 Message-ID: <3efb10970904270448j51e75d37q3df4d63ffcf3e4ad@mail.gmail.com> Subject: Re: using crosstool ng for building win32 hosted cross compiler From: Remy Bohmer To: "Yann E. MORIN" Cc: crossgcc@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact crossgcc-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: crossgcc-owner@sourceware.org X-SW-Source: 2009-04/txt/msg00074.txt.bz2 Hello, Thanks for your answer. >> I am currently using crosstool-ng to build a cross-toolchain for my >> target (target=3Dx86-bare, host=3Dx86-linux, build=3Dx86-linux) >> Now I also need the same toolchain that can run on a Windows host >> (target=3Dx86-bare, host=3Dx86-mingw, build=3Dx86-linux) > > That's a canadian-cross, and crosstool-NG does not yet handle this > case. I know... not yet! > > But it should be fine with: > =A0host=3Dx86-mingw, build=3Dx86-mingw, target=3Dx86-bare And this is what I wanted to prevent.... I prefer building on Linux, one build system for all platforms and tools; usually cross-compiling Linux stuff on a Windows box is just pain. Unfortunately there are application engineers that are addicted to Windows for whom I need a cross-compiler, so let's try to build one on Linux... I did it before (a few years ago) with my own set of dirty scripts which needs severe update. So I wanted to get it all going inside crosstool-ng. Back then I did it with first building the linux hosted toolchain, and finally replace every executable by its Windows counterpart by only building binutils and gcc for mingw. I was wondering if such a route was still possible, and if so: how to integrate that in crosstool-ng? > Also, please note that 1.4.0 can now be used under Cygwin. > If you can't build under mingw, then maybe Cygwin would be a good > fallback/workaround... Cygwin compiles slower and is annoying if make tooling is used that works outside the cygwin environment (and that do not understand the cygwin path-naming). >> Is there an lightweight way possible to make crosstool-ng build only >> the win32 executables by using a mingw cross-compiler, and using the >> linux-hosted-toolchain-build-results as starting point? If so, where >> in the build process ct-ng performs could this be added? >> I guess, as mingw cross-compiler the i586-mingw32msvc-gcc from Ubuntu >> can be used... > > Unfortunately, canadian-cross is not yet supported. I know it is not supported, and I wanted to do something about the 'not yet' part... > I don't have enough > time to test it, but most of the infrastructure should already be here. > Most probably, a matter of: > - set "Paths and misc options" --> "Experimental" (to see next option) > - set "Toolchain options" --> "Type" --> "Canadian" > - set "Toolchain options" --> "Host system" --> "Tuple" If I start using it, crosstool-ng complains about 'no-code' So, where to start to implement it nicely? > This will be like hunting for a dear treasure in a dungeon full of traps > and monsters, with only a one-hand sword, a few spells and a lot of good > will. May the dice be with you! That is what compiling glibc on Windows inside mingw is as well ;-) (Unless you walked that road before) Kind Regards, Remy -- For unsubscribe information see http://sourceware.org/lists.html#faq