This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
On Fri, 21 Jun 2002, Alan Bishop wrote:
> I've built my cross compiler (ARM target) for Cygwin, and was wondering how
> to get a toolchain that can run on a straight Win32 system. Most Cygwin
> executables run as long as I put the Cygwin DLL on the Win32 machines, but I
> don't think it's that simple when the executables are cross compilation
> tools. Won't gcc crap out when it tries to read its spec file from a Cygwin
> file name?
I just tried a small experiment and it looks like it should work.
On cygwin
$ mount
C:\cygwin\lib /usr/lib system textmode
I run gcc -dumpspecs
On win32
mkdir \usr\lib
Copy \cygwin\lib\* to \usr\lib\*
copy gcc.exe and cygwin1.dll to \usr
cd \usr and run gcc -dumpspecs. This is the same as above. I suspect that
if you put all (whatever that means) your files under \usr you'll be
fine. You'll only have the problem that the drive won't be included in
the path.
--
Joel Coltoff
Perfection, then, is finally achieved, not when there is nothing left
to add, but when there is nothing left to take away.
-- Antoine de Saint-Exupery
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |