> >> As for the remaining .a libraries in your list (libheap.a, >> libmyisam.a, >> etc.). Does the customer really need these? I thought all client >> development could be performed with just libmysqlclient? These >> look like >> libraries only needed during linking of the server binary. >> >> > 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 ...
If you are only building clients then technically you only need libmysqlclient, but if you are developing a C app that accesses the structures and information in the response from mysqlclient you may need the other (libmystrings particularly). If you want to develop or add a storage engine to existing setup, then you need all the other libraries *except* libmysqlclient. MC -- Martin 'MC' Brown, mc at mcslp.com Everything MCslp: http://planet.mcslp.com
