On newer versions of OS X (maybe only Yosemite), building fails (and running a
binary build on another, earlier system will crash on yosemite) if boost 1.54
is used, if I recall, it was something about this combo that made wxPython
displeased and stop working.
So I have been building using -D
Simon,
I applied your patch in the product branch r5394. I generally frown
patches like this. While technically you are correct EDA_ITEM not used
directly, this is merely semantics. When this kind of patch is the
biggest issue in the KiCad source, I will retire to some tropical island
and soak
Hello!
I've made this suggestion in the past, just trying to be the squeaky wheel.
It'd be really great if the EESchema BOM intermediate XML held more source
information, like Title, Rev, Date, and Comments from the Title Block. More
custom tailored BOM's with valid identification information for
On 01/29/2015 01:52 AM, Fat-Zer wrote:
2015-01-29 2:40 GMT+03:00 Bob Gustafson :
From the KiCad directory, I loaded a fresh source copy by:
bzr checkout lp:kicad kicad.bzr
(I use the checkout so I can enter the kicad.bzr and do ‘bzr up’ )
Then enter the kicad.bzr directory and do:
What about a KiCad dinner on Saturday? Those who would like to join,
let me know off-list so I can book a table somewhere. Also, mobile
phone numbers for some of the CERN folks can be found in our public
phone book [1].
Cheers,
Javier
[1] https://phonebook.cern.ch
__
This patch is no longer valid.
On 1/25/2015 4:25 PM, Simon Richter wrote:
> This function takes an UR_* flag to denote the operation, not an item
> status. As these constants have the same value, this doesn't change
> generated code.
> ---
> eeschema/dialogs/dialog_edit_libentry_fields_in_lib.cpp
6 matches
Mail list logo
