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 <[email protected]> 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 > > >
_______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
