Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


just a quick heads-up, since this is rather exceptional nowadays:
pulling this commit requires a "make clean" on Mac OS X; just doing an
incremental build is very likely to fail!

On 09/09/14 13:29, Tor Lillqvist wrote:
New commits:
commit 6492c8576e0393f7ee548cd938e84c80e8d37127
Author: Tor Lillqvist <tml@collabora.com>
Date:   Tue Sep 9 10:44:56 2014 +0300

    Make the "Mac-like" or "canonical" app bundle structure always used on OS X
    
    In other words, only executable files go in the MacOS folder. Dynamic
    libraries and bundled frameworks (i.e., LibreOfficePython), and
    nothing else, go in the Frameworks folder, and all other files go in
    the Resources folder.
    
    Especially, note that Java class files and rc (.ini) files also go in
    Resources.
    
    Such an app bundle structure is what Apple strongly suggests one
    should use, and it has been hinted that future versions of code
    signing and/or Gatekeeper will require such a structure.
    
    There is still some ugliness thanks to traces of the historical
    separation of URE from "the office". Like there are two separate
    "unorc" files, one for URE, one for the LibreOffice application. IMHO,
    this should be cleaned up, but is probably controversial.
    
    (Eek! I now see there are actually *three* unorc files in the app
    bundle. Not intentional. Need to fix that later.)
    
    Change-Id: Idcf235038deb5b8e1d061734993e9f31869b7606




Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.