kicad-developers team mailing list archive

[Jason Whiteman <whitemanjason@xxxxxxxxx>]

Brian,

     I "closed" my other thread where I was having problems with SCRIPTING
ON.  Unfortunately, I do not have clear direction for what was the "real"
issue - but I can say it would be nice to have a parameters to pass to
make.bat to allow for a "make clean" in case that was the issue.  I doubt
it because I did get the same (errant) behavior when I tried building fresh
on a new server from scratch.    Of course, running a clean make is not a
big deal outside of winbuilder -- but it may be good to support a feature
or two from the command-line.

     Regarding the toolchain swap -- I knew what I was doing was suspect
because there must be some wisdom in the choice of toolchain used and why
it's a few revs old vs. the "bleeding edge".  I did find this out and had -
a few days ago - backed out my toolchain swap (dlg) to the original
(winbuilder).  One example issue with the dlg is lack of OMP.  So even
though I worked around this in ratsnest - the link problems I was having
(mostly wxpython related -- even with the original winbuilder wxpython)
showed me I should just keep the lid on the toolchain and revert back to
winbuilder native.

     Since my original scripting "shared library" issue went away -- my
motivation for upgrading wxpython also went away -- so I've reverted back
to the winbuilder native version of wxpython.  I figured you would be more
successful than I would be coming in green -- and can wait for the
"official" release.  I do still have my changes in my personal build to the
pointers for w64 compatibility.

      My remaining top-line issue is a crash with pcbnew on exit.   It's
not altogether clear what the source of this is -- and I haven't socialized
it enough to determine what category it fits into.  The second line issue I
am having is the same build that works under Win7 (copy of the binaries,
RunKicad, etc) does not work on the machine I am compiling on (Win 2k8).

      Thanks for the pointers/tips/error reporting workflow.  I'm ramping
up.

Regards,
Jason



On Tue, Jul 1, 2014 at 4:20 PM, Brian Sidebotham <brian.sidebotham@xxxxxxxxx
> wrote:

> 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
> >
>