davidjsherman / aseba-osx Goto Github PK

Lastest Dashel compiles @rpath in symbol table. Need to fix packager rules to rewrite them

The current installer signs everything, both installers and components. The MacOS Code Signing Guide isn't entirely clear what to sign or not. This needs to be understood and implemented.

Possibly impacted by #2, since Packager may have intelligent defaults.

The current installer does some funny tricks to use shared libraries by both apps and command-line tools, within the same app bundle.

The usual MacOS way to do this is to use a public framework, that can be shared by individual apps. From the Framework Programming Guide (emphasis mine):

Custom frameworks intended for internal use should be installed inside the application that uses them.... The limitation of embedding frameworks is that you cannot share the framework among a suite of applications. If your company develops a suite of applications that rely on the same framework, you might want to install one copy of that framework that all of the applications can share. In such a situation, you should install the frameworks in the /Library/Frameworks directory and make sure the frameworks bundle does not contain any public header information.

Frameworks in /Library will be searched buy @rpath, see #1.

Installing a Framework alongside with apps requires a package installer.
A good lead to try is Stéphane Sudre's Packages.