mir/libreoffice
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
30fe6781ea25659426f2842c299db137304ee085
libreoffice/cppunit/ExternalProject_cppunit.mk

64 lines
2.0 KiB
Makefile
Raw Normal View History

convert cppunit to gbuild Change-Id: Idcba54973940b9f197f2fd84a906b50468d1b166
2012-11-25 16:37:40 -05:00
# -*- Mode: makefile-gmake; tab-width: 4; indent-tabs-mode: t -*-
#
# This file is part of the LibreOffice project.
#
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
#
gbuild: ExternalProject: remove second parameter again... ... now that everything is consistent. Change-Id: I96c15159648815554280202eb1b6d274ead4e7b8
2013-05-06 23:46:30 +02:00
$(eval $(call gb_ExternalProject_ExternalProject,cppunit))
convert cppunit to gbuild Change-Id: Idcba54973940b9f197f2fd84a906b50468d1b166
2012-11-25 16:37:40 -05:00
$(eval $(call gb_ExternalProject_register_targets,cppunit,\
build \
))
ifeq ($(OS)$(COM),WNTMSC)
$(call gb_ExternalProject_get_state_target,cppunit,build) :
quiet external module build log unless failure ExternalProject usually involve a configure and a make step that produce a bunch of output usually irrelevant including a large number of warning and other mess. now that everything is pretty much in tail_build these output get interleaved with useful output from the build of the product and actually drown them in a logorrhea of messy noise. This store the output of external modules in a log file and only print them as a whole if the module failed do build. on a non-verbose build. Change-Id: I3abfcccd6d16821a9e061a71e031b427cc283647 Reviewed-on: https://gerrit.libreoffice.org/2304 Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com> Tested-by: Norbert Thiebaud <nthiebaud@gmail.com>
2013-02-21 08:15:39 -06:00
$(call gb_ExternalProject_run,build,\
adapt all externals to build against MSVC debug runtime Add patches and/or tweaks to the following modules: curl, cppunit, icu, lcms2, libxml2, libxslt, libxmlsec, lpsolve, nss, openssl, python3 lcms2 has an inconsistency where the .lib and the .dll don't agree on the .dll name. openssl gets a honorable mention because apparently it's undocumented custom build system can build with /MDd if one picks the right configuration but i couldn't figure out how to do that in an hour of trying, and just patched the release config instead. Change-Id: I7854a0fc85247e398d561b4f513d09fe2d1ebb3c
2013-04-14 13:52:56 +02:00
msbuild.exe cppunit_dll.vcxproj /p:Configuration=$(if $(MSVC_USE_DEBUG_RUNTIME),Debug,Release) \
quiet external module build log unless failure ExternalProject usually involve a configure and a make step that produce a bunch of output usually irrelevant including a large number of warning and other mess. now that everything is pretty much in tail_build these output get interleaved with useful output from the build of the product and actually drown them in a logorrhea of messy noise. This store the output of external modules in a log file and only print them as a whole if the module failed do build. on a non-verbose build. Change-Id: I3abfcccd6d16821a9e061a71e031b427cc283647 Reviewed-on: https://gerrit.libreoffice.org/2304 Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com> Tested-by: Norbert Thiebaud <nthiebaud@gmail.com>
2013-02-21 08:15:39 -06:00
$(if $(filter 110,$(VCVER)),/p:PlatformToolset=v110 /p:VisualStudioVersion=11.0) \
&& cd ../DllPlugInTester \
adapt all externals to build against MSVC debug runtime Add patches and/or tweaks to the following modules: curl, cppunit, icu, lcms2, libxml2, libxslt, libxmlsec, lpsolve, nss, openssl, python3 lcms2 has an inconsistency where the .lib and the .dll don't agree on the .dll name. openssl gets a honorable mention because apparently it's undocumented custom build system can build with /MDd if one picks the right configuration but i couldn't figure out how to do that in an hour of trying, and just patched the release config instead. Change-Id: I7854a0fc85247e398d561b4f513d09fe2d1ebb3c
2013-04-14 13:52:56 +02:00
&& msbuild.exe DllPlugInTester.vcxproj /p:Configuration=$(if $(MSVC_USE_DEBUG_RUNTIME),Debug,Release) \
quiet external module build log unless failure ExternalProject usually involve a configure and a make step that produce a bunch of output usually irrelevant including a large number of warning and other mess. now that everything is pretty much in tail_build these output get interleaved with useful output from the build of the product and actually drown them in a logorrhea of messy noise. This store the output of external modules in a log file and only print them as a whole if the module failed do build. on a non-verbose build. Change-Id: I3abfcccd6d16821a9e061a71e031b427cc283647 Reviewed-on: https://gerrit.libreoffice.org/2304 Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com> Tested-by: Norbert Thiebaud <nthiebaud@gmail.com>
2013-02-21 08:15:39 -06:00
$(if $(filter 110,$(VCVER)),/p:PlatformToolset=v110 /p:VisualStudioVersion=11.0) \
,src/cppunit)
convert cppunit to gbuild Change-Id: Idcba54973940b9f197f2fd84a906b50468d1b166
2012-11-25 16:37:40 -05:00
else
Probably a good idea to use -D_GLIBCXX_FULLY_DYNAMIC_STRING here, too While at it, do the CXXFLAGS dance on separate lines as appends to a variable for clarity, instead of in-line on the configure command line. Change-Id: I61843ae82efdf341c7e33d3f08d5715a14fa2f40
2013-04-16 13:31:15 +03:00
cppunit_CXXFLAGS=$(CXXFLAGS)
Revert _GLIBCXX_DEBUG on Mac OS X again It does not work, see <http://lists.freedesktop.org/archives/libreoffice/2013-April/050321.html> "Re: [ANN] --enable-dbgutil: everyone gets a Debug STL!" Change-Id: I0b0c0faa03a1a03095b70454d38a1a193b42d56a
2013-04-18 08:38:06 +02:00
ifneq (,$(filter ANDROID DRAGONFLY FREEBSD IOS LINUX NETBSD OPENBSD,$(OS)))
Probably a good idea to use -D_GLIBCXX_FULLY_DYNAMIC_STRING here, too While at it, do the CXXFLAGS dance on separate lines as appends to a variable for clarity, instead of in-line on the configure command line. Change-Id: I61843ae82efdf341c7e33d3f08d5715a14fa2f40
2013-04-16 13:31:15 +03:00
ifneq (,$(gb_ENABLE_DBGUTIL))
cppunit_CXXFLAGS+=-D_GLIBCXX_DEBUG
endif
endif
ifeq ($(OS)-$(COM),WNT-GCC)
cppunit_CXXFLAGS+=-mthreads
endif
ifneq (,$(debug))
cppunit_CXXFLAGS+=-g
endif
convert cppunit to gbuild Change-Id: Idcba54973940b9f197f2fd84a906b50468d1b166
2012-11-25 16:37:40 -05:00
$(call gb_ExternalProject_get_state_target,cppunit,build) :
quiet external module build log unless failure ExternalProject usually involve a configure and a make step that produce a bunch of output usually irrelevant including a large number of warning and other mess. now that everything is pretty much in tail_build these output get interleaved with useful output from the build of the product and actually drown them in a logorrhea of messy noise. This store the output of external modules in a log file and only print them as a whole if the module failed do build. on a non-verbose build. Change-Id: I3abfcccd6d16821a9e061a71e031b427cc283647 Reviewed-on: https://gerrit.libreoffice.org/2304 Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com> Tested-by: Norbert Thiebaud <nthiebaud@gmail.com>
2013-02-21 08:15:39 -06:00
$(call gb_ExternalProject_run,build,\
./configure \
--disable-dependency-tracking \
$(if $(filter TRUE,$(DISABLE_DYNLOADING)),--disable-shared,--disable-static) \
--disable-doxygen \
--disable-html-docs \
--disable-latex-docs \
$(if $(filter YES,$(CROSS_COMPILING)),--build=$(BUILD_PLATFORM) --host=$(HOST_PLATFORM)) \
$(if $(filter MACOSX,$(OS)),--prefix=/@.__________________________________________________NONE) \
$(if $(filter WNT,$(OS)),LDFLAGS="-Wl$(COMMA)--enable-runtime-pseudo-reloc-v2") \
$(if $(filter SOLARIS,$(OS)),LIBS="-lm") \
$(if $(filter ANDROID,$(OS)),LIBS="-lgnustl_shared -lm") \
Probably a good idea to use -D_GLIBCXX_FULLY_DYNAMIC_STRING here, too While at it, do the CXXFLAGS dance on separate lines as appends to a variable for clarity, instead of in-line on the configure command line. Change-Id: I61843ae82efdf341c7e33d3f08d5715a14fa2f40
2013-04-16 13:31:15 +03:00
CXXFLAGS="$(cppunit_CXXFLAGS)" \
quiet external module build log unless failure ExternalProject usually involve a configure and a make step that produce a bunch of output usually irrelevant including a large number of warning and other mess. now that everything is pretty much in tail_build these output get interleaved with useful output from the build of the product and actually drown them in a logorrhea of messy noise. This store the output of external modules in a log file and only print them as a whole if the module failed do build. on a non-verbose build. Change-Id: I3abfcccd6d16821a9e061a71e031b427cc283647 Reviewed-on: https://gerrit.libreoffice.org/2304 Reviewed-by: Norbert Thiebaud <nthiebaud@gmail.com> Tested-by: Norbert Thiebaud <nthiebaud@gmail.com>
2013-02-21 08:15:39 -06:00
&& cd src \
&& $(MAKE) \
)
convert cppunit to gbuild Change-Id: Idcba54973940b9f197f2fd84a906b50468d1b166
2012-11-25 16:37:40 -05:00
endif
# vim: set noet sw=4 ts=4:
Reference in New Issue Copy Permalink