No problems here, but i was just curious, also would it not be better to move the os dependent resouces files to the resources folder (this will require a bit of effort for Info.plist but the rest will be easy...
for example pcbnew.icns, pcbnew_doc.icns and pcbnew.rc Info.plistl are more suitable in a resources directory Simon On Wed, Apr 13, 2016 at 4:55 AM, Wayne Stambaugh <[email protected]> wrote: > I have a bunch of code cleaning on my todo list and want to make sure I > don't step on anyone's toes. Here is the list of things that I'm going > to remove: > > * All of the macro code which does nothing and appears to have been > abandoned long ago. I should have do this before the stable release. > > * All of the user build scripts in the scripts/ folder including the OSX > specific stuff. > > * The packaging folder which I believe we've discussed this in the past > and agreed that we could get rid of it. There is some OSX stuff in > there that I'm not sure about. > > * Some of the old documentation of items that have been completed or are > no longer being developed. > > * The old subversion cmake files. > > Please let me know if there is anything here that I need to keep or if > there is anything I missed. I do want to keep the new/ folder as there > is an inheritance design in there that may prove useful when the new > component library file format is implemented. Once that hurdle is > cleared, I'll remove the contents of the new/ folder. > > Cheers, > > Wayne > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
