kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

On 3/13/2015 8:06 AM, Nick Østergaard wrote:
> 2015-03-13 12:44 GMT+01:00 Brian Sidebotham <brian.sidebotham@xxxxxxxxx>:
>> On 13 March 2015 at 11:37, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
>>> On 3/12/2015 5:48 PM, Brian Sidebotham wrote:
>>>> On 12 March 2015 at 17:48, Wayne Stambaugh <stambaughw@xxxxxxxxx> wrote:
>>>>>
>>>>>
>>>>> On 3/12/2015 1:37 PM, Nick Østergaard wrote:
>>>>>> 2015-03-12 18:26 GMT+01:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
>>>>>>>
>>>>>>>
>>>>>>> On 3/12/2015 1:26 PM, Nick Østergaard wrote:
>>>>>>>>
>>>>>>>> Den 12/03/2015 18.16 skrev "Wayne Stambaugh" <stambaughw@xxxxxxxxx
>>>>>>>> <mailto:stambaughw@xxxxxxxxx>>:
>>>>>> [snip]
>>>>>>>>> FYI.  Using the msys2/mingw64 builds of wxWidgets 3.0.2-3, wxWidgets is
>>>>>>>>> compiled with -std=gnu++11 which breaks the KiCad build.  I'm guessing
>>>>>>>>> that KiCad will build with the -std=gnu++11 option but I haven't tried
>>>>>>>>> it yet.  I filed a bug report so I'm guessing it will be fixed soon so
>>>>>>>>> you may run into problems.  You can always downgrade the wxWidgets
>>>>>>>>> package to 3.0.2-2.
>>>>>>>>
>>>>>>>> I have not experinced any compilation issues, although I would like to
>>>>>>>> use the new docs from ciampix repo and get the GUI translations in an
>>>>>>>> more lightweight repo, for example in the new doc repo or even a
>>>>>>>> standalone git repo. I am able to split the repo and keep comnit history.
>>>>>>>>
>>>>>>>> Byt maybe I am just not on -3. I will have a look later.
>>>>>>>
>>>>>>> It was just pushed to the repo yesterday so if you haven't upgraded in
>>>>>>> the last day or so, your still using -2.  I just tried to compile KiCad
>>>>>>> using -3 with -std=gnu++11 and now it's choking on boost.  Do yourself a
>>>>>>> favor an do not upgrade until -4 is released.
>>>>>>
>>>>>> Do you have a link to the report? I can't find it in the open issues
>>>>>> at Alexpux/MINGW-packages on github.
>>>>>
>>>>> I filed it on the old SourceForge bug tracker here:
>>>>>
>>>>> http://sourceforge.net/p/msys2/tickets/138
>>>>
>>>> Nick, thank-you for posting this to the list!
>>>>
>>>> Wayne,
>>>>
>>>> Thanks for the confirmation. I was bit by this last night while trying
>>>> to test the KiCad-Winbuilder stuff. I soon realised that it was doomed
>>>> after the wxWidgets-3 push. Hopefully they'll get it sorted out pretty
>>>> quickly.
>>>
>>> I just upgraded this morning and the -5 build of wxWidgets has already
>>> been released.  I'll give the msys2 folks credit, they get things fixed
>>> very quickly given the size and scope of the project.
> 
> Great.
> 
>>
>> Yep, I saw that. They're very active which is encouraging.
>>
>>>>
>>>> Thanks for reporting the bug, looks like they're getting on with it
>>>> pretty quickly.
>>>>
>>>> This is exactly why it makes sense for us to use the pacman stuff to
>>>> build with; Because it's one build system that we're all trying to
>>>> support. Plus, it means no more maintenance of external projects like
>>>> wxwidgets-cmake, etc. for me! Phew!
>>>
>>> I really am impressed by what the msys2 project has accomplished.  It
>>> certainly makes life easier building KiCad on windows.  There already is
>>> a PKGBUILD file for kicad which I created for the msys2 project.  It
>>> should be as simple as running a nightly build using makepkg-mingw.
> 
> This is what I use.
> 
>>> Unfortunately, it's an all in one package which includes the docs and
>>> libraries so it's rather larger.  The msys2 folks seemed to prefer that
>>> I package kicad that way so I didn't argue with them about it.  For our
>>> purposes, we could split the package any way we prefer.
> 
> Yeah, that is a pity. But I would like to use the new docs repo,
> because the bzr repo actually fails for me usually. I propose to split
> the internat directory out in a seperate repo for itself, such that
> contributors don't have the gigantic overhead of the old bzr repo
> which is pretty darn big in download size (and disk space). It is
> possible to keep the commit history, see:
> 
> https://github.com/nickoe/kicad-internat-only
> 
> This need to have the cmake scripts fixed.
> 
> Also, I wonder why the compiled po files are in the repo also (the .mo
> files). Is there a reason for this? Why not just do this as a build
> step?

I'm not sure.  I've never done any of the internationalization stuff.
JP would probably have a better idea of why it's done this way.  It
makes sense to me to make it a build step but there may be other issues
at play that I am not aware of.

> 
>> That is all we do. That way, we're aligned. The packaging is fine,
>> because we can then choose what we want to do - Build our own
>> installer with/without docs, with/without libraries, etc.
>>
>> I don't think it'll take us much more effort to get to a place where
>> it can build installers that can be used. Nick's already had that done
>> manually for a while and automating it more so it is KiCad-Winbuilder
>> has proved to be pretty straight forward too.
>>
>> Thanks for your excellent work on the packaging btw - it's been a
>> pleasure to build KiCad with MSYS2!
>>
>> Best Regards,
>>
>> Brian.
>>
>> _______________________________________________
>> 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