kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

I'm OK with installing the xsl files in share/kicad/xsl but it will
break existing custom BOM configurations so I'm sure there will be some
user grumbling.

Maybe we should put the python scripts in share/kicad/scripting/python
in case we add other scripting languages in the future.  From what I
understand, swig handles many more languages with less issues than in
the past so it may be prudent rather than have to change paths in the
future.

Anyone have any strong objections to these changes?

On 9/28/2015 2:16 PM, Nick Østergaard wrote:
> Yes, and this is exactly why I ask these questions.
> 
> I personally don't think that scripting examples needs to be
> installed. But of course we can do that.
> 
> But I still think we should make the xsl "plugins" not just a plugins
> folder. I propose to install the python wizards
> share/kicad/plugins/scripting and the xsl stuff as
> share/kicad/plugins/xsl. This instead of the lib/kicad/plugins where
> the xsl files are located now.
> 
> In this way they are located in the same place, but still seperated in
> different folder. I am open for input for this.
> 
> 2015-09-28 19:58 GMT+02:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
>> I just discovered the python plugins are not installed on any platform
>> but apple.  It appears that the cmake install directive for the python
>> plugin files got moved inside the conditional apple configure code.  I
>> will fix this but it still doesn't solve the path problem.  Using
>> ${KICAD_PATH}/scripting/plugins will require the user to set the
>> KICAD_PATH environment variable in order for this to work.
>>
>> What about the scripting examples?  It doesn't look like they are
>> getting installed either?
>>
>> On 9/28/2015 11:54 AM, Nick Østergaard wrote:
>>> From the kicadplugins.i file tha Ajo linked it is in theese dirs on linux:
>>>
>>> ${KICAD_PATH}/scripting/plugins
>>> ${HOME}/.kicad_plugins
>>> ${HOME}/.kicad/scripting/plugins
>>>
>>> KICAD_PATH is not internally defined in kicad, it seems.
>>>
>>> In principle it is installed in something called KICAD_DATA  on cmake,
>>> which is share/kicad on linux, and then as scripting/plugins in there.
>>>
>>> But remember we also have a concept of plugins in eeschema with the
>>> BOM exporter, which usually uses xlstproc with xsl files.
>>>
>>> So I am not sure what is the appropiate place.
>>>
>>> 2015-09-28 17:37 GMT+02:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
>>>> There is no $KICAD_PATH in the cmake configuration files.  There is
>>>> CMAKE_INSTALL_PREFIX that defaults to the appropriate platform path for
>>>> using `make install`.  This can be changed when configuring cmake if
>>>> your not happy with the default.  Relative to CMAKE_INSTALL_PATH, what
>>>> is the sub-directory that the python scripts need to be install in to
>>>> ensure the they can be used without any additional user configuration?
>>>>
>>>> On 9/28/2015 6:36 AM, Miguel Angel Ajo wrote:
>>>>> Hmm, that's a good point, I guess we should install them to
>>>>>
>>>>> $KICAD_PATH/scripting/plugins
>>>>>
>>>>> as it's the standard place where kicad will try to load them from [1]
>>>>>
>>>>> [1]
>>>>> https://github.com/KiCad/kicad-source-mirror/blob/master/scripting/kicadplugins.i#L85
>>>>>
>>>>>
>>>>> Nick Østergaard wrote:
>>>>>> Hi
>>>>>>
>>>>>> What is the plan for the python footprint wizrards [1]?
>>>>>>
>>>>>> I was trying to figure out how they were supposed to be installed, as
>>>>>> it looks now, it seems that they are not installed by cmake [3]. I see
>>>>>> that the eeschema bom pluings (the xsl files [2]) are intalled with
>>>>>> cmake, but that [1] is not, although it seems like they sould be
>>>>>> installed if we look at [3], but only if APPLE. And it seemt hat if
>>>>>> not __MINGW32__ or __WXMAC__ then we use the completely hardcoded path
>>>>>> on linux to /usr/local/kicad/bin/scripting/plugins ! [4].
>>>>>>
>>>>>> Although I can put them in ~/.kicad_plugins and they will work too.
>>>>>> But I am not exactly sure where this is defined.
>>>>>>
>>>>>> So what is the desired way to fix this issue? As is now it makes it
>>>>>> difficult to package the footprint wizards, because it is not
>>>>>> instlaled with cmake nor is there a dynamic path defined on linux.
>>>>>>
>>>>>> Regards
>>>>>> Nick Østergaard
>>>>>>
>>>>>> [1]
>>>>>> https://github.com/KiCad/kicad-source-mirror/tree/master/pcbnew/scripting/plugins
>>>>>>
>>>>>> [2]
>>>>>> https://github.com/KiCad/kicad-source-mirror/tree/master/eeschema/plugins
>>>>>> [3]
>>>>>> https://github.com/KiCad/kicad-source-mirror/blob/edbcf2d0cb5b6cd41f2c8f5da02eea83a87e23f5/pcbnew/CMakeLists.txt#L662
>>>>>>
>>>>>> [4]
>>>>>> https://github.com/KiCad/kicad-source-mirror/blob/edbcf2d0cb5b6cd41f2c8f5da02eea83a87e23f5/pcbnew/pcbnew.cpp#L244
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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