[Cmake] types.h

[Bill Hoffman]

Actually, the POSIX standard says that you have to use UNIX style slashes in 
c or c++ programs.   

So, #include <a/b>   
will always include file b in directory (or folder a) on both windows and UNIX.

You can not use windows style paths in c or c++ programs for #includes.
The "\" is an escape character.  So if you include a\b, it is a file called
a[backspace], since \b is the escape code for a backspace.

Anyway, this has nothing to do with not finding sys/types.h. 

-Bill


At 10:45 AM 9/20/2001 -0500, ebmiddlecamp at imation.com wrote:

>This is a "well known" problem in using code back and forth between Unix
>and Windows. In UNIX compilers, you can do an #include "a\b", and it will
>look in folder "a" for file "b". On Windows, it doesn't work for some
>reason. However, if you copy file "b" into its parent folder, and rename it
>to "a\b", it should work.
>
>Eric Middlecamp
>Imation Corp
>
>
>
>
>
>"Aaron Luttman" <aaron.luttman at esat.kuleuven.ac.be>@public.kitware.com on
>09/20/2001 06:50:38 AM
>
>Sent by:  cmake-admin at public.kitware.com
>
>
>To:   <cmake at public.kitware.com>
>cc:
>
>Subject:  [Cmake] types.h
>
>
>
>Greetings CMakers,
>    I just installed CMake on win2k  (to use with vc++6.0).  I attempted to
>compile a project (that was  previously compiling fine) with the native
>compiler, and I'm getting errors with  <sys/types.h>.  Did the CMake
>install play with my *.dll's in a way  that is causing issues?
>
>Help please,
>Aaron Luttman
>
>
>
>_______________________________________________
>Cmake mailing list
>Cmake at public.kitware.com
>http://public.kitware.com/mailman/listinfo/cmake