RE: [GD-Windows] another devenv problem

[Lewin, G. <gl...@ea...>]

Well you could create a master .cpp file, #include all the .cc files in
it, and make all of them non-build files. It will work, and as a side
issue it will improve you build speeds.

_________________________________________
Gareth Lewin - http://www.garethlewin.com

"Facts are useless. You can use facts to prove anything that's even
remotely true. Facts shmacts!" -- Homer Jay Simpson.=20

> -----Original Message-----
> From: Chris Raine [mailto:c....@gm...]=20
> Sent: Monday, November 15, 2004 4:11 PM
> To: gam...@li...
> Subject: RE: [GD-Windows] another devenv problem
>=20
> On Mon, 2004-11-15 at 18:35, Jon Watte wrote:
> > The .sln and .vcproj files are text files. You can open=20
> them and edit=20
> > them. I suggest saving a copy of your .vcproj, then=20
> changing one file=20
> > and saving, then running diff on the project file. When=20
> done, write a=20
> > perl script to apply the same change for all files.
> >=20
> > It is also sometimes possible to select more than one file=20
> and make a=20
> > change on many files at the same time in the property=20
> pages. I don't=20
> > recall whether this is one of those cases.
> >=20
> > Cheers,
> >=20
> > 			/ h+
> >=20
>=20
> I had also thought about writing a perl script, which parses=20
> the devenv project files. But my perl-foo is too limited to=20
> do such a task. And maintaining another piece of crypto-code=20
> for every new devenv release (this unix code is going to=20
> stick with us for a while) .... yuck.
>=20
> I guess either living with the second solution (that actually=20
> works - I feel quite stupid now), or going for SCons=20
> (www.scons.org) or this boost-jam seems the only way to go.=20
>=20
> Thanks for the tip.
>=20
> --
> regards,
> Chris Raine=20
>=20
>=20