Mail Archives: cygwin/2002/12/11/22:31:00
Kun,
The PATH environment variables is used only to find executables and the DLL
(dynamically linked libraries) those executables require.
Include files required during C or C++ compilation are located via a
separate search path maintained by the compiler and not driven by any
environment variable, at least not in the Cygwin compiler, which is GCC.
You'll probably need to learn about the conventions and rules of C
programming and compilers (and related tools such as "make") in order to be
able to generalize the build scripts you're using.
By the way, is this the same CLDC whose home page is
<http://java.sun.com/products/cldc/>? If so, are you also building the KVM
yourself? If not, is the KVM also built with GCC? If these two components
are not going to be built with the same compilers, then you must verify
that the compilers' ABIs (application binary interfaces) are compatible, or
the CLDC native library you're building will not be usable from the KVM.
It is a certainty that a Java Native Interface library built using GCC will
not be able to be accessed from the Sun JVM for Windows.
Also, just to be pedantic, it's "Cygwin," not "CygWin."
Randall Schulz
Mountain View, CA USA
At 19:08 2002-12-11, Wu Kun wrote:
>Hi, all:
>
>When I use CygWin 3.17.1 to build Sun's CLDC 1.0.x, an error occurs:
>
>../../src/check_class.c(30) : fatal error C1083: Cannot open include
>file: 'ctype.h': No such file or directory
>
>But the file "ctype.h" is right in the /usr/include, which has been set
>in the $PATH.
>
>
>Can some body help me out ?
>
>Best Regards
>
>Wu Kun
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -