VS2005 patch

OK, fixed the problem with the intrin.h header that doesn't exist in previous versions of VS...

JIT.patch (974 Bytes)

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

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:

applied, thanks!
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060123/031225.html

-Chris

Remaining patches applied:

http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060123/031235.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060123/031236.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060123/031239.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060123/031238.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060123/031237.html

Chris Lattner 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.

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

Morten Ofstad wrote:

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

It shouldn't hurt to define it though, even if VC2003 where it does nothing. Right?

-Chris

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@cs.uiuc.edu http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

_______________________________________________
LLVM Developers mailing list
LLVMdev@cs.uiuc.edu http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

-Chris

The new property manager doesn't exist in VS2003 either. Don't know where to add it.

Chris Lattner wrote:

The new property manager doesn't exist in VS2003 either. Don't know where to add it.

Isn't there a place to add -D_CRT_SECURE_NO_DEPRECATE for the preprocessor? Isn't this all we are talking about, or am I missing something?

-Chris

I don't know. If that's all it was, why is there a special new property manager to set it? Morten will need to explain what to do in VS2003 to make VS2005 happy.

Chris Lattner wrote:

Hello Jeff,

Done. I have no way to verify that it has the desired effect in VS2005, but it has no effect as far as I can tell in VS2003 (as to be expected).

Oleg Smolsky wrote:

Jeff Cohen wrote:

I don't know. If that's all it was, why is there a special new property manager to set it? Morten will need to explain what to do in VS2003 to make VS2005 happy.

Sorry I made this confusing... I was just talking about what someone who has their own project files for VS2005 would do, the property manager is a new feature that allows you to make 'property sheets' (basically a set of compiler options) that you can add in as defaults for the projects in your solution. That way you can keep any 'extra' settings in one place so you're less likely to get a conflict when you update from CVS.

When that is said, it wouldn't hurt to just define _CRT_SECURE_NO_DEPRECATE in the VS2003 project files. It would make life even easier for someone using VS2005...

m.