kicad-developers team mailing list archive

[Jean-Paul Louis <louijp@xxxxxxxxx>]

I like KiCad, but can easily live with kicad.
So will you do like below?

USRLIB=~/Library/Application Support/kicad
SYSLIB=/Library/Application Support/kicad

Then there should be sub-dirs like
 ./symbols
 ./footprints
 ./modules
 ./doc
 ./scripts
 ./python
 ./etc..
as needed

Jean-Paul
AC9GH


On May 6, 2014, at 5:52 PM, Marco Serantoni <marco.serantoni@xxxxxxxxx> wrote:

> 
> On 06/mag/2014, at 22:59, Jean-Paul Louis <louijp@xxxxxxxxx> wrote:
> 
> Lower case kicad,
> 
> This choose was planned in advance, when all applications will collapse in kicad.app the default “application name” will be kicad.
> This approach permits to use wxStandardPaths references for Application Data repository, since will match ::GetUserDataDir  “appinfo” 
> 
> The reason why is not already used is because each application has a different "application name” then:
> eeschema will be -> ~/Library/Application Support/eeschema
> pcbnew will be -> ~/Library/Application Support/pcbnew
> etc.
> So they will point to different paths.
> 
> To cirmcumvent it was choosen to hardcode it, waiting for use something more standard that could arrive soon.
> 
> About /Library/Application Support/kicad, i prefer it because could save a lot of diskspace in multiuser workstations avoiding to replicate libraries for each user.
> If some user needs its private library could use ~/Library/Application Support/kicad that has the precedence over the global one.
> 
> Precendence:
> ~/Library/Application Support/kicad
> /Library/Application Support/kicad
> 
> The first is found is used.
> 
> This arrangement optimizes diskspace that in the new SSDs Macs become again an issue and still provide the maximum flexibility for the users.
> 
> —
> Marco
> 
> 
> 
>> Thanks a lot, Adam!
>> 
>> Now I can see my $HOME/Library.
>> 
>> For the Master Data Location, I would prefer /Library/Application Support/Kicad,
>> and a similar ~/Library/Application Support/Kicad, for the personal or project libraries.
>> 
>> Jean-Paul
>> AC9GH
>> 
>> On May 6, 2014, at 4:08 PM, Adam Wolf <adamwwolf@xxxxxxxxx> wrote:
>> 
>>> http://www.macworld.com/article/2057221/how-to-view-the-library-folder-in-mavericks.html
>>> 
>>> 
>>> On Tue, May 6, 2014 at 3:04 PM, louijp <louijp@xxxxxxxxx> wrote:
>>> Marco,
>>> /Library is not visible in my finder.
>>> I have to use a terminal to go there, and I do not have a ~/Library. That's the default on a new Macbook pro. But that might be an acceptable choice if you tell me how to modify the Finder app to see the /Library directory.
>>> 
>>> My $0.02,
>>> Jean-Paul
>>> 
>>> 
>>> Sent from my Verizon Wireless 4G LTE smartphone
>>> 
>>> 
>>> -------- Original message --------
>>> From: Marco Serantoni 
>>> Date:2014/05/06 12:59 PM (GMT-05:00) 
>>> To: Adam Wolf 
>>> Cc: kicad-developers@xxxxxxxxxxxxxxxxxxx 
>>> Subject: Re: [Kicad-developers] KICAD_DATA on OS X 
>>> 
>>> Adam,
>>> I'm for /Library & ~/Library, first because they are coherent with the enviroment and wxStandardPaths.
>>> We have discussed about that with Wayne not much months ago, we agree from much time about the correctness to use that class without reinvent the wheel, the differences were about ::GetUserConfigDir ::GetUserDataDir and fp_table, now the discussion could be easier to understand with updated documentation.
>>> 
>>> http://docs.wxwidgets.org/trunk/classwx_standard_paths.html#a7c7cf595d94d29147360d031647476b0
>>> 
>>> 
>>> Placing things inside a bundle is nice, but is nice only for Support files that are immutable, libraries are not, they have  be changed.
>>> 
>>> /usr/local in osx is the same than ask an linux user to make a C:/windows directory in its root, moreover the Finder could not navigate those directory easly.
>>> 
>>> 
>>> Try to take a look to common/systemdirsappend.cpp, i'vent seen deepier the changes but i don't think that points to /usr/local.
>>> 
>>> 
>>> --
>>> Marco
>>> 
>>> 
>>> On Tue, May 6, 2014 at 5:30 PM, Adam Wolf <adamwwolf@xxxxxxxxx> wrote:
>>> Hi folks,
>>> 
>>> I have been producing OS X builds for a while now, and I'm working on addressing some feedback before I start setting up the push of DMGs to Miguel's system.
>>> 
>>> The first main feedback point is KICAD_DATA.  I apologize if this has been discussed before--I promise I searched in the archives for about five minutes before drafting this.
>>> 
>>> Right now, various things like eeschema are looking at /usr/local/library, which isn't what we want.
>>> 
>>> Some places users have suggested to me include:
>>> 	•	/usr/local/share/kicad/library
>>> 	•	/Library/Application Support/Kicad
>>> 	•	~/LibraryApplication Support/Kicad
>>> 	•	Inside the .app Bundle
>>> 
>>> Marco and the other Mac folks, I am especially interested in your input.  Thanks!
>>> 
>>> Adam Wolf
>>> Wayne and Layne, LLC
>>> 
>>> 
>>> 
>>> 
>> 
>