Thanks. In the morning today, I shifted to git://gerrit.libreoffice.org/core
master branch and along with the regular iOS build options in README.cross,
I added the options that you had provided but I seem to be getting this
error now somewhere down the line : "~/lo/core/solenv/gbuild/LinkTarget.mk:518:
*** used LinkTarget StaticLibrary/libregistry_helper.a not defined.
Stop.", somewhere here:
"[build ECH] CustomTarget/postprocess/registry/writer.list
[build ECH] CustomTarget/postprocess/registry/xsltfilter.list
[build ECH] CustomTarget/postprocess/registry/Langpack-en-US.list
[build CUS] readlicense_oo/readme
/Users/akochhar/lo/core/solenv/gbuild/LinkTarget.mk:518: *** used
LinkTarget StaticLibrary/libregistry_helper.a not defined. Stop.
make[1]: *** Waiting for unfinished jobs....
make: *** [build] Error 2"
Not sure how close to the build completion I am right now and currently
trying to figure out what might be going wrong here.
On Thu, Oct 8, 2015 at 11:55 AM, Tor Lillqvist <tml@iki.fi> wrote:
On 8 October 2015 at 05:51, Arjun kochhar <arjun.ice@gmail.com> wrote:
I updated configure.ac to consider 9.0 as a possible SDK too, since the
highest value mentioned there was 8.3
Then you must be using some other branch than master, because that was
changed on June 16 in master. Please use the master branch for any iOS
build attempts, as the (very few) iOS-specific fixes I do (I try it maybe
once a month) go into master, not any "stable" branch.
--tml
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.