Re: LibreOfficeLight / iOS

Hi On 5 January 2018 at 06:35, Jon Nermut wrote: > Hi Jan, > I've added the UIScrollView into the mix - you can now scroll and zoom and > it's nicely re-rendering at higher res when zooming. It surprisingly good > for a first cut. Havent tried it on device yet. > > One

Re: LibreOfficeLight / iOS

> Sorry for not being clear - please disable GPGME for iOS (for both > build and host). It currently serves no useful purpose on that > platform, and is certainly not necessary for building. > You were perfectly clear, and it is disabled for the iOS build (== host), but the tools (build-tools) is

Re: LibreOfficeLight / iOS

jan iversen wrote: > I have just checked my different build environments: > > MACOS (works) > Yes. It's supposed to work there. > iOS (tools build but cannot run due to missing libassuan dylib) > > > config_build.mk > > export BUILD_TYPE=... LIBGPGERROR LIBASSUAN GPGMEPP ... > > export

Re: LibreOfficeLight / iOS

> > Ah, for makefiles, use ENABLE_GPGMEPP to check if that's > available. HAVE_FEATURE_GPGME is for source code, and defined in > config_host/config_gpgme.h > I have just checked my different build environments: MACOS (works) config_host.mk export BUILD_TYPE=... LIBGPGERROR LIBASSUAN GPGMEPP

Re: LibreOfficeLight / iOS

jan iversen wrote: > Please advice me, how to disable GPGME for both build and host > configuration. > Ah, for makefiles, use ENABLE_GPGMEPP to check if that's available. HAVE_FEATURE_GPGME is for source code, and defined in config_host/config_gpgme.h Cheers, -- Thorsten signature.asc

Re: LibreOfficeLight / iOS

Manually adding BRAND_SHARE_SUBDIR=share > to fundamentalrc allowed me to render a tile using the CGContext based > code in the unit test, and save it to a png. Woohoo! > > I'm not sure where that should be added? > It is generated in iOS/CustomTarget_iOS_setup.mk line 54-64, once I get my things

Re: LibreOfficeLight / iOS

libassuan is part of the gpg4libre subsystem, and rather certainly not > useful on iOS. I suggest to disable that, like on Android (there's a > feature check define now, HAVE_FEATURE_GPGME). > Thanks for the info, I can see HAVE_FEATURE_GPGME is being defined in configure.ac, but it not declared

Re: LibreOfficeLight / iOS

jan iversen wrote: > I have just updated my master, and now I see your problem with libassuan, > which I am trying to solve. It is being build locally but not copied to the > right place. I did a couple of commits yesterday to a.o. include your idea > on how to make LIBRARY_PATH relative, thanks

Re: LibreOfficeLight / iOS

The tile rendering exception was caused by this path: OUString VclBuilderContainer::getUIRootDir() { OUString sShareLayer( "$BRAND_BASE_DIR/$BRAND_SHARE_SUBDIR/config/soffice.cfg/"); rtl::Bootstrap::expandMacros(sShareLayer); return sShareLayer; } In my build $BRAND_SHARE_SUBDIR

Re: LibreOfficeLight / iOS

Well a framework is effectively dylib *in a bundle*. For swift there is some special module stuff baked in too. So I also moved all the resources to the framework (hence the changes I made to look up the framework bundle instead of the main bundle to find the rc / unorc etc files. You're probably

Re: LibreOfficeLight / iOS

Happy new year, very interesting work. I have just updated my master, and now I see your problem with libassuan, which I am trying to solve. It is being build locally but not copied to the right place. I did a couple of commits yesterday to a.o. include your idea on how to make LIBRARY_PATH

Re: LibreOfficeLight / iOS

try the -r flag which is for prelinking. you can see that in the .mk file And of course a debug version contains tons of symbols in order for the debugger to be able to do its work. > iOS has allowed dylibs since iOS 8 and the introduction of Swift. In fact > you can't produce a static lib with

Re: LibreOfficeLight / iOS

Hi Jan, The way I understand it is that the static libs, the .a files, aren't actually linked yet - they are just an archive of .o object files collected together. When you link the app with the static lib it has to do a full read of the symbols in the .a file and write the relevant ones into the

Re: LibreOfficeLight / iOS

Hi adding dev list to reply, so that others might benefit from the info. Hope you don't mind the unsolicited email, I figured you were the guy to > talk to about this from the git commits. > I am working actively on creating a version of LO for the iPad. So I got it compiling via lode, with

Re: LibreOfficeLight / iOS

BTW: from the marketing perspective (where I came from) I love the name you gave your babe: I would also love to have two apps, for Android the existing "Viewer" what it isn't anymore with the new possibilities for editing e.g. and for iOS your awesome work, both as "LibreOfficeLight".

Re: LibreOfficeLight / iOS

Please do not misunderstand my comments, I am open to any enhancements especially on the linking process of the app...but I would like to see a benefit of the changes. rgds jan I. On 29 December 2017 at 09:36, Jon Nermut wrote: > Thanks for the reply Jan. > > My main

Re: LibreOfficeLight / iOS

On 29 December 2017 at 09:36, Jon Nermut wrote: > Thanks for the reply Jan. > > My main point about BridgeLOKit was that you don't really need to add > another FFI on top of the existing LibreOfficeKit.h FFI. > Swift can import and use the existing _LibreOfficeKit / >

Re: LibreOfficeLight / iOS

Thanks for the reply Jan. My main point about BridgeLOKit was that you don't really need to add another FFI on top of the existing LibreOfficeKit.h FFI. Swift can import and use the existing _LibreOfficeKit / _LibreOfficeKitClass and _LibreOfficeKitDocument / _LibreOfficeKitDocumentClass structs