The new property manager doesn't exist in VS2003 either. Don't know where to add it. Chris Lattner wrote:> On Fri, 27 Jan 2006, Jeff Cohen 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 at cs.uiuc.edu http://llvm.cs.uiuc.edu >>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >>> >>> >>> >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> > > -Chris >
On Fri, 27 Jan 2006, Jeff Cohen 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>> On Fri, 27 Jan 2006, Jeff Cohen 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 at cs.uiuc.edu http://llvm.cs.uiuc.edu >>>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >>>> >>>> >>>> >>> >>> _______________________________________________ >>> LLVM Developers mailing list >>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >>> >> >> -Chris >> > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >-Chris -- http://nondot.org/sabre/ http://llvm.org/
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:> On Fri, 27 Jan 2006, Jeff Cohen 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 > >>> On Fri, 27 Jan 2006, Jeff Cohen 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 at cs.uiuc.edu http://llvm.cs.uiuc.edu >>>>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >>>>> >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> LLVM Developers mailing list >>>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >>>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >>>> >>> >>> -Chris >>> >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> > > -Chris >