kicad-developers team mailing list archive

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

I made a clean build and it seems to be working just fine now.

2015-06-07 22:25 GMT+02:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
> I just checked both 32 and 64 bit builds on windows and I don't have any
> issues no matter how I launch pcbnew, KiCad, EEschema, or stand alone.
>
> On 6/7/2015 4:11 PM, Nick Østergaard wrote:
>> I just tied to pull those changes, but now I get a segfault when
>> starting pcbnew from the kicad app.
>>
>> I could possibly be some other stuff that I did not revert in my
>> workspace before the build. The backtrace looks funny:
>> http://dpaste.com/0DF8RP8
>>
>> Could anyone just try to verify weather or not it crashes if you start
>> kicad with a project and then open pcbnew form there?    I guess this
>> should preferable be tested on a linux system to verify. (Trace looks
>> gtk related)
>>
>> 2015-06-07 20:20 GMT+02:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
>>> I just committed a patch (r5718) from Dick that should greatly simplify
>>> the process of footprint assignment using cvpcb.  This patch does away
>>> with using the intermediate *.cmp file and directly updates the s-expr
>>> netlist via kiway express messaging.  This means there is no more stand
>>> alone executable of cvpcb.  This also means that you will have to use
>>> the s-expr netlist when importing in pcbnew.  If you do not normally
>>> back import the footprint assignments from the *.cmp file into eeschema,
>>> you will have to do this before your run cvpcb because the s-expr
>>> netlist will not contain the footprint assignments until you do this.
>>> This patch will eliminate one more unnecessary step when assigning
>>> footprints and streamline the process.  I still need to fix the save
>>> tooltip in the cvpcb toolbar since the *.cmp file does not get saved.  I
>>> also need to remove the read footprints from *.cmp file in the pcbnew
>>> import netlist dialog since the *.cmp can no longer be generated by
>>> cvpcb.  Going forward, the *.cmp file will only be useful for back
>>> importing from pcbnew to eeschema.  At some point in the future, even
>>> that will go away.j  Please test this and let me know if you find any
>>> issues.
>>>
>>> Cheers,
>>>
>>> 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
>
>
> _______________________________________________
> 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