This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

how to put uVision project files under source control

Hello,

has anybody a good solution how to put the uVision project files under source control?
We only want to store the information that is absolutely neccessary to rebuild the objects. We do not need
informations how windows are placed - since this may be different from developer to developer and every time one checks in the project files get also checked in though nothing really has changed ...

Parents Reply Children
  • No, this has nothing to do with building!

    The .opt file records what files were open, and the positions of their windows.

    The .uv2 file can use relative paths, so the project doesn't have to be always checked-out to an identical path, but the .opt file uses fully-qualified paths - so if someone checks the project out to a different path, you get a "cannot find file" message for each window it tries tp re-open.
    But this doesn't affect building - only the attempt to "re-open" the files that were last open.

    Hence, of course, if there are no files open when you check-in, the problem doesn't arise!

    Note that I never use the "integrated" source control - I always keep it separate.
    Dunno if that has any effect...?

  • No, this has nothing to do with building!

    True, but that is not what I meant: I was under the impression that project files are saved only after closing a project. thus, if one creates dependencies into C modules that are not part of the project files when the check-in is done, there is a problem.

  • No, that is not the case!

    The project files are updated immediately the change is made.

    IMO, this is a very BAD feature - because it means that there is no way to discard changes made to the project!!