kicad-developers team mailing list archive

[Brian Sidebotham <brian.sidebotham@xxxxxxxxx>]

Thanks for the release information Dick, we'll look to include that in
Winbuilder as soon as possible. At the moment the version used is a
patched v3.0.0, not a vanilla version. Therefore some vital fixes for
KiCad were already included. It will be good to upgrade to get the bug
fixes though.

Jason,

Changing everything is likely just going to get you in more of a mess
tbh, The toolchain included with Winbuilder is a mingw-w64 version
from the mingw-builds project. It's a SJLJ version, be very careful
using a different compiler with the other winbuilder dependencies.
There's been some nasty bugs seen before when mixing toolchains.

Everything in Winbuilder works, but it would seem in your instance the
environment is different when running KiCad. You *must* run KiCad from
the RunKiCad.bat start script included in winbuilder because that sets
up the environemt. It's meant to be an isolated environment so that no
install is required, but it looks like there's something that isn't
isolated in your case.

I would recommend taking the following steps:

(1) File a full bug report on Launchpad for KiCad-Winbuilder ( I think
this is definitely a Winbuilder bug, not KiCad )
(2) Build from a fresh download of KiCad-Winbuilder-3.4-2 on a local
drive ( non-removable media )
(3) Attached the build logs from that build to the bug you reported on
Launchpad.
(4) If you can, get process monitor (
http://technet.microsoft.com/en-gb/sysinternals/bb896645.aspx ), start
it and add a filter to only include items from a process called
pcbnew.exe and then start PCBNEW from the KiCad program manager and
report all entries in process monitor. This way we'll see the exact
paths that the dynamic loader is trying to load _pcbnew.kiface from
and also what dependencies that loads and where from too.

Reporting the bug generally gets other people's input too because
there's always more than one person suffering from the same problem.
However, so far I've not seen anyone else experiencing this bug.

Best Regards,

Brian.

On 30 June 2014 08:04, Jason Whiteman <whitemanjason@xxxxxxxxx> wrote:
> Thanks for the heads up -- this started me a bit down a rabbit hole.  I've
> swapped out the winbuilder mingw with the "mingw-w64-dgn" personal build.
> He's got wxwidgets-3.0.1 pre-built.  This brought gcc up to 4.8.3 (could
> have went the 4.9.0 way -- but decided to stay within the 4.8.x) and moved
> to an x64 compiler.
>
> This exposes a few pointers that need to be retyped for x64 - I'm working
> through that.
>
> Also, the dgn build doesn't come with OpenMP out-of-the-box.  I think I have
> to install llvm perhaps.  Not a big deal - only ratsnest uses is thus far in
> my compile -- so I #undef'd OpenMP out of the src.  I've got it queued to go
> back and "unpatch" that - but at this point I'm just trying to sort through
> a w64 build.  I'm sure this has been done many times over by others.
>
> Regards,
> Jason
>
>
>
> On Sun, Jun 29, 2014 at 7:58 AM, Dick Hollenbeck <dick@xxxxxxxxxxx> wrote:
>>
>>
>> http://wxwidgets.org/news/2014/06/wxwidgets-3.0.1-released/
>>
>> Is good news.  I have seen quite a few bugs in the 3.0 release myself, and
>> stopped using
>> it after about a month. In my case, I simply use SVN HEAD.
>>
>> Might be a good idea if winbuilder would use this 3.0.1 version.
>>
>> Dick
>>
>>
>> _______________________________________________
>> 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
>
>
>
> _______________________________________________
> 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
>