another devenv problem

Chris Raine <[email protected]> Mon, 15 Nov 2004 14:54:42 +0100
Newsgroups gmane.games.devel.windows
Message-ID <[email protected]>
I have another devenv dilemma to add. 

I am currently supposed to port and maintain an old and large project
from unix to win32, which is working out suprisingly well with the new
studio 7.1 - except that *.cc files are still not fully supported.

I remember I had to set some registry values in devenv 6 to get it to
compile *.cc files - in devenv 7.1 it recognizes and compiles them
correctly, but I have to set the C++ project settings manually for every
single .cc file. 

With about 6 build configurations and >300 .cc files that is >300*6
settings pages I have to configure manually.

I have searched the web and asked coworkers and friends - with no
result, and if there is no solution, I will continue to beg for the
permission to massively rename the >300 .cc files to .cpp - or switch to
a different build-system like scons or jam and use makefile projects. 

Is there a way to convince devenv that .cc files are exactly the same as
.cpp files and it should treat them in exactly the same way?

-- 
regards, 
Chris Raine
signature.asc (application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBBmIJmc8D8qKhyZMoRArpKAJwLB3pBFb6TWvdQ0eMpIPx4o4VCjQCeMWsC
VbOAD0HCux4afHXCMx4bNnM=
=TQTn
-----END PGP SIGNATURE-----