kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/databases/myodbc/options.mk

33 lines
900 B
Makefile
Raw Normal View History

Changes 5.1.8: * Documentation in .CHM and .HLP format has been removed from the distribution. * For some procedure and parameter combinations SQLProcedureColumns() did not work correctly. For example, it could not return records for an existing procedure with correct parameters supplied. * Further, it returned incorrect data for column 7, TYPE_NAME. For example, it returned VARCHAR(20) instead of VARCHAR. * The MySQL Connector/ODBC MSI installer did not set the InstallLocation value in the Microsoft Windows registry. * In bulk upload mode, SQLExecute would return SQL_SUCCESS, even when the uploaded data contained errors, such as primary key duplication, and foreign key violation. * SQLDescribeCol and SQLColAttribute could not be called before SQLExecute, if the query was parameterized and not all parameters were bound. * Note, MSDN states that “For performance reasons, an application should not call SQLColAttribute/SQLDescribeCol before executing a statement.” However, it should still be possible to do so if performance reasons are not paramount. * When SQLNumResultCols() was called between SQLPrepare() and SQLExecute() the driver ran SET @@sql_select_limit=1, which limited the resultset to just one row. * After installing MySQL Connector/ODBC, the system DSN created could not be configured or deleted. An error dialog was displayed, showing the error message “Invalid attribute string”. * In this case the problem was due to the fact that the driver could not parse the NULL-separated connection string. * When used after a call to SQLTables(), SQLRowCount() did not return the correct value.
2011-08-19 09:59:58 +02:00
# $NetBSD: options.mk,v 1.5 2011/08/19 07:59:58 adam Exp $
Update to 3.51.12 (latest stable version). There were zillions of changes... please see the Changelog file. Now it builds with both mysql-4.1.x and mysql-5.1.x. pkgsrc changes: Supported build options: * myodbc-gui: builds the QT widgets library. (disabled) * myodbc-iodbc: uses iodbc for the odbc functions. (enabled) * myodbc-unixodbc: uses unixodbc for the odbc functions. (disabled) Uses MASTER_SITE_MYSQL.
2006-01-23 19:53:45 +01:00
PKG_OPTIONS_VAR= PKG_OPTIONS.myodbc
PKG_OPTIONS_REQUIRED_GROUPS= db
Changes 5.1.8: * Documentation in .CHM and .HLP format has been removed from the distribution. * For some procedure and parameter combinations SQLProcedureColumns() did not work correctly. For example, it could not return records for an existing procedure with correct parameters supplied. * Further, it returned incorrect data for column 7, TYPE_NAME. For example, it returned VARCHAR(20) instead of VARCHAR. * The MySQL Connector/ODBC MSI installer did not set the InstallLocation value in the Microsoft Windows registry. * In bulk upload mode, SQLExecute would return SQL_SUCCESS, even when the uploaded data contained errors, such as primary key duplication, and foreign key violation. * SQLDescribeCol and SQLColAttribute could not be called before SQLExecute, if the query was parameterized and not all parameters were bound. * Note, MSDN states that “For performance reasons, an application should not call SQLColAttribute/SQLDescribeCol before executing a statement.” However, it should still be possible to do so if performance reasons are not paramount. * When SQLNumResultCols() was called between SQLPrepare() and SQLExecute() the driver ran SET @@sql_select_limit=1, which limited the resultset to just one row. * After installing MySQL Connector/ODBC, the system DSN created could not be configured or deleted. An error dialog was displayed, showing the error message “Invalid attribute string”. * In this case the problem was due to the fact that the driver could not parse the NULL-separated connection string. * When used after a call to SQLTables(), SQLRowCount() did not return the correct value.
2011-08-19 09:59:58 +02:00
PKG_OPTIONS_GROUP.db= iodbc unixodbc
PKG_SUPPORTED_OPTIONS= gui
PKG_SUGGESTED_OPTIONS= iodbc
Update to 3.51.12 (latest stable version). There were zillions of changes... please see the Changelog file. Now it builds with both mysql-4.1.x and mysql-5.1.x. pkgsrc changes: Supported build options: * myodbc-gui: builds the QT widgets library. (disabled) * myodbc-iodbc: uses iodbc for the odbc functions. (enabled) * myodbc-unixodbc: uses unixodbc for the odbc functions. (disabled) Uses MASTER_SITE_MYSQL.
2006-01-23 19:53:45 +01:00
.include "../../mk/bsd.options.mk"
Convert to use PLIST_VARS instead of manually passing "@comment " through PLIST_SUBST to the plist module.
2008-04-13 00:42:57 +02:00
PLIST_VARS+= gui
Changes 5.1.8: * Documentation in .CHM and .HLP format has been removed from the distribution. * For some procedure and parameter combinations SQLProcedureColumns() did not work correctly. For example, it could not return records for an existing procedure with correct parameters supplied. * Further, it returned incorrect data for column 7, TYPE_NAME. For example, it returned VARCHAR(20) instead of VARCHAR. * The MySQL Connector/ODBC MSI installer did not set the InstallLocation value in the Microsoft Windows registry. * In bulk upload mode, SQLExecute would return SQL_SUCCESS, even when the uploaded data contained errors, such as primary key duplication, and foreign key violation. * SQLDescribeCol and SQLColAttribute could not be called before SQLExecute, if the query was parameterized and not all parameters were bound. * Note, MSDN states that “For performance reasons, an application should not call SQLColAttribute/SQLDescribeCol before executing a statement.” However, it should still be possible to do so if performance reasons are not paramount. * When SQLNumResultCols() was called between SQLPrepare() and SQLExecute() the driver ran SET @@sql_select_limit=1, which limited the resultset to just one row. * After installing MySQL Connector/ODBC, the system DSN created could not be configured or deleted. An error dialog was displayed, showing the error message “Invalid attribute string”. * In this case the problem was due to the fact that the driver could not parse the NULL-separated connection string. * When used after a call to SQLTables(), SQLRowCount() did not return the correct value.
2011-08-19 09:59:58 +02:00
.if !empty(PKG_OPTIONS:Mgui)
Update to 3.51.12 (latest stable version). There were zillions of changes... please see the Changelog file. Now it builds with both mysql-4.1.x and mysql-5.1.x. pkgsrc changes: Supported build options: * myodbc-gui: builds the QT widgets library. (disabled) * myodbc-iodbc: uses iodbc for the odbc functions. (enabled) * myodbc-unixodbc: uses unixodbc for the odbc functions. (disabled) Uses MASTER_SITE_MYSQL.
2006-01-23 19:53:45 +01:00
. include "../../x11/qt3-tools/buildlink3.mk"
CONFIGURE_ARGS+= --enable-gui
Added "c" to USE_LANGUAGES for packages that use GNU configure scripts, since they always need a C compiler, even when the source code is completely in C++. For some other packages, stated in the comment that a C compiler is really not needed.
2006-07-22 06:46:13 +02:00
USE_LANGUAGES= c c++
Convert to use PLIST_VARS instead of manually passing "@comment " through PLIST_SUBST to the plist module.
2008-04-13 00:42:57 +02:00
PLIST.gui= yes
Update to 3.51.12 (latest stable version). There were zillions of changes... please see the Changelog file. Now it builds with both mysql-4.1.x and mysql-5.1.x. pkgsrc changes: Supported build options: * myodbc-gui: builds the QT widgets library. (disabled) * myodbc-iodbc: uses iodbc for the odbc functions. (enabled) * myodbc-unixodbc: uses unixodbc for the odbc functions. (disabled) Uses MASTER_SITE_MYSQL.
2006-01-23 19:53:45 +01:00
.else
CONFIGURE_ARGS+= --disable-gui
.endif
Changes 5.1.8: * Documentation in .CHM and .HLP format has been removed from the distribution. * For some procedure and parameter combinations SQLProcedureColumns() did not work correctly. For example, it could not return records for an existing procedure with correct parameters supplied. * Further, it returned incorrect data for column 7, TYPE_NAME. For example, it returned VARCHAR(20) instead of VARCHAR. * The MySQL Connector/ODBC MSI installer did not set the InstallLocation value in the Microsoft Windows registry. * In bulk upload mode, SQLExecute would return SQL_SUCCESS, even when the uploaded data contained errors, such as primary key duplication, and foreign key violation. * SQLDescribeCol and SQLColAttribute could not be called before SQLExecute, if the query was parameterized and not all parameters were bound. * Note, MSDN states that “For performance reasons, an application should not call SQLColAttribute/SQLDescribeCol before executing a statement.” However, it should still be possible to do so if performance reasons are not paramount. * When SQLNumResultCols() was called between SQLPrepare() and SQLExecute() the driver ran SET @@sql_select_limit=1, which limited the resultset to just one row. * After installing MySQL Connector/ODBC, the system DSN created could not be configured or deleted. An error dialog was displayed, showing the error message “Invalid attribute string”. * In this case the problem was due to the fact that the driver could not parse the NULL-separated connection string. * When used after a call to SQLTables(), SQLRowCount() did not return the correct value.
2011-08-19 09:59:58 +02:00
.if !empty(PKG_OPTIONS:Miodbc)
Update to 3.51.12 (latest stable version). There were zillions of changes... please see the Changelog file. Now it builds with both mysql-4.1.x and mysql-5.1.x. pkgsrc changes: Supported build options: * myodbc-gui: builds the QT widgets library. (disabled) * myodbc-iodbc: uses iodbc for the odbc functions. (enabled) * myodbc-unixodbc: uses unixodbc for the odbc functions. (disabled) Uses MASTER_SITE_MYSQL.
2006-01-23 19:53:45 +01:00
. include "../../databases/iodbc/buildlink3.mk"
Fix CONFIGURE option to pick up iODBC driver (default option) correctly. Pointed out by Yasushi Oshima in PR 33147. Bump PKGREVISION.
2007-01-14 13:28:56 +01:00
CONFIGURE_ARGS+= --with-iODBC=${BUILDLINK_PREFIX.iodbc}
Update to 3.51.12 (latest stable version). There were zillions of changes... please see the Changelog file. Now it builds with both mysql-4.1.x and mysql-5.1.x. pkgsrc changes: Supported build options: * myodbc-gui: builds the QT widgets library. (disabled) * myodbc-iodbc: uses iodbc for the odbc functions. (enabled) * myodbc-unixodbc: uses unixodbc for the odbc functions. (disabled) Uses MASTER_SITE_MYSQL.
2006-01-23 19:53:45 +01:00
CONFIGURE_ARGS+= --with-odbc-ini=${PKG_SYSCONFDIR.iodbc}/odbc.ini
.endif
Changes 5.1.8: * Documentation in .CHM and .HLP format has been removed from the distribution. * For some procedure and parameter combinations SQLProcedureColumns() did not work correctly. For example, it could not return records for an existing procedure with correct parameters supplied. * Further, it returned incorrect data for column 7, TYPE_NAME. For example, it returned VARCHAR(20) instead of VARCHAR. * The MySQL Connector/ODBC MSI installer did not set the InstallLocation value in the Microsoft Windows registry. * In bulk upload mode, SQLExecute would return SQL_SUCCESS, even when the uploaded data contained errors, such as primary key duplication, and foreign key violation. * SQLDescribeCol and SQLColAttribute could not be called before SQLExecute, if the query was parameterized and not all parameters were bound. * Note, MSDN states that “For performance reasons, an application should not call SQLColAttribute/SQLDescribeCol before executing a statement.” However, it should still be possible to do so if performance reasons are not paramount. * When SQLNumResultCols() was called between SQLPrepare() and SQLExecute() the driver ran SET @@sql_select_limit=1, which limited the resultset to just one row. * After installing MySQL Connector/ODBC, the system DSN created could not be configured or deleted. An error dialog was displayed, showing the error message “Invalid attribute string”. * In this case the problem was due to the fact that the driver could not parse the NULL-separated connection string. * When used after a call to SQLTables(), SQLRowCount() did not return the correct value.
2011-08-19 09:59:58 +02:00
.if !empty(PKG_OPTIONS:Munixodbc)
Update to 3.51.12 (latest stable version). There were zillions of changes... please see the Changelog file. Now it builds with both mysql-4.1.x and mysql-5.1.x. pkgsrc changes: Supported build options: * myodbc-gui: builds the QT widgets library. (disabled) * myodbc-iodbc: uses iodbc for the odbc functions. (enabled) * myodbc-unixodbc: uses unixodbc for the odbc functions. (disabled) Uses MASTER_SITE_MYSQL.
2006-01-23 19:53:45 +01:00
. include "../../databases/unixodbc/buildlink3.mk"
CONFIGURE_ARGS+= --with-unixODBC=${BUILDLINK_PREFIX.unixodbc}
CONFIGURE_ARGS+= --with-odbc-ini=${PKG_SYSCONFDIR.unixodbc}/odbc.ini
.endif
Reference in a new issue Copy permalink