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

revision controlling uvision projects

Hi, we use SVN for keeping track of our uvision projects.

We have an issue with the uvproj and uvopt files.

We keep them revision controlled as new developers need these files to work on a project, but these files get changed every time a new user opens them. They seem to have user specific settings. However this means that whenever we need to commit some code we need to make sure that we don't commit the uvproj and uvopt files which is an inconvenience.

I've worked with microsoft visual studio projects and they have required project files which do not change unless we modify project options (so we can keep these revision controlled), and then user specific files which aren't mandatory and don't need to be revision controlled(if these files don't exist they get created the first time the project is opened).

So I'm wondering which uvision files should be revision controlled?

Thanks in advance,
Alex

Parents
  • Some time ago I switched to makefile-based build system. I check in make.exe next to Makefile, so building the project is a matter of running "make" in the project directory. I only use the IDE for debugging. Setting up the IDE for debugging only takes a few mouse clicks, so I don't even bother to save the project files. For editor I use Source Insight - it is vastly superior to almost any IDE I know.

Reply
  • Some time ago I switched to makefile-based build system. I check in make.exe next to Makefile, so building the project is a matter of running "make" in the project directory. I only use the IDE for debugging. Setting up the IDE for debugging only takes a few mouse clicks, so I don't even bother to save the project files. For editor I use Source Insight - it is vastly superior to almost any IDE I know.

Children
No data