-
All of the Perforce-related tasks in NAntContrib neglect to use the 'port' paramater value (member of P4Base class) that can be supplied by NAnt build files. Tasks such as , , etc. all use *only* the default/current (i.e. set in your environment) setting for the port. This patch corrects all such fauty task implementations.
2009-04-07 04:49:28 UTC in NAntContrib
-
Logged In: YES
user_id=550130
I have the same errors (RedHat 8 system). I managed to get
past these particular errors by doing the following:
1) Change all occurances of 'RAM' to 'emulator->RAM' in
defines.h
2) Change all occurances of 'MapperInit' to
'emulator->MapperInit' in emulator_x86.c
3) Change all occurances of 'Mapper' to 'emulator->Mapper'
in emulator_x86.c
All...
2003-05-14 03:24:59 UTC in TuxNES
-
Logged In: YES
user_id=550130
That's what I figured, too (the "wouldn't work with VC6 either"
comment, not the "because he's lonely" part ;-)
We were compiling/linking/using 2.1 with VC6 just fine -- no
clue why it would be broken in VC7 (BTW, always using the
GUI, never the cl.exe or msdev.exe/devenv.exe from the
command line). Perhaps the VC6->7 project...
2002-06-05 23:48:44 UTC in Python
-
Extension modules (_sre, _socket, etc.) do not have
their entry points exported correctly when building
Python (2.1 onwards) with Microsoft Visual C++ 7
(part of Visual Studio .NET). (NOTE: Everything
compiles and links without errors. It's just the
exports that are missing.)
Think through the prepocessor flow when compiling
_sre.c, for example, the following happens (this is...
2002-05-21 00:18:52 UTC in Python
