kicad-developers team mailing list archive

[Roman Pavelka <roman.pavelka.asi@xxxxxxxxx>]

Hey,

this is great, tested on Debian 8.5



1. I would propose to add this one liner to documentation for
dependencies in Ubuntu and Debian:

sudo aptitude install libgtk-3-dev libcairo2-dev libgit2-dev transfig
imagemagick

and to add "sudo" before "make install"



2. Paths are broken for me for some symbols, because I have Kicad in
/usr/local/share/kicad

/usr/share/kicad/library/contrib.lib: No such file or directory
valves.lib: No such file or directory
/usr/share/kicad/library/valves.lib: No such file or directory
"TIP122" not found
"LM358N" not found

I tried change in kicad/kicad.h to only correct one
#define KICAD_DATAS_PATH(append)        \
    "/usr/local/share/kicad"    append

But no luck, after recompile and reinstall it gives this

contrib.lib: No such file or directory
valves.lib: No such file or directory
"TIP122" not found
"LM358N" not found

ls /usr/local/share/kicad/
demos  library  modules  scripting  template

ls /usr/local/share/kicad/library/
ac-dc.dcm            atmel.dcm      conn.lib
digital-audio.lib   ftdi.lib       ir.dcm       microcontrollers.dcm
   microchip_pic16mcu.lib  nordicsemi.dcm   power.dcm
relays.dcm    stm8.dcm         transistors.lib  Zilog.dcm
ac-dc.lib            atmel.lib      contrib.dcm             diode.dcm
         gennum.dcm     ir.lib       microcontrollers.lib
microchip_pic18mcu.dcm  nordicsemi.lib   powerint.dcm
relays.lib    stm8.lib         ttl_ieee.dcm     Zilog.lib
actel.dcm            audio.dcm      contrib.lib             diode.lib
         gennum.lib     Lattice.dcm  microchip.dcm
microchip_pic18mcu.lib  nxp_armmcu.dcm   powerint.lib
rfcom.dcm     supertex.dcm     ttl_ieee.lib     74xgxx.dcm
actel.lib            audio.lib      contrib_symbols_dl1eic
display.dcm         graphic.dcm    Lattice.lib
microchip_dspic33dsc.dcm  microchip_pic32mcu.dcm  nxp_armmcu.lib
power.lib             rfcom.lib     supertex.lib     valves.dcm
74xgxx.lib
adc-dac.dcm          brooktre.dcm   cypress.dcm
display.lib         graphic.lib    linear.dcm
microchip_dspic33dsc.lib  microchip_pic32mcu.lib  onsemi.dcm
Power_Management.lib  sensors.dcm   switches.dcm     valves.lib
74xx.dcm
adc-dac.lib          brooktre.lib   cypress.lib             dsp.dcm
         hc11.dcm       linear.lib   microchip.lib
motor_drivers.dcm       onsemi.lib       pspice.dcm
sensors.lib   switches.lib     video.dcm        74xx.lib
Altera.lib           cmos_ieee.dcm  dc-dc.dcm               dsp.lib
         hc11.lib       logo.lib     microchip_pic10mcu.dcm
motor_drivers.lib       opto.dcm         pspice.lib
silabs.dcm    texas.dcm        video.lib
analog_devices.dcm   cmos_ieee.lib  dc-dc.lib
elec-unifil.dcm     intel.dcm      maxim.dcm    microchip_pic10mcu.lib
   motorola.dcm            opto.lib         references.dcm
silabs.lib    texas.lib        Xicor.dcm
analog_devices.lib   cmos4000.dcm   device.dcm
elec-unifil.lib     intel.lib      maxim.lib    microchip_pic12mcu.dcm
   motorola.lib            Oscillators.lib  references.lib
siliconi.lib  transf.dcm       Xicor.lib
analog_switches.dcm  cmos4000.lib   device.lib
ESD_Protection.lib  interface.dcm  memory.dcm   microchip_pic12mcu.lib
   msp430.dcm              philips.dcm      regul.dcm
stm32.dcm     transf.lib       xilinx.dcm
analog_switches.lib  conn.dcm       digital-audio.dcm       ftdi.dcm
         interface.lib  memory.lib   microchip_pic16mcu.dcm
msp430.lib              philips.lib      regul.lib
stm32.lib     transistors.dcm  xilinx.lib

On 10 September 2016 at 11:23, Werner Almesberger
<werner@xxxxxxxxxxxxxxx> wrote:
> Eldar Khayrullin wrote:
>> I don't think that it is advisable now.
>
> Hmm, do you mean trying to use Eeschema/-like fonts ?
>
>> See Roadmap why it is as (http://ci.kicad-pcb.org/job/kicad-doxygen/ws/Documentation/doxygen/html/v5_road_map.html).
>
> There's a lot on this page :-) Are you thinking of
> Project > Common Library > Unified Rendering Framework
> "Port wxDC to GAL or get Cairo rendering" ?
>
> I've asked about that on #kicad, and I get the impressions that the
> plans for Eeschema are still fairly vague in this regard.
>
> In any case, I'm not in a hurry to jump into this. As long as text
> rendering works acceptably, that's good enough for me at the present
> stage. My current focus is mainly on file access (sounds boring but
> gets rather entertaining when you add repos and their history to the
> mix) and on making diffs better.
>
> - Werner
>
> _______________________________________________
> 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



-- 
Roman Pavelka
http://kmlinux.fjfi.cvut.cz/~pavelro1