kicad-developers team mailing list archive

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

2015-01-25 20:02 GMT+01:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
> On 1/25/2015 10:29 AM, Nick Østergaard wrote:
>> 2015-01-23 14:42 GMT+01:00 Wayne Stambaugh <stambaughw@xxxxxxxxx>:
>>> As you all know, we have had many users struggle with setting up the
>>> environment variables used in the footprint library table and 3D model
>>> code.  The attached patch sets the process environment variables
>>> KIGITHUB and KISYS3DMOD.  KIGITHUB should work for all platforms since
>>> it is the URL for the kicad library repos on GitHub which is always
>>> https://github.com/KiCad.  KISYS3DMOD uses the 3D model library install
>>> path created during the CMake configuration.  This works fine for me on
>>> windows and linux.  OSX may be a different story due to the way the
>>> bundle paths are defined.  Would on of the OSX devs please test this and
>>> give me some feedback?  Please don't forget to remove these environment
>>> variables that are set elsewhere.  Otherwise, the environment variable
>>> in this patch will be ignored.  My guess is that if we get the default
>>> environment variable set correctly that it would solve the problem for
>>> the largest percentage of users until I get some time to work on the
>>> dialog to edit them.  I will also add KISYSMOD to this code once have
>>> the default OSX paths established.
>>
>> What would the default KISYSMOD be? I currently set it to
>> /usr/share/kicad/footprints in my kicad-pretty-git AUR package [1].
>>
>> [1] https://aur.archlinux.org/packages/kicad-pretty-git/
>>
>
> The default KISYSMOD on Linux would be
> /usr/local/share/kicad/footprints.  However, this can be changed during
> the CMake configuration by passing -DCMAKE_INSTALL_PREFIX=/install/path.
>  My guess is that packagers set this to /usr instead of the default
> /usr/local when building distro specific KiCad packages.

True.

> The default
> should always correctly point to the correct path as long a the library
> install path is also set to the same path as the source build install
> path.  The problem child is OSX because of the way the install paths are
> defined so I still need an answer from the OSX devs before I commit this
> patch.  The Windows NSIS installer can also be problematic if the user
> installs KiCad anywhere but the default path which is c:\Program Files.

Ok, thank you for your explanation.