Thx investigating as we speak.
> On Aug 1, 2018, at 8:22 PM, Damjan Jovanovic wrote:
>
> The file:
> /Users/jim/src/asf/AOO420/main/instsetoo_native/
>
The file:
/Users/jim/src/asf/AOO420/main/instsetoo_native/
unxmaccx.pro/Apache_OpenOffice/dmg/install/en-US_inprogress/Apache_OpenOffice_4.2.0_MacOS_x86-64_install_en-US/OpenOffice.app/Contents/program/unopkg
is a small shell script. You should be able to call it manually with the
"sync --verbose
Anyone have any ideas where to start digging around for what
could be causing this last (hopefully!) nit on macOS:
in function: register_extensions
**
in function: register_extensionsstopping log at Fri Jul 27 12:32:08 2018
... removing directory
I'm using:
https://svn.apache.org/repos/asf/openoffice/devtools/build-scripts/4.2.0-dev/unxmacos/build_aoo64bit_on_macos.sh
with '--dev --verbose'
> On Jul 28, 2018, at 12:01 AM, Damjan Jovanovic wrote:
>
> Pleasure :)
>
> No, when got AOO from Oracle, the only documentation for gbuild
Pleasure :)
No, when got AOO from Oracle, the only documentation for gbuild was a few
short notes on wiki pages, eg.
https://wiki.openoffice.org/wiki/Build_Environment_Effort/Module_Migration
I had to figure out AUXTARGETS on my own. I did send out an email some time
ago with some of my own notes
On 7/27/2018 1:32 PM, Jim Jagielski wrote:
> That patch did it. Thx! That is good knowledge to know. Do we
> have a Wiki page somewhere that goes into some level of
> detail regarding the build system? That trick seems like a
> good addition to it.
Hi Jim;
There is always the Apache OpenOffice
That patch did it. Thx! That is good knowledge to know. Do we
have a Wiki page somewhere that goes into some level of
detail regarding the build system? That trick seems like a
good addition to it.
Now we "just" have, afaict, the issue of unpkg failures:
Error: ERROR:
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
On Wed, Jul 25, 2018 at 6:30 PM Jim Jagielski wrote:
> As readers no doubt recall, I'm been struggling with getting
> the latest HEAD of 4.2.0 to build on macOS... The various
> migrations of modules from the old build to gbuild, w/o
> consideration for other platforms has broken things, both
>
On Wed, Jul 25, 2018 at 6:30 PM Jim Jagielski wrote:
> As readers no doubt recall, I'm been struggling with getting
> the latest HEAD of 4.2.0 to build on macOS... The various
> migrations of modules from the old build to gbuild, w/o
> consideration for other platforms has broken things, both
>
Hi
instsetoo_native is the last module that is built, since it's the one
responsible for generating installation packages.
In your error the command "unopkg sync" fails. With our opengrok gone, I
can't easily tell where register_extensions is. Also I wonder if unopkg
sync is called correctly
As readers no doubt recall, I'm been struggling with getting
the latest HEAD of 4.2.0 to build on macOS... The various
migrations of modules from the old build to gbuild, w/o
consideration for other platforms has broken things, both
related to required libs not being linked and/or copied
(fallout
As readers no doubt recall, I'm been struggling with getting
the latest HEAD of 4.2.0 to build on macOS... The various
migrations of modules from the old build to gbuild, w/o
consideration for other platforms has broken things, both
related to required libs not being linked and/or copied
(fallout
As readers no doubt recall, I'm been struggling with getting
the latest HEAD of 4.2.0 to build on macOS... The various
migrations of modules from the old build to gbuild, w/o
consideration for other platforms has broken things, both
related to required libs not being linked and/or copied
(fallout
17 matches
Mail list logo
