llvm dev - Jan 2006 - [LLVMdev] VS2005 patch

The project files need frequent updating.  I cannot maintain VS2005 
project files, so while they could be distributed with LLVM, they will 
become broken fast.  Also, VS2003 and VS2005 project and solution files 
cannot coexist in the same directories, further complicating matters.

Aaron Gray wrote:
> Hi Morten,
>
> If you can make the VS2005 project files availiable on the net then I 
> can test them as I have VS2005 now, so then with Chris'es okay then 
> they could be distributed with LLVM.
>
> Thanks,
>
> Aaron
>
> ----- Original Message ----- From: "Morten Ofstad" <morten at
hue.no>
> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu>
> Sent: Thursday, January 26, 2006 3:31 PM
> Subject: [LLVMdev] VS2005 patch
>
>
>> OK, fixed the problem with the intrin.h header that doesn't exist
in
>> previous versions of VS...
>>
>
>
>
--------------------------------------------------------------------------------
>
>
>
>> Index: lib/Target/X86/X86JITInfo.cpp
>>
==================================================================>> RCS
file: /var/cvs/llvm/llvm/lib/Target/X86/X86JITInfo.cpp,v
>> retrieving revision 1.14
>> diff -u -r1.14 X86JITInfo.cpp
>> --- lib/Target/X86/X86JITInfo.cpp 22 Jul 2005 20:49:37 -0000 1.14
>> +++ lib/Target/X86/X86JITInfo.cpp 26 Jan 2006 15:28:54 -0000
>> @@ -20,6 +20,11 @@
>> #include <iostream>
>> using namespace llvm;
>>
>> +#ifdef _MSC_VER
>> +  extern "C" void *_AddressOfReturnAddress(void);
>> +  #pragma intrinsic(_AddressOfReturnAddress)
>> +#endif
>> +
>> void X86JITInfo::replaceMachineCodeForFunction(void *Old, void *New) {
>>   unsigned char *OldByte = (unsigned char *)Old;
>>   *OldByte++ = 0xE9;                // Emit JMP opcode.
>> @@ -64,9 +69,6 @@
>>     "popl    %ebp\n"
>>     "ret\n");
>> #else
>> -  extern "C" void *_AddressOfReturnAddress(void);
>> -  #pragma intrinsic(_AddressOfReturnAddress)
>> -
>>   void X86CompilationCallback2(void);
>>
>>   _declspec(naked) void X86CompilationCallback(void) {
>>
>
>
>
--------------------------------------------------------------------------------
>
>
>
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>>
>
>
>
--------------------------------------------------------------------------------
>
>
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.375 / Virus Database: 267.14.22/239 - Release Date: 
> 24/01/2006
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
>

Jeff Cohen wrote:
> The project files need frequent updating.  I cannot maintain VS2005 
> project files, so while they could be distributed with LLVM, they will 
> become broken fast.  Also, VS2003 and VS2005 project and solution files 
> cannot coexist in the same directories, further complicating matters.
The VS2003 project files convert without problems -- you might want to add in a
property sheet (using the new property
manager) that defines _CRT_SECURE_NO_DEPRECATE, though. Actually the VS2005
project files are XML and not that different
from the VS2003 files, so just using CVS you will pick up any changes to the
VS2003 files. In conclusion there is no
need for separate VS2005 project files.

m.

_CRT_SECURE_NO_DEPRECATE is new for VS2005.  Nothing I can do with it in 
VS2003.

Morten Ofstad wrote:
> Jeff Cohen wrote:
>
>> The project files need frequent updating.  I cannot maintain VS2005 
>> project files, so while they could be distributed with LLVM, they 
>> will become broken fast.  Also, VS2003 and VS2005 project and 
>> solution files cannot coexist in the same directories, further 
>> complicating matters.
>
>
> The VS2003 project files convert without problems -- you might want to 
> add in a property sheet (using the new property manager) that defines 
> _CRT_SECURE_NO_DEPRECATE, though. Actually the VS2005 project files 
> are XML and not that different from the VS2003 files, so just using 
> CVS you will pick up any changes to the VS2003 files. In conclusion 
> there is no need for separate VS2005 project files.
>
> m.
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
>