kicad-developers team mailing list archive

[Mark Roszko <mark.roszko@xxxxxxxxx>]

The findwxwidgets script in kicad is screwy, it can't even find wxwidgets
in msys2 if I invoke Msys2 via a secondary terminal/application (i.e. using
msys2 as a toolchain rather than shell directly).

On Mon, Mar 12, 2018 at 7:02 PM, Nick Østergaard <oe.nick@xxxxxxxxx> wrote:

> I can't make cmake find wxwidgets from vcpkg. I think Thomas Figueroa also
> uses vcpkg, but he built wxwidgets himself to overcome this. So I think
> something is missing for wxwidgets in vcpkg, or something else is not quite
> right in that corner.
>
> 2018-03-12 23:36 GMT+01:00 Mark Roszko <mark.roszko@xxxxxxxxx>:
>
>> Wayne,
>>
>> Long term there is good news, VCPKG exists. https://github.com/Mic
>> rosoft/vcpkg  right now its separate but eventually it'll be part of VS.
>> (But it works now).
>>
>> It's like msys....but for MSVC and it builds packages locally and puts
>> them in a central store. I think most of  Kicad's depedencies are there, I
>> actually started to work on seeing if Kicad would compile with it but
>> didn't get far before being distracted.
>>
>>
>> On Mon, Mar 12, 2018 at 5:33 PM, Wayne Stambaugh <stambaughw@xxxxxxxxx>
>> wrote:
>>
>>> Tom,
>>>
>>> I would prefer KiCad not be in the business of providing dependency
>>> binaries.  I can't stop anyone from providing them but I would rather
>>> developers focus on kicad development rather than our dependencies as
>>> much as possible.  The whole point of removing all of the dependency
>>> build code from v4 was specifically for this reason.  The amount of time
>>> we were spending supporting this was significant.  I would prefer that
>>> the projects provide their own binary installers or we do a better job
>>> of choosing dependencies.
>>>
>>> Cheers,
>>>
>>> Wayne
>>>
>>> On 03/12/2018 04:18 PM, Tomasz Wlostowski wrote:
>>> > On 12/03/18 19:10, Wayne Stambaugh wrote:
>>> >>  The context switching build
>>> >> issue will most likely have to be fixed yet again if we choose to go
>>> >> down this path.
>>> >
>>> > Wayne,
>>> >
>>> > One of the things that Windows does remarkably well is binary
>>> > compatibility. We can just provide pre-built libcontext binaries (as
>>> > well as binaries of every other dependency for Kicad), say, once a
>>> year,
>>> > and with a very high probability they will work on every Windows box
>>> out
>>> > there. I wouldn't worry much about libcontext, I'm more worried about
>>> > code that MSVC might not like in Kicad - but as Mark & Jon reported,
>>> > newer MSVC versions have fixed such interoperability issues, so I hope
>>> > things will go smoothly. Simon has been running MSVC builds for a
>>> while,
>>> > so he's likely more up-to-date than me in MSVC compatibility.
>>> >
>>> > Tom
>>> >
>>>
>>> _______________________________________________
>>> 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
>>>
>>
>>
>>
>> --
>> Mark
>>
>> _______________________________________________
>> 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
>>
>>
>


-- 
Mark