dengxy wrote:
> emit an error for an unresolve external symbol named:
>
> mysql_more_results@4
> mysql_next_result@4
>
> when building examples. However, libmysqlclient.def contains:
>
> ...
> mysql_more_results
> mysql_next_result
> ...
>
> After changes these 2 lines to the version above(append "@4"), the examples can be
> built successfully. Is this strange? Since
> the original one can use with MySQL 4.1, or the .def file need
> patched against MySQL 5.0?
The lines without @X (where X is some number) are all technically
mistakes. We add the proper @X value whenever we need it. You are
simply discovering a new case where another @X is needed.
You may want to join with "Death Gauge" in his thread to get MySQL++
working with MinGW. He is already working on this sort of problem.