Right, I wasn't able to find iostream among the available headers (remember, I'm not linking yet).
Stefan, are you suggesting that I install microsofts tool-chain and compile the code with the ms compiler? Sounds reasonable. I'm not sure what you mean by PE .exe, though. I have no need to link to Linux libraries, other than this is a pure windows codebase and some of the libraries referenced are not available in winelib/msvcrt. Thanks, Rino On Mon, Jan 19, 2009 at 11:37 PM, Damjan Jovanovic <damjan....@gmail.com> wrote: > On Tue, Jan 20, 2009 at 2:23 AM, Stefan Dösinger <ste...@codeweavers.com> > wrote: >>> Yeah, it looks like there's some conflict with iostream and msvcrt: >>> http://www.mail-archive.com/wine-devel@winehq.org/msg08834.html >>> >>> I'm trying to follow the recommendations, but without much luck. >> Maybe try to use the iostream implementation from msvcrt(not sure how to do >> that, though - I never used winelib myself) >> >> Is there any reason why you have to compile the app using winelib? Unless >> you want to link against Linux libraries in your app there is no advantage >> over compiling the application as a PE .exe file(same performance, same >> runtime requirements etc). If you compile it as native .exe you avoid all >> the issues where Linux headers collide with Windows headers. >> > > I thought that Wine's msvcrt didn't have any iostreams yet (#11910, #6457)? > > Damjan > > >
