From: Douglas AT dsteele DOT demon DOT co DOT uk (Douglas Steele)
Subject: Re: win32 popen clone for mingw32 anyone?
1 Aug 1998 19:19:20 -0700
Message-ID: <ucQLHDAVL0w1EwIc.cygnus.gnu-win32@dsteele.demon.co.uk>
References: <9807311933 DOT AA20575 AT modi DOT xraylith DOT wisc DOT edu>
Mime-Version: 1.0
To: gnu-win32 AT cygnus DOT com

In article <9807311933 DOT AA20575 AT modi DOT xraylith DOT wisc DOT edu>, Mumit Khan
<khan AT xraylith DOT wisc DOT edu> writes
>Here I'm referring to not being able to reproduce the bug where windres 
>can't create resource because the output from CPP goes to the screen.
>
>This is what happens:
>  
>  - windres calls the pre-processor via popen
>    * if --preprocessor flag is given, then it uses that; otherwise,
>    * use 'gcc -E -xc-header -DRC_INVOKED'
>  - windres now reads from the file descriptor returned by popen. All
>    output to stdout from the "popen'd" process should now go to this
>    file descriptor, but it seems to go to the CONSOLE according to this
>    bug.
>
>I couldn't reproduce it using crtdll.dll version 3.50; I'd be happy 
>provide others with my rewrite of Perl's popen/pclose routines to try 
>out.
If you have binaries I could try it out.

>Note that in the case where the default preprocessor is used, there are
>*two* levels of process creation -- windres calls gcc, and gcc calls cpp. 
>I suggest folks who're having this problem try the following:
>  
>  % windres --preprocessor cpp --define RC_INVOKED -o testres.o test.rc
>
>Before doing that, you'll have to add the directory containing cpp.exe to
>your path (or copy cpp.exe to somewhere in your path). Also, please try
>this on a trivial file with no extra includes to avoid adding lots of
>--include arguments.
>
>If this works
Unfortunately it still dumped to the screen.


-- 
Douglas Steele
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".