* Compiling gcc for cygwin, still expects DOS paths.
@ 2004-01-19 1:54 Ben Bodley
0 siblings, 0 replies; only message in thread
From: Ben Bodley @ 2004-01-19 1:54 UTC (permalink / raw)
To: gcc-help
Hello,
I have searched and trolled the net to find the answer to a problem I am
having building a cross-compiler for arm under cygwin.
I am wanting to develop applications for Symbian (EPOC) using gcc in a
cygwin enviornment. I am using the Symbian supplied sources and patches for
gcc (No symbian specific source is patched, just a certain combination of
standard gcc patches from GNU).
I am using:
./configure --host=i686-pc-cygwin32 --build=i686-pc-cygwin32 --prefix=/opt/s
ymbian/UIQ_21 --target=arm-epoc-pe
Then building and installing with no problems.
I try and compile an application however and:
$ arm-epoc-pe-g++ dialog.cpp -I/opt/symbian/UIQ_21/include
In file included from dialog.cpp:1:
dialog.h:3: No include path in which to find eikdialg.h
dialog.cpp:6: No include path in which to find eikchlst.h
However, if I use DOS pathnames in my include directory:
$ arm-epoc-pe-g++ dialog.cpp -Ic:/cygwin/opt/symbian/UIQ_21/include
In file included from c:\cygwin\opt\symbian\UIQ_21\include\e32std.h:1305,
from c:\cygwin\opt\symbian\UIQ_21\include\coeccntx.h:10,
from c:\cygwin\opt\symbian\UIQ_21\include\eikdialg.h:10,
from dialog.h:3,
from dialog.cpp:1:
c:\cygwin\opt\symbian\UIQ_21\include\e32des16.h:301: #error no typedef for
__TText
What have I done wrong?? I would prefer makefiles I create to be "generic"
between Linux and Windows (ie. no c:\ everywhere). I was under the
impression that anything built under cygwin understood unix paths.
Thanks for any insights here guys.
Cheers,
Ben
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-01-19 1:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-01-19 1:54 Compiling gcc for cygwin, still expects DOS paths Ben Bodley
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).