On 14/09/15 18:11, pozz wrote:> Just a final note on the VCS to use for a newbie as me. Most of you > suggested to avoid git for its complexity. It is true, I found some > difficulties to understand the concepts behind git.That's completely backwards. The concepts behind git literally couldn't be any simpler. It's the command-line interface, options and nomenclature that are difficult, they're just chaotic. Learn the git internal object model and everything else starts to make sense.
How to use VCS (git) to save output binary files
Started by ●September 10, 2015
Reply by ●September 14, 20152015-09-14
Reply by ●September 17, 20152015-09-17
The best way to deal with clutter is to not run your builds inside of a VCS repository. Use the lndir command to create a image of your repository and run your tools in there. For example if your repo is named foo. mkdir foo_cmp cd foo_cmp lndir ../foo . foo_cmp is an exact image of foo. The only difference is that where foo has the real files, foo_cmp will have symbolic links back to the real files. Run your build in foo_cmp. All generated files will stay in foo_cmp and never appear in foo. Your "make clean" routine only has to rm the foo_cmp directory and rebuild it. It's clean simple and less work than maintaining all those makefiles. John Eaton --------------------------------------- Posted through http://www.EmbeddedRelated.com







