I found that the main thing to change was in
connectivity/source/drivers/mozab/bootstrap/MNSFolders.cxx. But by running
some tests, it seems that the root directory is ~/.config instead of ~/
Precisely, I put a fourth element to have DefaultProductDir[3][4] instead of
DefaultProductDir[3][3] then I added ".icedove" after the paths
".thunderbird/", ".mozilla-thunderbird/", ".mozilla/thunderbird/" (padded
the other lines of the array with NULL)
It's when I followed on gdb that I saw the .config problem. To be more sure,
I created a link to ~/.icedove in ~/.config and it worked
After some discussion with Caolan, here is the point (I'm quoting Caolan) :
"
::osl::Security::getConfigDir is used to find the config dir for those
mozilla apps. Its a good thing that we honour XDG_CONFIG_HOME for
getConfigDir, but mozilla doesn't use it. Question is whether the fix would
be #ifdef UNX getHomeDir and what the situation is/should be for macosx
"
Moreover, I saw that in MNSFolders.cxx, there's also the variable
"ProductRootEnvironment" which contains : "MOZILLA_PROFILE_ROOT",
"MOZILLA_THUNDERBIRD_PROFILE_ROOT", "MOZILLA_FIREFOX_PROFILE_ROOT" then a
getenv on each String. But none of these are defined on my laptop, no
ICEDOVE equivalent too
Any idea ?
Julien
--
View this message in context:
http://nabble.documentfoundation.org/About-enabling-Icedove-addressbook-connection-for-Base-tp3616221p3636193.html
Sent from the Dev mailing list archive at Nabble.com.
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.