Actually, I think it should be -no-cpp-precomp, sorry if I goofed. Anyway, as far as I am aware, it turns off precompiled c++ header support. At times while I was struggling with getting this to build, I was getting warnings about not being able to deal with those, so I added that to get rid of that problem. You are correct, I do not think that it is necessary, at least as far as gcc 3.1/OSX 10.2 is concerned.
-Jason
Wei Dai wrote:
On Wed, Feb 19, 2003 at 07:55:31PM -0500, Wei Dai wrote:
That's great. I would like to fold the changes into the current c50-fixes
branch and make sure the fixed code will still compile on other platforms. Can anyone give me access to an account on a MacOS X machine with gcc 3.1
installed for testing purposes?
Thanks to Adam Dershowitz, I was able to confirm the fixes and merge them into CVS. A patch is now posted on the Crypto++ web site. People who have MacOS X, please download it and try it out.
One question for Jason: -cpp-no-precomp doesn't seem to be needed in order to compile Crypto++, so I took it out. What is it for?
-- /******************************************************************************
Jason Arnold / Sandia National Laboratories
jdarnol @ sandia . gov / (925) 294-3693******************************************************************************/
