On Monday, 20 February, 2017 03:58, Cezary H. Noweta <c...@poczta.onet.pl> said:
> On 2017-02-19 22:25, Keith Medcalf wrote: > > Can you tell us how you do it with the amalgamation using MSVS? > ``autoconf'' (containing the same amalgamated ``sqlite3.c'') has the > following options for that task: > > -Gz -DSQLITE_CDECL=__cdecl -DSQLITE_APICALL=__stdcall > -DSQLITE_CALLBACK=__stdcall -DSQLITE_SYSAPI=__stdcall Yes, and I see the defines for those in the sqlite3.c file, but they are not used anywhere ... That is, I would have expected to see: SQLITE_API void SQLITE_APICALL sqlite3_.....() in all the function definitions. But I don't. Is there some "special" building of the amalgamation required for these macro's to appear in the function definitions? rather than use symbol=__stdcall, try using symbol=__attribute__((stdcall)) just as you define SQLITE_API=__declspec(dllexport) to have the APIs exported automatically with no need for a .def file (in fact, the compiler will generate one for you). Note that __declspec(dllexport) is an alias for __attribute__((dllexport)) See https://gcc.gnu.org/onlinedocs/gcc-4.7.2/gcc/Function-Attributes.html _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
