Re: [Libreoffice] [PATCH][PUSHED] Build problems (and some solutions) in Mac OSX

On Tue, Dec 20, 2011 at 12:04 AM, James C
<james.from.wellington@gmail.com> wrote:
> Hello All,
>
> I have burned about 1.5 GB of metered network bandwidth, so far,
> following these instructions:
>
> http://wiki.documentfoundation.org/Development/How_to_build#Getting_the_sources
>
> I have found and, I think fixed, problems which occur on both
> origin/master and origin/libreoffice-3-5, where the test for a
> parallel build bug presumes that mktmp and the thing to do sha1 hash
> sums look like they do on linux.  A patch is attached, which I *think*
> will not break the linux builds.  I release this change under GPLv3
> and MPL, as requested.  I hope that nobody has a software patent on
> the idea of correctness in code :-)

Looks nice, Thanks, pushed.

> There is also a human-sized problem, with some instructions on the
> web-site being wrong:
> https://bugs.freedesktop.org/show_bug.cgi?id=43920
>
> I am now stuck, and have not yet built libre-office.  There are two
> ways forward; one technical and one human.
>
> The technical one is:
>  - my builds of origin/master and origin/libreoffice-3-5 fail in
> pango, because it depends on where cairo gets its fonts from, and on
> Apple Aqua, cairo gets its fonts from quartz, for which the
> corresponding parts of pango seem not to have been written
>
>  - this bug records my journey:
>    https://bugs.freedesktop.org/show_bug.cgi?id=43917
>
>  - I expect that I will not complete it without help
>
>  - how, if at all, is this software buildable under MacOS?
>
> The human one is:
>  - prebuilt LibreOffice 3.4.4 OOO340m1 (Build:402) from here:
>    http://www.libreoffice.org/download/
>    runs on my Mac, so it must be buildable
>
>  - I cannot find the OOO340m1 tag in the git repository that I have
> already invested resources in downloading

1/ no OOO340m1 is _not_ a tag, just a reference to the lasted OOo
version that was 'merged' into lo.

2/ the 3.4 branch was build using a 'split repo' scheme. back then we
had 19 git repos... in august we merged most of them into what is
known as 'core'. see:
http://wiki.documentfoundation.org/Development/One_Git_Conversion for
the gory details...

since then the two repos have diverged... the old set is only used for
maintainling the 3-4 branch... and 3.4.4 occurred after the switch, so
it is not in core.
so, since you already invested in the core repo, you may want to stick
to the 3-5 beta....



>  - I do not understand which pieces of the source I would need, in
> order to play with Writer, and how big they would be

The writer code is in sw.
but you still to build thw 'whole' there is no method to build 'just writer'

>  - please can there be a link on the download page, to an explanation
> of how the various torrents relate to the various repositories?

torrent? you mean for binary download ? if so, I don't think that idea
will be popular. the binary download page is targeted to the public at
large, not develppers.. trying to explain the layout of our source
repo there is going to create more confusion than anything else.

>  - better yet, please can the source for this version be put into the
> repository, and I be told how to change to it?

there is a source download
see
http://www.libreoffice.org/download
and click on 'downalod the source and build your own installer'

the problem is that it is a tar.gz snapshot... making patch will be
problematic 9more exactly up-streaming them. and that method of
building is not very often practiced... so help is scarce.

Now regarding your freetype problem:

1/ you want to send your autogen.lastrun (that will tell us which
options/configuration you used to build... even better the output of
your autogen.sh
2/ some info about extra stuff you have, I presume you have the
pre-req XCode3 with 10.4 SDK, but also pay attention about the
possible nefaste interaction with macports and the like...

The good news is that both 3-5 and master build on MacOSX quite
regularly see: http://tinderbox.libreoffice.org/libreoffice-3-5/status.html,
so it is most likely some local configuration quick that surely can be
fixed :-)

Cheers,

Norbert

PS: thanks again for the patch. Few pointers for the next time: 1/
prefix the subject of the email with [PATCH]. that help us spot them
:-)  2/ if you can, try to learn how to do a commit (locally on your
own copy of git repo). that way you can create a nice patch using git
foramt-patch that is easier for us to apply, and already contain you
name and email (as the author) and preferably a nice comment for the
git log.
see : http://wiki.documentfoundation.org/Development/Patch_Handling_Guideline