The .sln and .vcproj files are text files. You can open them
and edit them. I suggest saving a copy of your .vcproj, then
changing one file and saving, then running diff on the project
file. When done, write a perl script to apply the same change
for all files.
It is also sometimes possible to select more than one file and
make a change on many files at the same time in the property
pages. I don't recall whether this is one of those cases.
Cheers,
/ h+
-----Original Message-----
From: gam...@li...
[mailto:gam...@li...]On Behalf Of
Chris Raine
Sent: Monday, November 15, 2004 5:55 AM
To: gam...@li...
Subject: [GD-Windows] another devenv problem
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
|
