kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/databases/qt4-odbc-plugin/Makefile

12 lines
251 B
Makefile
Raw Normal View History

Add NO_STAGE all over the place in preparation for the staging support (cat: databases)
2013-09-20 18:13:47 +02:00
# Created by: Michael Nottebrock <lofi@FreeBSD.org>
Add qt4, a multiplatform C++ application framework
2007-02-05 21:56:24 +01:00
# $FreeBSD$
qt4 sqldrivers: Switch to a proper qmake build, use Makefile.sqldrivers. We've recently started receiving pkg-fallout emails because qt4-mysql-plugin is failing to build in HEAD. It turns out we were using some custom-made Makefile.bsd files to drive the builds, and they did not always register all dependencies between the files correctly. Fix it by switching to a proper qmake build that uses the .pro files shipped with Qt4 itself: they can be used without running the `configure' script almost as if they were not part of the Qt distribution itself. By doing this we can stop having our own Makefiles and also stop setting a lot of variables in the port Makefiles. While here, consolidate most of the variable setting into a single Makefile.sqldrivers in devel/qt4 (like we already do for devel/qt5) so that each of the qt4-*-plugin ports only need to set a few values such as the plugin name and additional USES or includes that might be necessary. Bump PORTREVISION because we now include the debug versions of the plugins in PLIST_FILES when the ports are built with WITH_DEBUG=yes (they were already shipped before, but not registered in the plists).
2016-03-10 15:11:16 +01:00
PORTREVISION= 1
Add qt4, a multiplatform C++ application framework
2007-02-05 21:56:24 +01:00
DB= odbc
qt4 sqldrivers: Switch to a proper qmake build, use Makefile.sqldrivers. We've recently started receiving pkg-fallout emails because qt4-mysql-plugin is failing to build in HEAD. It turns out we were using some custom-made Makefile.bsd files to drive the builds, and they did not always register all dependencies between the files correctly. Fix it by switching to a proper qmake build that uses the .pro files shipped with Qt4 itself: they can be used without running the `configure' script almost as if they were not part of the Qt distribution itself. By doing this we can stop having our own Makefiles and also stop setting a lot of variables in the port Makefiles. While here, consolidate most of the variable setting into a single Makefile.sqldrivers in devel/qt4 (like we already do for devel/qt5) so that each of the qt4-*-plugin ports only need to set a few values such as the plugin name and additional USES or includes that might be necessary. Bump PORTREVISION because we now include the debug versions of the plugins in PLIST_FILES when the ports are built with WITH_DEBUG=yes (they were already shipped before, but not registered in the plists).
2016-03-10 15:11:16 +01:00
COMMENT= Qt Open Database Connectivity plugin
Add qt4, a multiplatform C++ application framework
2007-02-05 21:56:24 +01:00
qt4 sqldrivers: Switch to a proper qmake build, use Makefile.sqldrivers. We've recently started receiving pkg-fallout emails because qt4-mysql-plugin is failing to build in HEAD. It turns out we were using some custom-made Makefile.bsd files to drive the builds, and they did not always register all dependencies between the files correctly. Fix it by switching to a proper qmake build that uses the .pro files shipped with Qt4 itself: they can be used without running the `configure' script almost as if they were not part of the Qt distribution itself. By doing this we can stop having our own Makefiles and also stop setting a lot of variables in the port Makefiles. While here, consolidate most of the variable setting into a single Makefile.sqldrivers in devel/qt4 (like we already do for devel/qt5) so that each of the qt4-*-plugin ports only need to set a few values such as the plugin name and additional USES or includes that might be necessary. Bump PORTREVISION because we now include the debug versions of the plugins in PLIST_FILES when the ports are built with WITH_DEBUG=yes (they were already shipped before, but not registered in the plists).
2016-03-10 15:11:16 +01:00
LIB_DEPENDS= libodbc.so:${PORTSDIR}/databases/unixODBC
Update Qt to 4.8.5 and Qt Creator to 2.8.0. Proudly brought to you by the KDE on FreeBSD team, with commits by makc@, Schaich Alonso and yours truly. Besides the tons of upstream fixes, we have mkspecs for GCC 4.9 and clang33 (from ports), staging support in the Makefiles and dependency fixes related to pkg-config. Many thanks to the people who helped test the ports using our area51 repository, and also to the people who provided patches and bug reports via GNATS! PR: ports/180615 ports/181921 ports/182049
2013-10-14 01:15:50 +02:00
qt4 sqldrivers: Switch to a proper qmake build, use Makefile.sqldrivers. We've recently started receiving pkg-fallout emails because qt4-mysql-plugin is failing to build in HEAD. It turns out we were using some custom-made Makefile.bsd files to drive the builds, and they did not always register all dependencies between the files correctly. Fix it by switching to a proper qmake build that uses the .pro files shipped with Qt4 itself: they can be used without running the `configure' script almost as if they were not part of the Qt distribution itself. By doing this we can stop having our own Makefiles and also stop setting a lot of variables in the port Makefiles. While here, consolidate most of the variable setting into a single Makefile.sqldrivers in devel/qt4 (like we already do for devel/qt5) so that each of the qt4-*-plugin ports only need to set a few values such as the plugin name and additional USES or includes that might be necessary. Bump PORTREVISION because we now include the debug versions of the plugins in PLIST_FILES when the ports are built with WITH_DEBUG=yes (they were already shipped before, but not registered in the plists).
2016-03-10 15:11:16 +01:00
.include "${.CURDIR:H:H}/devel/qt4/Makefile.sqldrivers"
Reference in a new issue Copy permalink