Message-Id:	<199809281801.OAA26299@indy.delorie.com>
Comments:	Authenticated sender is <mert0407 AT sable DOT ox DOT ac DOT uk>
From:	"George Foot" <george DOT foot AT merton DOT ox DOT ac DOT uk>
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Date:	Mon, 28 Sep 1998 18:58:47 +0000
MIME-Version:	1.0
Subject:	Re: DJGPP and windows?
Reply-to:	mert0407 AT sable DOT ox DOT ac DOT uk
CC:	djgpp AT delorie DOT com

On 28 Sep 98 at 19:07, Eli Zaretskii wrote:

> On Mon, 28 Sep 1998, George Foot wrote:
> 
> > The problem isn't with these files, it's with other libraries
> > such as libc, libm and libg, of which RSXNTDJ provides its own
> > copies of course.  In addition, I thought it would be better to
> > prevent people from linking any DOS-djgpp libraries into
> > Windows programs.  stdcxx would be an easy library to link in
> > by accident, using gxx.  I'm not sure, but linking DOS
> > libraries into Windows programs doesn't seem very safe to me.
> 
> Sounds like a good reason to have a separate driver, don't you think?  If 
> people where to use wingcc or some such, then you could make wingcc.exe 
> that's a symlink to gcc.exe, and have a separate section in DJGPP.ENV 
> that redefines all variables like INCLUDE_PATH and LIBRARY_PATH to point 
> to RSXNT directories.
> 
> Will this solve the problems?

Probably. :)  I think that's an excellent solution, I'll make
it so.  There remains another slight problem, which is that the
resource compiler `grc' calls the C preprocessor directly, and
sometimes resource scripts need to include Windows header
files.  I can fix this (and other problems such as missing
`bin/cpp.exe') by rebuilding grc to use the gccwin.exe instead.

Thanks for your help.

-- 
george DOT foot AT merton DOT oxford DOT ac DOT uk

- Raw text -