Windows nightly build


There is no nightly builds for about a week, any idea when it will be back?

btw just came to know KiCad 4.0.3 Stable has been released and I thought it will include the new features like 3D viewer etc etc…but did’t mentioned in the change log. Does anybody tried the new stable release?

4.0.3 is bug fixes only, none of the new features.
Nightlies is having Windows build problems

1 Like

The no nightly builds thing does suck…
I’ve been trying to build them this entire week with no success in any of my tinkering.
It’s also undergoing a lot of under-the-hood stuff, and so it’s expected that there will be more failures.

At the moment the latest Windows nightly build is r7176:

But the latest Windows debug build is r7255:

Does anyone know if Windows nightly builds will be update to the latest revision soon?

What makes you think debug and nightly version numbers are related?

As far as I remember the nightlies are more or less automated builds that happen every couple of days.

I think some new features are incoming (Kicad2STEP), after debugging and testing it will be released to the product branch aka nightlies it seems.

Because they are :wink:
For example compare these file names:

Having different release numbers for debug and nighties would raise havoc in bug reporting.


This is not really related with the original event, but it seems that I forgot to actually enable the build when renaming stuff almost two weeks ago. IIRC the latest build do contain the STEP export, but I am actually not sure.

Anyways, the builds have been fixed, so a new build should appear tonight.

1 Like

Well, nighties are nighties - autocompiled latest versions from Git. As long as there are no compilation errors a nighty build is considered OK.

Many thanks, I’ll check it out!

Mea culpa @cioma, one never stops learning. :flushed:

@nickoe, I don’t know if intentional or not, but the last nightly (7176) I downloaded a couple of days ago does report like this on Win7:

Is that intentional?

I believe those hexadecimal numbers are related to the last git commit this release was generated from.
E.g. compare this file name:
And this commit:

It seems hex number in the file name is matching first digits of the Git commit ID.

Yeah sure, but the nightlies before that had the BZR/version instead of the hex number there… just wanted to point that out, as when I tried to get the 7176 number from that KiCAD instance I couldn’t find it. It’s always showing the hex number instead of the version number…

Or via the 'copy version number button:

Application: kicad
Version: (2016-09-17 revision 679eef1)-makepkg, release build
Libraries: wxWidgets 3.0.2
libcurl/7.46.0 OpenSSL/1.0.2d zlib/1.2.8 libidn/1.32 libssh2/1.6.0 librtmp/2.3
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW

  • Build Info -
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.57.0
    Curl: 7.46.0
    KiCad - Compiler: GCC 5.2.0 with C++ ABI 1009

I agree, it would make sense to also have decimal revision number shown in the KiCad “About” window.

It did before… I made a jump from 6971 to 7176, so somewhere between something changed… @nickoe probably knows what and can fix if deemed necessary :wink:

Yeah, that is an upstream change, not related to the windows builds specifically, so it is intentional.

So it’s 7 digit hex from here on, cool I guess :cry:

Would it be possible to have the letters show as uppercase, ie. 679EEF1 for faster recognition, or is that just me? :hushed:

1 Like

No upper case. Use the date to get relative versions, but be awere it is currently the build date and not commit date.

1 Like

It’s not just you. I am more likely to recognize hex numbers as such when they are represented as upper-case characters.


Maybe not everyone is aware - KiCad developers have switched source control from Bazaar to git (on Launchpad). Bazaar has traditional style revision numbers, therefore BZR7155 etc. Git does not have any concept of revision number, only commits which are tagged with a 160 bit hash value which are globally unique.

The git hash can be shortened to a few characters which is unique enough to identify a commit, but is essentially a random number. This is useful for developers but has little meaning to users.