[vlc-devel] [RFC] revision info causing rebuilding everything

Christophe Mutricy xtophe at chewa.net
Mon Feb 16 13:03:04 CET 2009

>> If generating a build tag interferes with regular development
>> then I would agree that the benefits do not outweigh the drawbacks.
>> It probably is less of an issue to build something
>> essentially equivalent into an automated build environment like, say, the
>> one providing the nightly builds.
> Last time they worked, nightly did not always rebuild everything either.
> Yet the build bots were already quite busy.

Yes and no.

The "continuous integration" i.e the ones built after every git push
just rebuild what's necessary. And that can get busy as three of the
buildslave are on altair when people are busy fixing bugs or commit on
master and 0.9-bugfix at the same time.
The "nightlies" which are available on http://nightlies.videolan.org
are built from a clean tree. their build time is less of a problem
becasue we can start them in a staggered maner and at a time of the
night where push by developers are unlikely (european night)

As we rebuilding every thing for the nightlies, for some OS there is a
sed on configure.ac to append the date (and time) after the -git in
the version number. So that the version inside vlc reflect the build
date of the nighly but also the packages have the date in their name
(.tar.bz2, .deb, .exe, ...)


More information about the vlc-devel mailing list