MySQL Connector/C++ is a fairly new JDBC 4.0 API implementation in C++.
Licensed under GPLv2.
See URL for more information.
MySQL Connector/C++ v1.0.6 will be a dependency for OpenOffice.org.
Therefore my report.
I am going to attach an ebuild for RFC. :)
Created attachment 202393 [details]
... from debian archive.
There will be a bump to revision 768 with test code and icu dependency removed.
Just waiting for the tarball on debian archive.
Created attachment 202580 [details]
Since one cannot add optional cmake flags I have to patch the examples build.
Instead of 06_disable_examples_build.diff I would prefer to add '-DMYSQLCPPCONN_BUILD_EXAMPLES:BOOL=0' to the cmake command.
Created attachment 202582 [details, diff]
Created attachment 202584 [details, diff]
Created attachment 202586 [details, diff]
Created attachment 202587 [details, diff]
Created attachment 207072 [details]
- add openssl dependency
- add debug and gcov USEflag
- upstream cleaned up :)
I wonder about gcov USEflag.
And this piece of '$(use USEflag && echo 1 || echo 0)'.
use_enable and use_with fail. :)
Any better idea?
Created attachment 207074 [details]
added use_cmake helper function.
Created attachment 210731 [details]
- add RESTRICT for debug build
- some minor cosmetics
Created attachment 212445 [details, diff]
Created attachment 212446 [details]
Created attachment 224229 [details]
- useflag [static-libs]
Created attachment 225089 [details]
I had to clean up the libdir stuff more.
Also used the patches straight from Debian, instead of having a duplicate copy.
Are you interested in being a proxy maintainer for this package?
Sure, why not. I test it with openoffice anyway. One question I have, though.
How does portage handle a debug build? My experience is that, although one enables the useflag [debug], portage strips the debug symbols from the resulting binaries and libraries. That should not be, should it?! Hard to debug then... Therefore I use 'RESTRICT="debug? ( strip )"' to have the debug symbols in the binaries and libraries.
USE=debug does not mean debug symbols. It means additional debugging code.
# FEATURES=splitdebug CFLAGS='... -g ...' emerge CAT/PN
will give you the debug data split off from the binaries, per the ELF debuglink spec. Alternatively, if you the monolith binaries with debug:
FEATURES='-splitdebug nostrip -strip' ...
Hanno Meyer-Thurow @16
@Robin & @Francesco
Thanks, I added that to /etc/portage/bashrc successfully.
marked as verified.
Finally got to test this package from portage.
I wonder if you want to apply debians patch 04_libmysqlclient_SONAME.dpatch. That hardwires mysql-5.1 afais. So the ebuild may depend on '=virtual/mysql-5.1' instead. Or do mysql 5.4 and 6.0 have libmysqlclient_r.so.16, too?
Another thing I wonder about is the useflag [static] versus [static-libs].
Looking at my world set it seems that programs use [static] and libraries, which dev-db/mysql-connector-c++ is, use [static-libs]. Whoever introduced the latter one ...
(In reply to comment #20)
> Finally got to test this package from portage.
> I wonder if you want to apply debians patch 04_libmysqlclient_SONAME.dpatch.
> That hardwires mysql-5.1 afais. So the ebuild may depend on
> '=virtual/mysql-5.1' instead. Or do mysql 5.4 and 6.0 have
> libmysqlclient_r.so.16, too?
5.4, 5.5 and 6.0 do have the same SONAME version.
static-libs was added for people that wanted some package to build dynamic binaries but static libs at the same time.