kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

On 3/21/2016 3:10 PM, jp charras wrote:
> Le 21/03/2016 19:54, Nick Østergaard a écrit :
>> 2016-03-21 19:52 GMT+01:00 jp charras <jp.charras@xxxxxxxxxx>:
>>> Le 21/03/2016 16:13, Wayne Stambaugh a écrit :
>>>> Going, going, gone!  Since I haven't gotten any objections, I committed
>>>> the patch to enable C++11.  Thanks Simon for the patch but be prepared
>>>> for the grumbling. :)
>>>>
>>>
>>> On Ubuntu 14.04 LTS - 64 bits (with latest update) I have an issue when
>>> compiling pcbnewPYTHON_wrap.cxx.
>>
>> I guess this is because wxpython is missing on 14.04.
> 
> No.
> I am able to build Kicad with option -DKICAD_SCRIPTING_WXPYTHON=ON.
> The issue is not related to wxpython.
> I also have this issue when I use only the option -DKICAD_SCRIPTING=ON.
> This issue exists *only* when option -std=c++11 or -std=gnu++11 is used.

It looks like swig is creating some code that C++11 doesn't like.  What
version of swig are you using?  I'm using 3.0.6 on windows msys2 builds.

> 
>>
>>> With no python support, Kicad itself compiles without any problem.
>>> but with python support, I have the attached error.
>>>
>>> I am not especially motivated to fix it, and I do not have a lot of
>>> experience about swig. Each test takes *a bunch of* time.
>>>
>>> If someone has an idea about a fix and can help, he is welcome!
>>>
>>> Despite of this issue, I am thinking using C++11 features is a good idea.
>>>
>>> --
>>> 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
>>>
>>
> 
>