[Cmake] MS Project dsp regeneration

[Bill Hoffman]

At 11:11 AM 1/14/2002 -0500, Miller, James V (CRD) wrote:
>I like this suggestion.  It makes sense to me that cmake should avoid overwriting the existing dsp if
>nothing "changed".

It would always run that rule because the .dsp files would never catch up.


>Does a DevStudio "Clean" wipe out the current dsp's in the workspace?

Yes, the clean wipes out all the dsp files.



>-----Original Message-----
>From: Amitha Perera [mailto:perera at cs . rpi . edu]
>Sent: Monday, January 14, 2002 11:02 AM
>To: Bill Hoffman
>Cc: cmake at public . kitware . com
>Subject: Re: [Cmake] MS Project dsp regeneration
>
>
>> 2. You could use the Clean and ReBuild all options on MSDeve without being
>> inundated with the "dsp file has changed on disk would you like to
>> reload?" questions.
>
>Couldn't you avoid this by actually writing the .dsp if and only if
>the contents change? For example, the DSPWriter could write to a
>temporary file, then compare the original with the new, and update the
>original only if necessary. This would give flexibility, so that you
>are prompted for reloading only when you've actually made a change
>that warrants reloading.
>
>Previously, a number of out users have run into "problems" because the
>DSP did not reflect the CMakeLists.txt. Being able to edit the file
>within VS, and having the change take effect immediately went a long
>way toward solving those issues.
>
>[ However, I don't develop under VS, so my opinion is probably not
>worth much. :-) ]
>
>Amitha.
>_______________________________________________
>Cmake mailing list
>Cmake at public . kitware . com
>http://public . kitware . com/mailman/listinfo/cmake