EDN Admin
Well-known member
Dear all,
I am developing a VC9 solution which contains multiple projects. All the .vcproj files of each project is generated by a Perl script instead of by VC9.
Under this scenario, I have encountered an issue which is that:
Sometimes, after the whole solution is built, I may have to update some new compile option to a project (ex. ProjectA). So I execute the Perl script re-gen all the vcproj files. I may only need to re-compile the sinle project
ProjectA and link others. But VC9 is trying to check and re-build all the objs and libraries even the .vcproj file is identical to previous one. This takes a huge time in "linking" phase.
This seems like VC9 re-compile all files if the obj/lib is older than .vcproj, is this assumption right?
Is there any option or setting which can help me disable VC9s check of the timestamp of all solution but only re-build the one I specified?
Thank you very much.
View the full article
I am developing a VC9 solution which contains multiple projects. All the .vcproj files of each project is generated by a Perl script instead of by VC9.
Under this scenario, I have encountered an issue which is that:
Sometimes, after the whole solution is built, I may have to update some new compile option to a project (ex. ProjectA). So I execute the Perl script re-gen all the vcproj files. I may only need to re-compile the sinle project
ProjectA and link others. But VC9 is trying to check and re-build all the objs and libraries even the .vcproj file is identical to previous one. This takes a huge time in "linking" phase.
This seems like VC9 re-compile all files if the obj/lib is older than .vcproj, is this assumption right?
Is there any option or setting which can help me disable VC9s check of the timestamp of all solution but only re-build the one I specified?
Thank you very much.
View the full article