Jyri Virkki wrote: > Ritu Kamboj wrote: > >> the dynamic client libraries are available for 5.0 as well...in a >> typical MySQL release area you will find both the static and dynamic >> version of client library and that was our initial plan as >> well....however, we can just ship the dynamic version of client >> libraries and take out the static library. >> > > Sounds like a good plan, if the shared libs are available do ship > those instead. >
I'd be a bit concerned about this, as I recall PHP mysql modules use the static client libraries when it builds by default. A quick search or two seems to confirm this. I wish it weren't the case, but there are probably other 'downstream' pieces of Open Source, and potential end user apps, that expect to link in the .a files. Given that the upstream build scripts leave them there by default, what do we gain by removing them? I assume the answer is discourage such linking, but it also will mean more complex porting/building for apps (both end user and other Open Source) that expect them. > >> The following static libraries exist in typical MySQL install area: >> libdbug.a, libmysys.a , libmystrings.a , libz.a. (in addition to >> client static library). >> I am working with MySQL to get a definitive answer about their use case ... >> > > Ok let us know.. > -- Matt Ingenthron - Web Infrastructure Solutions Architect Sun Microsystems, Inc. - Global Systems Practice http://blogs.sun.com/mingenthron/ email: matt.ingenthron at sun.com Phone: 310-242-6439
