Re: [Kicad-developers] Uninitialized KISYSMOD issue on OS X?

2015-12-03 Thread Adam Wolf
A good one! But alas, we have them drag and drop a kicad/ directory onto a symlink to /Library/Application\ Support/, and it does a popup asking for admin privileges. (We also have this in the README right there when you install). It's certainly got me puzzled! On Thu, Dec 3, 2015 at 2:16 PM,

[Kicad-developers] Uninitialized KISYSMOD issue on OS X?

2015-12-03 Thread Adam Wolf
Hi folks! A user is having a problem with the latest OS X RC2 release, and I haven't been able to figure it out. Quick background: There is a KiCad package, and a KiCad Extras package. The KiCad Extras package has a modules/ directory in it, and it has all the footprints. It's for offline use.

Re: [Kicad-developers] Uninitialized KISYSMOD issue on OS X?

2015-12-03 Thread Bob Gustafson
Maybe it is a 'first time use problem' - maybe no kicad directory in the /Library/Application Support/. It may require a privilege password to add this directory the first time. A thought anyway. Bob G On 12/03/2015 02:08 PM, Adam Wolf wrote: Hi folks! A user is having a problem with the

Re: [Kicad-developers] Uninitialized KISYSMOD issue on OS X?

2015-12-03 Thread Bernhard Stegmaier
It’s not in a plist, but in ~/Library/Preferences/kicad/kicad_common. As far as I can remember, if you had something wrong in there before the environment-variable changes Wayne did, it didn’t vanish with the changes… you had to manually change via Preferences => Path Configuration (or,

Re: [Kicad-developers] Uninitialized KISYSMOD issue on OS X?

2015-12-03 Thread Adam Wolf
I asked him for Preferences => Path Configuration in the last email. He hasn't responded yet. He doesn't have footprints available, but it looks like that's due to a networking issue and Github footprints? Not sure. I am almost willing to chalk this up to it being a fluke, especially if we

Re: [Kicad-developers] Uninitialized KISYSMOD issue on OS X?

2015-12-03 Thread Adam Wolf
I am glad I am not the only one puzzled by this. I also searched the plists, because at one point we were putting environment variables in there, but that stopped over a year ago I thought. Oh the other hand-- Is it possible he had some other error, and saw the debug messages that say line

Re: [Kicad-developers] Uninitialized KISYSMOD issue on OS X?

2015-12-03 Thread Bernhard Stegmaier
I also don’t see any reason for what you described. The SEARCH_STACK stuff should not be used in pcbnew any more, the other one in pgm_base.cpp looks good IMHO. I can’t remember any other place where this could be a problem except there is already some path slipping in from outside of KiCad.

Re: [Kicad-developers] Uninitialized KISYSMOD issue on OS X?

2015-12-03 Thread Wayne Stambaugh
I didn't see it in his comments but the environment variable config dialog highlights environment variables that are already defined when kicad starts so they take precedence over the user configuration by design. Is it possible that he has KISYSMOD already set? On 12/3/2015 3:43 PM, Adam Wolf

Re: [Kicad-developers] Uninitialized KISYSMOD issue on OS X?

2015-12-03 Thread Wayne Stambaugh
On 12/3/2015 3:08 PM, Adam Wolf wrote: > Hi folks! > > A user is having a problem with the latest OS X RC2 release, and I > haven't been able to figure it out. > > Quick background: > > There is a KiCad package, and a KiCad Extras package. The KiCad Extras > package has a modules/ directory in