Fixup documentation for macOS Python script plugins. Fixes #1789960.

This commit is contained in:
Adam Wolf 2018-11-27 07:58:05 -06:00 committed by Wayne Stambaugh
parent 8ca0fe6722
commit 3392162d49
1 changed files with 5 additions and 3 deletions

View File

@ -43,9 +43,11 @@ packages and Python script files in specific directories on startup.
In order for the discovery process to work, the following requirements must be met. In order for the discovery process to work, the following requirements must be met.
* The plugin must be installed in the KiCad plugins search paths as documented * The plugin must be installed in the KiCad plugins search paths as documented
in `scripting/kicadplugins.i`. in `scripting/kicadplugins.i`. You can always discover the search path for your
setup by opening the Scripting console and entering the command: `import pcbnew;
print pcbnew.PLUGIN_DIRECTORIES_SEARCH`.
Currently on a Linux Installation this is Currently on a Linux Installation the plugins search path is
* /usr/share/kicad/scripting/plugins/ * /usr/share/kicad/scripting/plugins/
* ~/.kicad/scripting/plugins * ~/.kicad/scripting/plugins
@ -56,7 +58,7 @@ In order for the discovery process to work, the following requirements must be m
* \{KICAD_INSTALL_PATH\}/share/kicad/scripting/plugins * \{KICAD_INSTALL_PATH\}/share/kicad/scripting/plugins
* %APPDATA%/Roaming/kicad/scripting/plugins * %APPDATA%/Roaming/kicad/scripting/plugins
On MacOS On macOS, there is a security feature that makes it easier to add scripting plugins to the ~/Library... path than to kicad.app, but the search path is
* /Applications/kicad/Kicad/Contents/SharedSupport/scripting/plugins * /Applications/kicad/Kicad/Contents/SharedSupport/scripting/plugins
* ~/Library/Application Support/kicad/scripting/plugins * ~/Library/Application Support/kicad/scripting/plugins