DDBI and MySQL

[Max Samukha]

On Fri, 29 Aug 2008 20:16:22 -0700, "Chris R. Miller"
<lordSaurontheGreat at gmail.com> wrote:

>dsss_objs\D\dbi-mysql-MysqlDatabase.obj(dbi-mysql-MysqlDatabase)
> Error 42: Symbol Undefined _mysql_init at 4
>dsss_objs\D\dbi-mysql-MysqlDatabase.obj(dbi-mysql-MysqlDatabase)
> Error 42: Symbol Undefined _mysql_real_connect at 32
>dsss_objs\D\dbi-mysql-MysqlDatabase.obj(dbi-mysql-MysqlDatabase)
> Error 42: Symbol Undefined _mysql_errno at 4
>dsss_objs\D\dbi-mysql-MysqlDatabase.obj(dbi-mysql-MysqlDatabase)
> Error 42: Symbol Undefined _mysql_error at 4
>dsss_objs\D\dbi-mysql-MysqlDatabase.obj(dbi-mysql-MysqlDatabase)
> Error 42: Symbol Undefined
>_D3dbi5mysql10MysqlError17specificToGeneralFkZE3dbi9
>ErrorCode9ErrorCode
>dsss_objs\D\dbi-mysql-MysqlDatabase.obj(dbi-mysql-MysqlDatabase)
> Error 42: Symbol Undefined _mysql_close at 4
>dsss_objs\D\dbi-mysql-MysqlDatabase.obj(dbi-mysql-MysqlDatabase)
> Error 42: Symbol Undefined _mysql_real_query at 12
>dsss_objs\D\dbi-mysql-MysqlDatabase.obj(dbi-mysql-MysqlDatabase)
> Error 42: Symbol Undefined _mysql_store_result at 4
>dsss_objs\D\dbi-mysql-MysqlDatabase.obj(dbi-mysql-MysqlDatabase)
> Error 42: Symbol Undefined _mysql_insert_id at 4
>dsss_objs\D\dbi-mysql-MysqlDatabase.obj(dbi-mysql-MysqlDatabase)
> Error 42: Symbol Undefined _mysql_get_client_version at 0
>dsss_objs\D\dbi-mysql-MysqlResult.obj(dbi-mysql-MysqlResult)
> Error 42: Symbol Undefined _mysql_fetch_row at 4
>dsss_objs\D\dbi-mysql-MysqlResult.obj(dbi-mysql-MysqlResult)
> Error 42: Symbol Undefined _mysql_fetch_lengths at 4
>dsss_objs\D\dbi-mysql-MysqlResult.obj(dbi-mysql-MysqlResult)
> Error 42: Symbol Undefined _mysql_free_result at 4
>dsss_objs\D\dbi-mysql-MysqlResult.obj(dbi-mysql-MysqlResult)
> Error 42: Symbol Undefined _mysql_num_fields at 4
>dsss_objs\D\dbi-mysql-MysqlResult.obj(dbi-mysql-MysqlResult)
> Error 42: Symbol Undefined _mysql_fetch_fields at 4
>
All those symbols are exported by the lib I supplied. I guess you are
still trying to link against a wrong lib. Check your lib paths.


>I'm not an expert at all, but I think that's because it can't discover
>the functions to link against.  If I change it back to extern(C) I get this:
>

Even if you manage to link using extern(C), your program won't work
correctly, because C and Windows calling conventions differ not only
in name decorations. So you must use either extern(Windows) or
extern(System).