"Nelson B. Bolyard" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > Jamie Nicolson wrote: > > I think the makefiles will only work in environments that > > silently convert slash to backslash--this probably means you need a UNIX > > emulation package such as cygwin or MKS. > > AFAIK, MKS does not ever "silently convert slash to backslash". > The only time that I have found a forward slash to be an issue is when > it comes at the beginning of a path (i.e. an absolute path) in a command > line argument. Some progams interpret the leading slash as unix interprets > a dash. Using relative paths, or using a drive-letter-colon prefix > solves this problem. (e.g. if /project/include causes an error, then > c:/project/include will probably work.)
Thanks Nelson, I solve my path problem by changing my UNIX emulation package to the cygwin one. Now I have another problem: C compiler seems to search a types.h from secport.h, but it don't find it because the file doesn't exist. Here is the output message: ../../../../../../dist/public/security\secport.h(83) : fatal error C1083: Cannot open include file: 'types.h': No such file or directory What's wrong ?
