this isn't a suitable way to develop code.
Indeed not. It is a way to experiment before some saner way exists,
nothing more.
Is that where you got the NSEnumerator stuff?
Most likely, I can't remember writing anything such myself...
I guess it's an antique like all the Mac stuff.
Indeed.
this isn't a suitable way to develop code.
Indeed not. It is a way to experiment before some saner way exists,
nothing more.
Xcode has a way to import makefiles and turn them into projects. I've never
used that feature but it might be a way to use the existing build system.
Is it possible that I don't need module tail_build?
Anyway, that leads to my next question. How do I build an Xcode project that
works like the project you show in your July blog post? Do I just add all
the .a files from core/solver/unxiosr.pro/lib to the project? Is there an
example project I
Tor,
I did a git pull to update my source and I get a different failure, although
of the same kind.
This fails:
from
/Users/brians/develop/libreOffice2/core/solver/unxiosr.pro/inc/sal/main.h:48,
from
/Users/brians/develop/libreOffice2/core/cpputools/source/regsingleton/regsingleton.cxx:32:
Is it possible that I don't need module tail_build?
tail_build is a meta-module that actually builds most of the modules
that have been migrated over to the new gnu make based build system.
It includes all the business logic of Calc, Writer etc, so sure,
stuff from it will be needed.
Anyway,
OK so I fixed the problem in bridges. The includes just needed to be
modified like the mac version of that file.
I'm still not getting a successful build but I'm a few steps closer.
Some comments and questions:
Needless to say there's no need to build the arm bridge if I'm trying to
produce a
Env.Host.sh ends up with
CPUNAME of ARM when I think it ought to be intel.
Well, CPUNAME or CPU aren't used for any deep magic, they are just
strings used to form some directory names etc. I don't think we would
win much by using a separate CPU and CPUNAME string for the iOS
simulator. The only
This one:
[ build C ] desktop/source/app/main
In file included from
/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator4.3.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:9,
from
So - in terms of product shipment, you'll want to use the MPL license;
currently that is not possible - but as/when Oracle have finally managed
to get the code under AL2, we'll be applying all our work on top of that
under MPL/LGPLv3+
Yes, MPL would work better for me. I thought that
Hi Brian,
On Mon, 2011-11-14 at 06:31 -0800, BrianS wrote:
Yes, MPL would work better for me. I thought that Oracle have placed all of
the OO source under AL2.
Well - that is ongoing :-)
But the LO fork was done before that. Is there an announcement that I can
read that describes
I did a fresh get and I get this build error
./autogen.sh --with-distro=LibreOfficeiOS CXX=ccache
/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/g++-4.2 -arch i386
-isysroot
/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator4.3.sdk
CC=ccache
I am sorry to say this, but it is fairly pointless to try to build for
iOS at this stage if you are not also prepared to dig into the
problems you will encounter and fix them, sorry.
Nobody is actively working on the iOS port right now. (As for myself I
am concentrating on the Android port at the
On Fri, 2011-11-11 at 08:30 -0800, BrianS wrote:
I might be interested in including some LO source in my app, if that can be
made to work technically and within License restrictions.
So - in terms of product shipment, you'll want to use the MPL license;
currently that is not possible -
I think I've read everything on this topic that Mr Google helped me to find.
// This succeeded
./autogen.sh --with-distro=LibreOfficeiOS CXX=ccache
/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/g++-4.2 -arch armv7
-isysroot
I get this build error:
/Users/brians/develop/libreOffice/libo/bridges/source/cpp_uno/gcc3_ios_arm/cpp2uno.cxx:491:
OK, I haven't actually compiled for the device much lately, only for
the simulator, so some bit rot might have happened. I suggest you just
compile for the simulator for now.
./autogen.sh --with-distro=LibreOfficeiOS CXX=ccache
/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/g++-4.2 -arch i386
-isysroot
/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator4.3.sdk
CC=ccache /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/gcc-4.2
./soffice --convert-to pdf foo.docx
Yup. Something like that should be doable relatively soon,
How do you imagine something like that working? As you probably know IPC
on
iOS is restricted in some ways.
I have no idea;) The command line above was just to give an idea of
how such
Entering /Users/brians/develop/libreOffice/libo/l10ntools/source
Ah OK, l10ntools. That is a module it shouldn't even be building for
non-desktop OSes. It contains some command-line tools that make no
sense on iOS (or Android). No libraries that actual LO code would use
are built in l10ntools as
Hi All,
I'm interested in the possibility of using parts of LO to convert documents
from .doc and related formats to .pdf on iOS. I know that the port of LO to
iOS is underway but honestly I've had some difficulty building it. Is it
likely to be possible to take a subset of LO for this purpose of
Hi Brian,
On Thu, 2011-11-10 at 13:59 -0800, BrianS wrote:
I'm interested in the possibility of using parts of LO to convert documents
from .doc and related formats to .pdf on iOS.
Great - sounds like it overlaps with Tor's Android work quite nicely,
it'd be fantastic to have you
Ok I have my confirmation of being removed from this list, why am I
still receiving e-mails?
On 11/10/2011 4:59 PM, BrianS wrote:
Hi All,
I'm interested in the possibility of using parts of LO to convert documents
from .doc and related formats to .pdf on iOS. I know that the port of LO to
iOS
That's quite normal, you've read README.cross ? :-) also more concrete
details on the specific problems would be good.
Also, http://www.iki.fi/tml/libocon2011-xcompiling.pdf gives an
overview of LibeOffice cross-compilation in general.
I've had some difficulty building it.
Please give more
22 matches
Mail list logo
