/cppunit/examples/ contains a Visual C++ workspace
options file (examples.opt)
These files are intended to store per-user options
assciated with a workspace, and should not be added to
source control.
If I remember correctly, the .opt files also contains the
path of the programm to debug. All thoses path in
examples.opt should be relative to the project and therefore
reusable in any deployement.
I believe the capability of being able to run/debug project
such as 'simple_plugin' (test plug-in demo) out of the box
superseed by far the 'intended to store per-user options'.
Could you give a better rationnal while taking in account
the above element ?
(notes that the .opt will always be in CVS, we just don't
update it on every check-in).
Baptiste.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=196852
If I remember correctly, the .opt files also contains the
path of the programm to debug. All thoses path in
examples.opt should be relative to the project and therefore
reusable in any deployement.
I believe the capability of being able to run/debug project
such as 'simple_plugin' (test plug-in demo) out of the box
superseed by far the 'intended to store per-user options'.
Could you give a better rationnal while taking in account
the above element ?
(notes that the .opt will always be in CVS, we just don't
update it on every check-in).
Baptiste.
Logged In: YES
user_id=186473
OK, now I understand the motivation.
Generally, MS recommends that .opt files should not be
checked in:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs600/html/msdn_worksp.asp