kicad-developers team mailing list archive

[Nick Østergaard <oe.nick@xxxxxxxxx>]

Den 30/03/2015 01.47 skrev "Wayne Stambaugh" <stambaughw@xxxxxxxxx>:
>
> On 3/29/2015 5:55 PM, Nick Østergaard wrote:
> > 2015-03-29 23:53 GMT+02:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
> >> On 3/29/2015 5:50 PM, Nick Østergaard wrote:
> >>> 2015-03-29 23:44 GMT+02:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
> >>>> On 3/29/2015 5:38 PM, Nick Østergaard wrote:
> >>>>> Thank you for the announcement. Hopefully we can then close a lot of
> >>>>> bugs then, not that this is something that has not been done in the
> >>>>> meantime. Thumbs up.
> >>>>
> >>>> I'll have some more info on that over the next few days so we can
start
> >>>> focusing on the stable release.
> >>>>
> >>>>>
> >>>>> But it seems like the newest commit does not build on the build
> >>>>> server. Please see:
> >>>>> http://ci.kicad-pcb.org/job/kicad-full/319/console
> >>>>>
> >>>>> Do the environment require an update?
> >>>>
> >>>> Are you building this against wx 2.8?  Your build is failing for
> >>>> undefined wxRichMessageDialog which is only available since wx 2.9.5.
> >>>
> >>> No, this is against 3.0.1 according to wx-config --version.
> >>
> >> I wonder if there is a custom build option when building wxWidgets
under
> >> linux to enable this.  I hope not.  Otherwise, everyone's linux builds
> >> will be broken.  I may be implementing our own custom rich message box
> >> sooner than I thought.  I will try to build it on linux as soon as I
can
> >> to see if I have the some problem.
> >
> > It builds fine on the fedora20 machine, with wx 3.0.2. This is using
> > Ajo's wx stuff IIRC.
>
> I just finished building this on my Debian testing system and it build
> fine so it appears that it may be something wrong with you wx 3.0.1 build.

What is the wx version on your debian system?

> >
> >>>>> 2015-03-29 23:23 GMT+02:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
> >>>>>> Attention all developers.  I have finally committed the environment
> >>>>>> variable configuration dialog (although I named it the "Path
> >>>>>> Configuration" because the term environment variable is apparently
too
> >>>>>> scary) so we are now in feature freeze.  This means if you want to
add a
> >>>>>> new feature or change any functional behavior you must run it by
the
> >>>>>> developers list first.  This includes me as well.  The only thing
I'm
> >>>>>> aware that's already in the pipe line at the moment is the
footprint
> >>>>>> wizard that Orson is working on so that can be committed without
approval.
> >>>>>>
> >>>>>> Please test the path configuration editor to make sure it is
robust for
> >>>>>> the stable release.  I did not do anything too fancy in the wxGrid
> >>>>>> control used in the editor so the grid editing will be very basic.
> >>>>>> Also, I kept the default wxGrid tab key behavior which means you
will
> >>>>>> have to use Ctrl+Tab to perform the default action which is the OK
> >>>>>> button.  I also created a warning dialog using wxRichMessageDialog
when
> >>>>>> an externally defined environment variable is modified.  I'm not
really
> >>>>>> thrilled with the appearance of this dialog so I will most like
roll my
> >>>>>> own version that will look a bit like our exit dialog but feed back
> >>>>>> would be appreciated.  This also means that KiCad will no longer
build
> >>>>>> against wxWidgets 2.8 for anyone out there still clinging to that
version.
> >>>>>>
> >>>>>> Now that we are in feature freeze it's time to take stock on what
is
> >>>>>> going on in other areas such as documentation and nightly builds
so I
> >>>>>> will be sending out additional topic specific messages over the
next few
> >>>>>> days.
> >>>>>>
> >>>>>> Thanks,
> >>>>>>
> >>>>>> Wayne
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> 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
> >>>>
> >>
>