search for: build_log

Nice, very well done on the CMake build. This command worked perfectly: cmake -G "Visual Studio 8 2005" -DCMAKE_CXX_FLAGS="-D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_SECURE_NO_DEPRECATE -D_SECURE_SCL=0 -D_SCL_SECURE_NO_DEPRECATE -D_HAS_ITERATOR_DEBUGGING=0" ..\trunk > ..\build_log.txt And for the actual build, went very well. The INSTALL was much project was better then I was expecting (although did not install to a place I wanted it to, I guess that can be changed with another option passed to the above command-line call). No errors in the build, and the only real warnin...

Hello, there seems to be an odd behaviour regarding the CD-Rom drives in wine depending on whether you run a precompiled version (in my case a Debian package) or compile wine for yourself (same version). Background is that there seems to be a regression in wine which I wanted to debug. The regression is in a game which checks for the CD first and then shows an intro and a menu (which has

On Mon, Nov 24, 2008 at 10:13 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: > /* snip */ Thanks so much for that information. :) For note, this is my usual line I add to the end of my preprocessor definitions in *every* single project I ever open now (thanks to some very bad memories associated with not having them).

"Cory Nelson" <phrosty at gmail.com> writes: > On Mon, Nov 24, 2008 at 8:18 PM, Óscar Fuentes <ofv at wanadoo.es> wrote: >> OvermindDL1 <overminddl1 at gmail.com> writes: >>> As long as instructions are supplied on how to pass in user defined >>> macros to the build system. I have to turn off a lot of the extra >>> safety crap that

I thought I had all the tools I needed for this, but it seems something is missing. When I build the 2.6.18-8.1.3 kernel from source, I get this error: extracting debug info from /var/tmp/kernel-2.6.18-8.el5.trace-root/usr/src/kernels/2.6.18-8.el5.trace-x86_64/scripts/conmakehash extracting debug info from