kicad-developers team mailing list archive

[Mário Luzeiro <mrluzeiro@xxxxx>]

I manage to change the common/CMakeLists.txt Line 122:
# Generate version header file.
and comment that function add_custom_target

So it will not change the header..

Mario
________________________________________
From: Kicad-developers [kicad-developers-bounces+mrluzeiro=ua.pt@xxxxxxxxxxxxxxxxxxx] on behalf of jp charras [jp.charras@xxxxxxxxxx]
Sent: 21 November 2015 19:54
To: kicad-developers@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Kicad-developers] "generate version string header"

Le 20/11/2015 21:56, Wayne Stambaugh a écrit :
> On 11/20/2015 3:08 PM, Mário Luzeiro wrote:
>> Hello all,
>>
>> I am building kicad on windows msys/mingw32
>> Everytime I update (pull) my development bzr branch it will  "generate version string header" and rebuild all kicad. :S
>
> It should only rebuild when there is a commit change to your branch.
> Even when it does change, it should only update the version string,
> recompile the common library, and relink all of the binaries to the
> updated common library.

This is true on Linux, but unfortunately, not on Windows:
Each time the bzr version has changed a full compilation of all files in
Kicad sources is made.


 This is the normal behavior to ensure that the
> version string matches the repo version.
>
>>
>> Is there anyway to flag to skip this step?
>
> You could force it by setting KICAD_BUILD_VERSION during configuration,
> then the version string will always be what was defined.  If you send
> bug report, the version info copied from the Help->Copy Version
> Information will be incorrect.  You really shouldn't do this if you
> don't need to.  This option is for stable release builds.
>
>>
>> Thanks!
>> Mario


--
Jean-Pierre CHARRAS

_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp