forwarding after a bad-reply-to failure :(
Hi, I'm not 100% sure of what you want. This mail supposes you need a native win32 version of cegcc (ie windows without cygwin). If not, I'm sorry. If you search on this mailing list archive you will find my own problems to get this. I tried to use msys to build it. There was lots of problems related to libiberty & al. My solution was to rebuild the compiler using a "canadian cross build" (awesome name, isn't it?), ie generate a compiler that - generates arm-wince-pe code (TARGET) - runs on mingw (i586-mingw) (HOST), - all of this done from a linux-i686 host (BUILD). yes, I see your eyebrows raised, but it works :-) As intermediary steps, you need : - a linux mingw compiler (it was in my default apt-get) - GMP/MPFR for i586-mingw (cross compiled from sources with the i586-mingw compiler in the previous step) - a linux cegcc to build the target libs from linux (use a tarball or build it). - very few changes are required to the build_mingw32ce.sh script. They are related to --with-gmp and --with-mpfr at the gcc configure, to give the script the correct location for the mingw versions of these libs. these changes may be useless when using the correct env vars, but I prefer long command lines. I also have a binary zip at http://www.unsads.com/~squalyl/cegcc/mingw32ce-4.1.zip<http://www.unsads.com/%7Esqualyl/cegcc/mingw32ce-4.1.zip>, but it's not an official build. It has previously helped a few people, though. Regards, Sebastien. On Wed, Dec 16, 2009 at 9:39 AM, Daniel Reimer <reimer.dan...@freenet.de>wrote: > Hi, > > I have a question regarding native Windows building of ceGCC. As some > ppl might know already, we added basic ARM Support to ReactOS a while > ago. Now I wanted to add ARM Build Support to RosBE, our Build > Environment by using ceGCC as Target Compiler. Well, I loaded the recent > Version and had to realize, its a cygwin Version. After some hacking / > researching I managed to provide it with all dlls its needs, but now I > have a nice Search Path Problem. *nix Paths vs Windows Paths... Now I > have two ways to get this done: 1. Try to fix the Search Paths of GCC by > using Environment Variables if there are any I can use without > interfering with the Host i386-mingw32 Compiler (Except LIBRARY_PATH and > /C_INCLUDE_PATH / /CPLUS_INCLUDE_PATH) or 2. Hope for a native Port from > you. > > Will there be one in the future and if yes, approximately when and if no > can you help me with fixing the Search Path Problem? We won't add a > fully bloated cygwin to our slim BE, which does a great job in Batch or > Powershell, I fear. > > Thx in advance > > Daniel Reimer > ReactOS Build Environment Developer > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Cegcc-devel mailing list > Cegcc-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/cegcc-devel >
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
