Use your commit and attach to the url ".patch", so
https://github.com/apache/openoffice/commit/ba72a0641c1b077c4de326a8da20fc7252b99bc1.patch
Hope that helps.
--- original message ---
From: FR web forum
Date: 26.07.2018 15:53:15
To: dev@openoffice.apache.org
Subject: Re: Patch through Github
The reason I asked for the final Mac AOO installation package filenames of
jpipe, is because I need to understand the interaction between the .dylib
and .jnilib files during delivery and packaging.
For example in a similar problem on *nix, in
main/solver/420/unxfbsdx/workdir/LinkTarget/Library I
In previous versions and, in fact, before jurt was ported to gbuild, all worked
as it should. the macosx.mk makefile took care of the symlinking as well
as ensuring that the jnilib file came along for the ride.
$(if $(filter Library,$(TARGETTYPE)),\
$(PERL)
That looks right.
You were saying libjpipe.jnilib doesn't get copied over. If it doesn't
appear in that output, it won't be.
My Mac experience is pretty minimal, but grepping through main/solenv/inc
and reading main/solenv/macosx-create-bundle seems to say how libfoo.jnilib
is a symlink back to
%# make showdeliverables
/Users/jim/src/asf/AOO420/main/solver/420/unxmaccx.pro/workdir/Ant/jurt.jar
/Users/jim/src/asf/AOO420/main/solver/420/unxmaccx.pro/bin/jurt.jar
/Users/jim/src/asf/AOO420/main/solver/420/unxmaccx.pro/workdir/LinkTarget/Library/libjpipe.dylib
Ah that will be fine
Thanks Matthias
- Mail original -
> De: "Matthias Seidel"
> À: dev@openoffice.apache.org
> Envoyé: Jeudi 26 Juillet 2018 16:03:00
> Objet: Re: Patch through Github
>
> Hi,
>
> Am 26.07.2018 um 15:53 schrieb FR web forum:
> > Thanks for this answer
> > I know that I
Hi,
Am 26.07.2018 um 15:53 schrieb FR web forum:
> Thanks for this answer
> I know that I can do it with SVN
> But this is too heavy for me to download all aoo-trunk files.
> Is it possible to create a patch from Github and then submit to BZ?
I don't know.
But since it is only two lines, I will
All my VMs are VMware Fusion images.
> On Jul 25, 2018, at 5:34 PM, Peter Kovacs wrote:
>
> Hi all,
>
> We had this Idea to collect VMs for all our supported systems.
>
> Is this still on?
>
> Can we have a MacOS VM too? I never got that setup on my Macbook Air.
>
> I am sure we manage to
Thanks for this answer
I know that I can do it with SVN
But this is too heavy for me to download all aoo-trunk files.
Is it possible to create a patch from Github and then submit to BZ?
- Mail original -
> De: "Matthias Seidel"
> À: dev@openoffice.apache.org
> Envoyé: Jeudi 26 Juillet
Hi,
I think GitHub is "readonly".
Contributions can be made with subversion:
https://openoffice.apache.org/source.html
https://openoffice.apache.org/contributing-code.html
Or you can attach a patch file to the specific issue in Bugzilla.
Did you test the code or would you be interested in a
Hello dev team,
Is it a right way to submit patch through Github?
https://github.com/apache/openoffice/pulls
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail:
> -Original Message-
> From: Marcus [mailto:marcus.m...@wtnet.de]
> Sent: Wednesday, July 25, 2018 10:26 PM
> To: dev@openoffice.apache.org
> Cc: Rainer Schlegel
> Subject: Re: Probleme im Calc
>
> Please note that this mailing list is international and therefore for
> English only
12 matches
Mail list logo
