kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxxxx>]

On 11/13/2013 1:48 PM, Lorenzo Marcantonio wrote:
> On Wed, Nov 13, 2013 at 05:47:14PM +0100, Maciej Sumiński wrote:
>> Recently I wanted to play with build flags and I have noticed that they are
>> overwritten by CMakeLists.txt (see patch attached).
>> I am just wondering - is there any specific reason for that? Does anyone
>> mind appending build flags instead of setting them constant?
> 
> IIRC there are some issue with boost so they need to be tweaked for
> different parts of the build. It this where automake there would be no
> problem, but maybe cmake has its own reasons...
> 
> I don't really like cmake but unless it stops working that's fine for
> me:P automake/autoconf has other dark areas anyway so I think is only
> a question of choosing and suffering:P
> 
> Talking about playing with options: I tried an lto build and now (after
> the new boost patches/options/whatever) link fails with some mismatch
> between TLS and non-TLS in (guess what) wxString...  that class has to
> die. I think wxString alone would be a good reason enough to *not* use
> wxWidgets:D yes, glib string handling still is less painful
> 
Not too many folks would disagree with your wxString assessment.  Now
that wxWidgets 3.0 has officially been released, I think it's days are
numbered.  Until wxWidgets 3.0 becomes the default for most of the major
distros, we'll have to continue to support it.  My hope would be within
the next year or so but it all rests in the hands of the distro packagers.