cvs commit: ports/editors/openoffice-2.0-devel Makefile distinfo ports/editors/openoffice-2.0-devel/files Makefile.localized oo_setup.resp openoffice-wrapper

[Nakata Maho]

In Message-ID: <20040614001431.GA75296 at xor.obsecurity.org> 
Kris Kennaway <kris at obsecurity.org> wrote:

Thank you very much for your feedback!

> Have they finally fixed localized builds so they don't compile the
> entire OO package suite?  This is a major headache for package
> building since

This is also my concern. For localized builds, we can build all
the localized version at one time, just adding ALL in configure_args.
however current situation of ports framework, it is quite difficult.

> * The OpenOffice 1.1 builds are not deterministic; they often fail
> with internal errors in random places.

Hmmm...I haven't encounter such situation for FreeBSD 5.2.1-RELEASE.
I restrict supported environment to FreeBSD 5.2.1-RELEASE
so that others can build smoothly. is it better for us to
restrict FreeBSD version? or does it occur
even for FreeBSD 5.2.1-RELEASE?

> >   4) make use of ccache
> 
> Is this a help within one build, or only useful for repeated builds.
> I'm concerned it will have a significant space impact on package
> builds without benefit.

It doesn't help for one build. ONLY useful for repeated builds.
Why I added this is for localized builds, so that we can make full 
use of ccache. ccache remembers what it had complied before by
md5sums of C preprocessor output and command line, etc.

Currently, if we want japanese localized version after
building english version for example
we type
cd /usr/ports/editors/openoffice-1.1/ ; make package
cd /usr/ports/japanese/openoffice-1.1/ ; make package
.
one can easily imagine the next build (Japanese) will use
cached data, but actually not. since command line inclues the location
of work directory. Here is the log of my build.

> ccache g++32 -w -c -I.  -I. -I../inc -I../../../inc -I../../../unx/inc -I../../../unxfbsd.pro/inc -I. -I/work/ports/editors/openoffice-2.0-devel/work/oo_2.0_src/solver/680/unxfbsd.pro/inc/stl -I/work/ports/editors/openoffice-2.0-devel/work/oo_2.0_src/solver/680/unxfbsd.pro/inc/external -I/work/ports/editors/openoffice-2.0-devel/work/oo_2.0_src/solver/680/unxfbsd.pro/inc -I/work/ports/editors/openoffice-2.0-devel/work/oo_2.0_src/solenv/unxfbsd/inc -I/work/ports/editors/openoffice-2.0-devel/work/oo_2.0_src/solenv/inc -I/work/ports/editors/openoffice-2.0-devel/work/oo_2.0_src/res -I/work/ports/editors/openoffice-2.0-devel/work/oo_2.0_src/solver/680/unxfbsd.pro/inc/stl -I/work/ports/editors/openoffice-2.0-devel/work/oo_2.0_src/solenv/inc/Xp31 -I/usr/local/jdk1.4.2/include -I/usr/local/jdk1.4.2/include/freebsd -I/usr/local/jdk1.4.2/include/bsd -I/usr/local/jdk1.4.2/include/native_threads/include -I/us....

/work/ports/editors/openoffice-2.0-devel
will subjected to change for localized one, so ccache recognizes
they are totally different files.

Please see the files/Makefile.localized. for now, Japanese localized
version can build at
cd /usr/ports/editors/openoffice-2.0-devel/ ; make LOCALIZED_LANG=ja USE_CCACHE=yes package

in this case we make full use of ccache.

Your questions are very welcome!

Best regards,
--nakata maho