2010-11-11 01:42:52 -06:00
|
|
|
# @configure_input@
|
2010-08-18 10:48:07 -05:00
|
|
|
|
2010-12-07 03:30:05 -06:00
|
|
|
SHELL=/usr/bin/env bash
|
2010-08-18 10:48:07 -05:00
|
|
|
|
2011-01-10 01:05:38 -06:00
|
|
|
ifeq ($(USE_GMAKE),)
|
|
|
|
|
GBUILD_OPT:=
|
|
|
|
|
else
|
|
|
|
|
GBUILD_OPT:=--gmake
|
|
|
|
|
endif
|
|
|
|
|
|
2011-04-20 08:30:08 -05:00
|
|
|
prefix = @prefix@
|
|
|
|
|
exec_prefix = @exec_prefix@
|
|
|
|
|
libdir = @libdir@
|
2011-01-10 01:05:38 -06:00
|
|
|
|
Rehash of cross-compilation ideas
Like in my previous plan, when cross-compiling we run the same
configure script separately for a native build configuration on the
build platform, in a temporary subdirectory.
Now use a fixed name "CONF-FOR-BUILD" for that subdirectory, so that
it is easy to edit out that path component from those build
environment variables that contain it.
Pass more of the native build environment variables up to the main
configure and propagate those to the build environment suffixed with
_FOR_BUILD: INPATH, OUTPATH OUTDIR, PATH, SOLARINC, SOLARLIB,
WORKDIR. Whether these all will actually be needed remains to be seen,
the set can be reduced later.
The environment setting file (*Env.Set.sh) for the native build is
copied here to the top directory under the name Env.Build.sh, and the
environment variables set in it that contain pathnames are modified to
point directly to this top directory, not the temporary CONF-FOR-BUILD
subdirectory.
When doing a cross-compiling build, we first do a build of the
necessary build-time tools for the build platform. This is done in the
same source tree. As the directories where build results are stored
include the platform specification (OUTPATH or in some cases INPATH),
there should be no clashes.
Don't run the download script from ./bootstrap(.1). We are running it
from Makefile already anyway often enough. This could also do with
some clean-up; the ./g -f clone phase is a bit slow, I am not sure if
it really is necessary every time? Also, we should not overwrite
ooo.lst if its contents isn't changing.
Use INPATH_FOR_BUILD in SOLARBINDIR so that the self-built tools like
idlc that we run are for the build platform, not the host
platform.
Attempt to get rid of the makefile.rc and makefile.mk files. Surely it
should be enough with just Makefile(.in) (and then GNUmakefile.mk for
its own so far special gbuild purposes). Instead of invoking dmake to
do "clean" or "distclean" from Makefile(.in), we already just do the
same directly in Makefile(.in). This way we don't need to first build
dmake in order to be able to do a make clean, which will then finally
clean out dmake again;)
Ideally I would like to get rid of bootstrap(.1), too. It should be
possible to merge its tasks into configure(.in) or Makefile(.in) as
appropriate.
And actually, maybe also what set_soenv(.in) does could well be merged
into configure(.in)?
2011-06-04 06:59:34 -05:00
|
|
|
ifeq (@CROSS_COMPILING@,YES)
|
|
|
|
|
all: Makefile dmake/dmake@EXEEXT_FOR_BUILD@ src.downloaded cross-build-toolset
|
|
|
|
|
else
|
2011-05-27 13:39:04 -05:00
|
|
|
all: Makefile dmake/dmake@EXEEXT_FOR_BUILD@ src.downloaded
|
Rehash of cross-compilation ideas
Like in my previous plan, when cross-compiling we run the same
configure script separately for a native build configuration on the
build platform, in a temporary subdirectory.
Now use a fixed name "CONF-FOR-BUILD" for that subdirectory, so that
it is easy to edit out that path component from those build
environment variables that contain it.
Pass more of the native build environment variables up to the main
configure and propagate those to the build environment suffixed with
_FOR_BUILD: INPATH, OUTPATH OUTDIR, PATH, SOLARINC, SOLARLIB,
WORKDIR. Whether these all will actually be needed remains to be seen,
the set can be reduced later.
The environment setting file (*Env.Set.sh) for the native build is
copied here to the top directory under the name Env.Build.sh, and the
environment variables set in it that contain pathnames are modified to
point directly to this top directory, not the temporary CONF-FOR-BUILD
subdirectory.
When doing a cross-compiling build, we first do a build of the
necessary build-time tools for the build platform. This is done in the
same source tree. As the directories where build results are stored
include the platform specification (OUTPATH or in some cases INPATH),
there should be no clashes.
Don't run the download script from ./bootstrap(.1). We are running it
from Makefile already anyway often enough. This could also do with
some clean-up; the ./g -f clone phase is a bit slow, I am not sure if
it really is necessary every time? Also, we should not overwrite
ooo.lst if its contents isn't changing.
Use INPATH_FOR_BUILD in SOLARBINDIR so that the self-built tools like
idlc that we run are for the build platform, not the host
platform.
Attempt to get rid of the makefile.rc and makefile.mk files. Surely it
should be enough with just Makefile(.in) (and then GNUmakefile.mk for
its own so far special gbuild purposes). Instead of invoking dmake to
do "clean" or "distclean" from Makefile(.in), we already just do the
same directly in Makefile(.in). This way we don't need to first build
dmake in order to be able to do a make clean, which will then finally
clean out dmake again;)
Ideally I would like to get rid of bootstrap(.1), too. It should be
possible to merge its tasks into configure(.in) or Makefile(.in) as
appropriate.
And actually, maybe also what set_soenv(.in) does could well be merged
into configure(.in)?
2011-06-04 06:59:34 -05:00
|
|
|
endif
|
2011-05-16 18:22:19 -05:00
|
|
|
@. ./*Env.Set.sh && \
|
2010-11-11 01:42:52 -06:00
|
|
|
cd instsetoo_native && \
|
2011-01-10 01:05:38 -06:00
|
|
|
build.pl $(GBUILD_OPT) -P@BUILD_NCPUS@ --all -- -P@BUILD_MAX_JOBS@
|
2010-08-18 10:48:07 -05:00
|
|
|
|
Rehash of cross-compilation ideas
Like in my previous plan, when cross-compiling we run the same
configure script separately for a native build configuration on the
build platform, in a temporary subdirectory.
Now use a fixed name "CONF-FOR-BUILD" for that subdirectory, so that
it is easy to edit out that path component from those build
environment variables that contain it.
Pass more of the native build environment variables up to the main
configure and propagate those to the build environment suffixed with
_FOR_BUILD: INPATH, OUTPATH OUTDIR, PATH, SOLARINC, SOLARLIB,
WORKDIR. Whether these all will actually be needed remains to be seen,
the set can be reduced later.
The environment setting file (*Env.Set.sh) for the native build is
copied here to the top directory under the name Env.Build.sh, and the
environment variables set in it that contain pathnames are modified to
point directly to this top directory, not the temporary CONF-FOR-BUILD
subdirectory.
When doing a cross-compiling build, we first do a build of the
necessary build-time tools for the build platform. This is done in the
same source tree. As the directories where build results are stored
include the platform specification (OUTPATH or in some cases INPATH),
there should be no clashes.
Don't run the download script from ./bootstrap(.1). We are running it
from Makefile already anyway often enough. This could also do with
some clean-up; the ./g -f clone phase is a bit slow, I am not sure if
it really is necessary every time? Also, we should not overwrite
ooo.lst if its contents isn't changing.
Use INPATH_FOR_BUILD in SOLARBINDIR so that the self-built tools like
idlc that we run are for the build platform, not the host
platform.
Attempt to get rid of the makefile.rc and makefile.mk files. Surely it
should be enough with just Makefile(.in) (and then GNUmakefile.mk for
its own so far special gbuild purposes). Instead of invoking dmake to
do "clean" or "distclean" from Makefile(.in), we already just do the
same directly in Makefile(.in). This way we don't need to first build
dmake in order to be able to do a make clean, which will then finally
clean out dmake again;)
Ideally I would like to get rid of bootstrap(.1), too. It should be
possible to merge its tasks into configure(.in) or Makefile(.in) as
appropriate.
And actually, maybe also what set_soenv(.in) does could well be merged
into configure(.in)?
2011-06-04 06:59:34 -05:00
|
|
|
ifeq (@CROSS_COMPILING@,YES)
|
|
|
|
|
cross-build-toolset:
|
|
|
|
|
. ./Env.Build.sh && \
|
|
|
|
|
(cd idlc && build.pl $(GBUILD_OPT) -P@BUILD_NCPUS@ --all -- -P@BUILD_MAX_JOBS@ && deliver.pl) && \
|
2011-06-04 18:02:14 -05:00
|
|
|
(cd icu && build.pl $(GBUILD_OPT) -P@BUILD_NCPUS@ --all -- -P@BUILD_MAX_JOBS@) && \
|
|
|
|
|
(cd udkapi && build.pl $(GBUILD_OPT) -P@BUILD_NCPUS@ --all -- -P@BUILD_MAX_JOBS@ && deliver.pl) && \
|
|
|
|
|
(cd ridljar && build.pl $(GBUILD_OPT) -P@BUILD_NCPUS@ --all -- -P@BUILD_MAX_JOBS@ && deliver.pl)
|
Rehash of cross-compilation ideas
Like in my previous plan, when cross-compiling we run the same
configure script separately for a native build configuration on the
build platform, in a temporary subdirectory.
Now use a fixed name "CONF-FOR-BUILD" for that subdirectory, so that
it is easy to edit out that path component from those build
environment variables that contain it.
Pass more of the native build environment variables up to the main
configure and propagate those to the build environment suffixed with
_FOR_BUILD: INPATH, OUTPATH OUTDIR, PATH, SOLARINC, SOLARLIB,
WORKDIR. Whether these all will actually be needed remains to be seen,
the set can be reduced later.
The environment setting file (*Env.Set.sh) for the native build is
copied here to the top directory under the name Env.Build.sh, and the
environment variables set in it that contain pathnames are modified to
point directly to this top directory, not the temporary CONF-FOR-BUILD
subdirectory.
When doing a cross-compiling build, we first do a build of the
necessary build-time tools for the build platform. This is done in the
same source tree. As the directories where build results are stored
include the platform specification (OUTPATH or in some cases INPATH),
there should be no clashes.
Don't run the download script from ./bootstrap(.1). We are running it
from Makefile already anyway often enough. This could also do with
some clean-up; the ./g -f clone phase is a bit slow, I am not sure if
it really is necessary every time? Also, we should not overwrite
ooo.lst if its contents isn't changing.
Use INPATH_FOR_BUILD in SOLARBINDIR so that the self-built tools like
idlc that we run are for the build platform, not the host
platform.
Attempt to get rid of the makefile.rc and makefile.mk files. Surely it
should be enough with just Makefile(.in) (and then GNUmakefile.mk for
its own so far special gbuild purposes). Instead of invoking dmake to
do "clean" or "distclean" from Makefile(.in), we already just do the
same directly in Makefile(.in). This way we don't need to first build
dmake in order to be able to do a make clean, which will then finally
clean out dmake again;)
Ideally I would like to get rid of bootstrap(.1), too. It should be
possible to merge its tasks into configure(.in) or Makefile(.in) as
appropriate.
And actually, maybe also what set_soenv(.in) does could well be merged
into configure(.in)?
2011-06-04 06:59:34 -05:00
|
|
|
endif
|
|
|
|
|
|
2010-12-01 03:47:46 -06:00
|
|
|
install:
|
2011-05-16 18:22:19 -05:00
|
|
|
@. ./*Env.Set.sh && \
|
2011-04-20 08:30:08 -05:00
|
|
|
echo "Installing in $${libdir:-@libdir@}/@INSTALL_DIRNAME@..." && \
|
|
|
|
|
ooinstall "$${libdir:-@libdir@}/@INSTALL_DIRNAME@" && \
|
2010-12-01 03:47:46 -06:00
|
|
|
echo "" && \
|
|
|
|
|
echo "Installation finished, you can now execute:" && \
|
2011-04-20 08:30:08 -05:00
|
|
|
echo "$${libdir:-@libdir@}/@INSTALL_DIRNAME@/program/soffice"
|
2010-09-16 13:40:40 -05:00
|
|
|
|
2010-08-20 09:43:34 -05:00
|
|
|
dev-install:
|
2011-05-16 18:22:19 -05:00
|
|
|
@. ./*Env.Set.sh && \
|
2011-05-23 04:22:39 -05:00
|
|
|
cd smoketestoo_native && \
|
2011-05-25 03:23:06 -05:00
|
|
|
export SAL_USE_VCLPLUGIN="svp" && \
|
2011-05-23 04:22:39 -05:00
|
|
|
build.pl $(GBUILD_OPT) -P@BUILD_NCPUS@ --all -- -P@BUILD_MAX_JOBS@ && \
|
2011-05-25 16:53:06 -05:00
|
|
|
cd @abs_builddir@ && ln -s $$SOLARVER/$$INPATH/installation/opt/ install && \
|
2011-05-23 04:22:39 -05:00
|
|
|
echo "" && \
|
2011-05-31 18:27:25 -05:00
|
|
|
echo "Developer installation finished, you can now execute:"
|
|
|
|
|
@if test `uname -s` = Darwin; then \
|
|
|
|
|
echo open install/LibreOffice.app; \
|
|
|
|
|
else \
|
|
|
|
|
echo "cd @abs_builddir@/install/program" && \
|
2011-05-24 11:25:42 -05:00
|
|
|
echo ". ooenv" && \
|
2011-05-31 18:27:25 -05:00
|
|
|
echo "./soffice.bin"; \
|
|
|
|
|
fi
|
2010-12-01 03:47:46 -06:00
|
|
|
|
Rehash of cross-compilation ideas
Like in my previous plan, when cross-compiling we run the same
configure script separately for a native build configuration on the
build platform, in a temporary subdirectory.
Now use a fixed name "CONF-FOR-BUILD" for that subdirectory, so that
it is easy to edit out that path component from those build
environment variables that contain it.
Pass more of the native build environment variables up to the main
configure and propagate those to the build environment suffixed with
_FOR_BUILD: INPATH, OUTPATH OUTDIR, PATH, SOLARINC, SOLARLIB,
WORKDIR. Whether these all will actually be needed remains to be seen,
the set can be reduced later.
The environment setting file (*Env.Set.sh) for the native build is
copied here to the top directory under the name Env.Build.sh, and the
environment variables set in it that contain pathnames are modified to
point directly to this top directory, not the temporary CONF-FOR-BUILD
subdirectory.
When doing a cross-compiling build, we first do a build of the
necessary build-time tools for the build platform. This is done in the
same source tree. As the directories where build results are stored
include the platform specification (OUTPATH or in some cases INPATH),
there should be no clashes.
Don't run the download script from ./bootstrap(.1). We are running it
from Makefile already anyway often enough. This could also do with
some clean-up; the ./g -f clone phase is a bit slow, I am not sure if
it really is necessary every time? Also, we should not overwrite
ooo.lst if its contents isn't changing.
Use INPATH_FOR_BUILD in SOLARBINDIR so that the self-built tools like
idlc that we run are for the build platform, not the host
platform.
Attempt to get rid of the makefile.rc and makefile.mk files. Surely it
should be enough with just Makefile(.in) (and then GNUmakefile.mk for
its own so far special gbuild purposes). Instead of invoking dmake to
do "clean" or "distclean" from Makefile(.in), we already just do the
same directly in Makefile(.in). This way we don't need to first build
dmake in order to be able to do a make clean, which will then finally
clean out dmake again;)
Ideally I would like to get rid of bootstrap(.1), too. It should be
possible to merge its tasks into configure(.in) or Makefile(.in) as
appropriate.
And actually, maybe also what set_soenv(.in) does could well be merged
into configure(.in)?
2011-06-04 06:59:34 -05:00
|
|
|
distclean:
|
|
|
|
|
-rm config.cache
|
|
|
|
|
-rm config.log
|
|
|
|
|
ifeq (@BUILD_DMAKE@,YES)
|
|
|
|
|
-$(GNUMAKE) -C dmake distclean
|
|
|
|
|
endif
|
2010-12-01 03:47:46 -06:00
|
|
|
|
Rehash of cross-compilation ideas
Like in my previous plan, when cross-compiling we run the same
configure script separately for a native build configuration on the
build platform, in a temporary subdirectory.
Now use a fixed name "CONF-FOR-BUILD" for that subdirectory, so that
it is easy to edit out that path component from those build
environment variables that contain it.
Pass more of the native build environment variables up to the main
configure and propagate those to the build environment suffixed with
_FOR_BUILD: INPATH, OUTPATH OUTDIR, PATH, SOLARINC, SOLARLIB,
WORKDIR. Whether these all will actually be needed remains to be seen,
the set can be reduced later.
The environment setting file (*Env.Set.sh) for the native build is
copied here to the top directory under the name Env.Build.sh, and the
environment variables set in it that contain pathnames are modified to
point directly to this top directory, not the temporary CONF-FOR-BUILD
subdirectory.
When doing a cross-compiling build, we first do a build of the
necessary build-time tools for the build platform. This is done in the
same source tree. As the directories where build results are stored
include the platform specification (OUTPATH or in some cases INPATH),
there should be no clashes.
Don't run the download script from ./bootstrap(.1). We are running it
from Makefile already anyway often enough. This could also do with
some clean-up; the ./g -f clone phase is a bit slow, I am not sure if
it really is necessary every time? Also, we should not overwrite
ooo.lst if its contents isn't changing.
Use INPATH_FOR_BUILD in SOLARBINDIR so that the self-built tools like
idlc that we run are for the build platform, not the host
platform.
Attempt to get rid of the makefile.rc and makefile.mk files. Surely it
should be enough with just Makefile(.in) (and then GNUmakefile.mk for
its own so far special gbuild purposes). Instead of invoking dmake to
do "clean" or "distclean" from Makefile(.in), we already just do the
same directly in Makefile(.in). This way we don't need to first build
dmake in order to be able to do a make clean, which will then finally
clean out dmake again;)
Ideally I would like to get rid of bootstrap(.1), too. It should be
possible to merge its tasks into configure(.in) or Makefile(.in) as
appropriate.
And actually, maybe also what set_soenv(.in) does could well be merged
into configure(.in)?
2011-06-04 06:59:34 -05:00
|
|
|
clean:
|
|
|
|
|
. ./*Env.Set.sh && \
|
|
|
|
|
rm -rf */$$INPATH && \
|
|
|
|
|
rm -rf solver/*/$$INPATH && \
|
|
|
|
|
rm -rf install && \
|
|
|
|
|
$$GNUMAKE -C dmake clean && \
|
|
|
|
|
rm -f solenv/*/bin/dmake* && \
|
|
|
|
|
$$GNUMAKE -f GNUmakefile.mk -sr clean
|
|
|
|
|
ifeq (@CROSS_COMPILING@,YES)
|
|
|
|
|
. ./*Env.Set.sh && \
|
|
|
|
|
rm -rf */$$INPATH_FOR_BUILD && \
|
|
|
|
|
rm -rf solver/*/$$INPATH_FOR_BUILD
|
|
|
|
|
endif
|
2010-12-01 03:47:46 -06:00
|
|
|
|
2011-05-16 18:22:19 -05:00
|
|
|
dmake/dmake@EXEEXT_FOR_BUILD@:
|
Rehash of cross-compilation ideas
Like in my previous plan, when cross-compiling we run the same
configure script separately for a native build configuration on the
build platform, in a temporary subdirectory.
Now use a fixed name "CONF-FOR-BUILD" for that subdirectory, so that
it is easy to edit out that path component from those build
environment variables that contain it.
Pass more of the native build environment variables up to the main
configure and propagate those to the build environment suffixed with
_FOR_BUILD: INPATH, OUTPATH OUTDIR, PATH, SOLARINC, SOLARLIB,
WORKDIR. Whether these all will actually be needed remains to be seen,
the set can be reduced later.
The environment setting file (*Env.Set.sh) for the native build is
copied here to the top directory under the name Env.Build.sh, and the
environment variables set in it that contain pathnames are modified to
point directly to this top directory, not the temporary CONF-FOR-BUILD
subdirectory.
When doing a cross-compiling build, we first do a build of the
necessary build-time tools for the build platform. This is done in the
same source tree. As the directories where build results are stored
include the platform specification (OUTPATH or in some cases INPATH),
there should be no clashes.
Don't run the download script from ./bootstrap(.1). We are running it
from Makefile already anyway often enough. This could also do with
some clean-up; the ./g -f clone phase is a bit slow, I am not sure if
it really is necessary every time? Also, we should not overwrite
ooo.lst if its contents isn't changing.
Use INPATH_FOR_BUILD in SOLARBINDIR so that the self-built tools like
idlc that we run are for the build platform, not the host
platform.
Attempt to get rid of the makefile.rc and makefile.mk files. Surely it
should be enough with just Makefile(.in) (and then GNUmakefile.mk for
its own so far special gbuild purposes). Instead of invoking dmake to
do "clean" or "distclean" from Makefile(.in), we already just do the
same directly in Makefile(.in). This way we don't need to first build
dmake in order to be able to do a make clean, which will then finally
clean out dmake again;)
Ideally I would like to get rid of bootstrap(.1), too. It should be
possible to merge its tasks into configure(.in) or Makefile(.in) as
appropriate.
And actually, maybe also what set_soenv(.in) does could well be merged
into configure(.in)?
2011-06-04 06:59:34 -05:00
|
|
|
./bootstrap
|
2010-12-02 04:47:13 -06:00
|
|
|
|
2011-01-08 11:45:25 -06:00
|
|
|
src.downloaded: ooo.lst download
|
2011-05-16 18:22:19 -05:00
|
|
|
@. ./*Env.Set.sh && \
|
2010-12-02 04:47:13 -06:00
|
|
|
$$SRC_ROOT/download $$SRC_ROOT/ooo.lst && touch $@
|
|
|
|
|
|
2011-01-08 11:45:25 -06:00
|
|
|
fetch: src.downloaded
|
2010-12-02 08:06:21 -06:00
|
|
|
|
2010-12-16 04:17:30 -06:00
|
|
|
Makefile: configure.in set_soenv.in Makefile.in
|
|
|
|
|
./autogen.sh
|
|
|
|
|
|
2011-05-16 18:22:19 -05:00
|
|
|
check: Makefile dmake/dmake@EXEEXT_FOR_BUILD@ fetch
|
|
|
|
|
@. ./*Env.Set.sh && \
|
2010-12-02 08:06:21 -06:00
|
|
|
cd smoketestoo_native && \
|
|
|
|
|
export SAL_USE_VCLPLUGIN="svp" && \
|
2011-01-10 01:05:38 -06:00
|
|
|
build.pl $(GBUILD_OPT) -P@BUILD_NCPUS@ --all -- -P@BUILD_MAX_JOBS@
|
2011-05-24 09:33:07 -05:00
|
|
|
@. ./*Env.Set.sh && $$SOLARENV/bin/subsequenttests
|
2010-12-13 15:47:09 -06:00
|
|
|
|
|
|
|
|
id:
|
2011-05-16 18:22:19 -05:00
|
|
|
@. ./*Env.Set.sh && \
|
2010-12-13 15:47:09 -06:00
|
|
|
create-ids
|
|
|
|
|
|
|
|
|
|
tags:
|
2011-05-16 18:22:19 -05:00
|
|
|
@. ./*Env.Set.sh && \
|
2010-12-13 15:47:09 -06:00
|
|
|
create-tags
|
|
|
|
|
|
|
|
|
|
docs:
|
2011-05-16 18:22:19 -05:00
|
|
|
@. ./*Env.Set.sh && \
|
2010-12-13 15:47:09 -06:00
|
|
|
mkdocs.sh $$SRC_ROOT/docs $$SOLARENV/inc/doxygen.cfg
|
