<firstname.lastname@example.org> wrote in message
email@example.com > sed in <at888p$fuu$> firstname.lastname@example.org> >:
I understand that this would make the mysql server run, but what does
a developer do when he creates a program that links the
MySQL client library? The goal here is that if somebody has installed
MySQL package then a developer’s attempts to compile, link and run
will succeed. I was hoping there was a way to add the various MySQL
bits (/usr/include/mysql, /usr/lib/mysql) to the default paths. When I
It’s that developer’s job to add LD_RUN_PATH=/usr/lib/mysql
during the build, not MySQL vendor’s.
So you don’t have to and shouldn’t muck with “default search paths”.
I was talking about default search paths for .so, .a and .h files, without
which a user of the MySQL libraries will have to explicitly code the
locations of .so, .a and .h files into his makefiles. I don’t understand
comment about the MySQL vendor.
For QNX, it doesn’t hurt much to dump them into standard /usr/lib because
the actual image will be /pkgs/repository/public/mysql/*/opt/lib whatever
and uninstall is cheesy and “real” /usr/lib isn’t polluted at all.
MySQL is not careful about naming its libraries and headers because
it believes it will be living in its own subdirectories. There is a (small)
opportunity for library and header name collisions.
I agree that it should be possible to put MySQL’s headers and libs in
‘expected’ places. Perhaps that’s what I’ll do, and let the user
beware if they get superceded. Bleh.