Nov 03, 2016
08:19 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nov 03, 2016
08:19 AM
Hi,
is there a how to for using DAVE together with an version control? I want to use SVN for version control and now the question is which files have to be added to the version control and which one are generated. Is there a descrition?
Thanks for Help
Fabian
is there a how to for using DAVE together with an version control? I want to use SVN for version control and now the question is which files have to be added to the version control and which one are generated. Is there a descrition?
Thanks for Help
Fabian
- Tags:
- IFX
2 Replies
Nov 07, 2016
02:59 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nov 07, 2016
02:59 AM
You can exclude the usual suspects Debug and Release.
You might also exclude "Dave" which contains the code generated by the apps (I haven't tried that)
You might also exclude "Dave" which contains the code generated by the apps (I haven't tried that)
Nov 07, 2016
07:10 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Nov 07, 2016
07:10 AM
For version control, I would grab everything in the project directory as well as the Dave, Libraries, and Startup folders. We also have a DAVE_modified directory where we tweak some of the XMC library files that I get as well. I skip .settings folder.
In the Debug and Release directories, I check in just the makefile and .mk files. This allows me to do automated/nightly builds without the DAVE IDE running. The script I have sets up the environment, runs make, and logs all output to a file. If you don't plan on anything like that, the Debug and Release can be skipped completely.
In the Debug and Release directories, I check in just the makefile and .mk files. This allows me to do automated/nightly builds without the DAVE IDE running. The script I have sets up the environment, runs make, and logs all output to a file. If you don't plan on anything like that, the Debug and Release can be skipped completely.