My Account account_circle

I previously explained the basics of our build system for SmartInspect. This part goes further and tells more about the technical details.

As mentioned, we just need to enter the `make’ command to start a new build. Make is a tool for automated builds created and maintained by the GNU project. The input for make is a set of Makefiles. Those Makefiles specify the tasks to execute and their order. One advantage of make is that it’s very flexible and powerful with the drawback of being quite complex sometimes. If you are interested in using make, there are a lot of good tutorials to get started.

To return to our build system, once you start the initial make command, the current source tree is checked out of our subversion repository by using the subversion command line client. Then make changes into the working directory and starts the actual build.

At first, the internal build number is incremented and the resource files are dynamically created and compiled. It goes on by compiling all necessary binaries, like the different versions of the Console or the libraries, and by creating the online help and API documentation. The resulting binaries and some other files are then copied to a `dist’ directory before the setup compiler packages them into the different installation programs. Then the build completes by executing the test suites of the libraries and creating the test packages I already talked about.

How useful was this post?

Click on a star to rate it!

Stay ahead in Test Management.

Follow us on social media!

Help us improve this page!

What problem are you trying to solve?