Dear Duncan, In your document "readme.packages.txt" you have a very helpful chapter on "Using Visual C++". Please allow me to ask you one question: Why do you propose the option "/MT" instead of option "/MD"? (To my knowledge usually option "/MD" is used when compiling programs with VC++.) Best regards Christian _._._._._._._._._._._._._._._._._._ C.h.r.i.s.t.i.a.n S.t.r.a.t.o.w.a V.i.e.n.n.a A.u.s.t.r.i.a e.m.a.i.l: cstrato at aon.at _._._._._._._._._._._._._._._._._._
On 15/10/2009 5:01 PM, cstrato wrote:> Dear Duncan, > > In your document "readme.packages.txt" you have a very helpful chapter > on "Using Visual C++". > Please allow me to ask you one question: Why do you propose the option > "/MT" instead of option "/MD"? > (To my knowledge usually option "/MD" is used when compiling programs > with VC++.)I didn't write that: I've got no experience with VC++. It was Brian Ripley who wrote it, and the log says he wrote it in 1999. So I'd guess that it isn't bad advice (having lasted 10 years without a change), but I guess it's possible that it is no longer optimal. Duncan Murdoch
On Oct 15, 2009, at 17:01 , cstrato wrote:> Dear Duncan, > > In your document "readme.packages.txt" you have a very helpful > chapter on "Using Visual C++". > Please allow me to ask you one question: Why do you propose the > option "/MT" instead of option "/MD"? > (To my knowledge usually option "/MD" is used when compiling > programs with VC++.) >Have you read the MS docs? They have different purposes - /MD pulls in MSVCR which may not be what you want (depending on your code), /MT just says that you want thread-safe libs. The fact that something is "usually" used is not necessarily a very good indicator -- it's better if you know what you're doing ;). Cheers, Simon