Following on from the heightened interest in unit-testing at my workplace I had a tinker with some software at the weekend. I figured that if I wanted to start some unit-testing it would be good to have a place to keep all my code as well as having a nice command-line tool to build them. I didn't fancy using nmake for the latter and was quite keen to learn about writing makefiles.
The first was a source-control repository for me to use and I was happy to find that Perforce is free for limited use. I downloaded and configured it and was soon happily using it to create my own depot and check stuff in and out. The rest of my time was spent installing and configuring Jam.
I'd seen the contents of Visual Studio-generated make-files before and remember thinking they looked a little daunting. Jam is an alternative to the 'make' tool (or if, like me, you develop mainly using MS Visual Studio, the 'nmake' tool). It's part of Perforce Software's suite (although you download it separately to their SCM) and I elected to sync to the latest beta build direct from the Perforce Software public depot. It came down as source so I had to build it (using nmake) first.
After all that I didn't really get a chance to use either tool in anger.
No comments:
Post a Comment