Sylvain Pointeau wrote: > Hi again, > > as far as I know you cannot compile SQLite for C++/CLI directly, and I > recently have some problem using C++/CLI in my Qt project.
In C++/CLI one can have both .Net classes and standard C++ classes, since C++/CLI classes have a different syntax than standard C++ classes. I can compile code which uses the sqlite C++ classes as defined in the sqlite3.h header file. The linker warning I am getting is because the sqlite3 and sqlite3_stmt structs are incomplete in C++ in the sqlite3.h header files. Since code involving these structs only uses them through a pointer, they normally do not need to be complete to work properly. But I am worried about the linker warnings, and thought I would ask here to determine whether ot not they are benign or not. > > What I did was to let my application in C++ then compile some part in > C++/CLI, there is some way to mix the managed and unmanaged code. I do not understand what you are saying above. > I think > you want to do the opposite then you have to create the managed bridge to > the unmanaged code. I suggest you to create a separate dll for that. This does not make sense. My C++/CLI code which uses sqlite is purely standard C++ classes, not C++/CLI .Net classes. > > in my opinion the best would be to use > System.Data.SQLite<http://sqlite.phxsoftware.com/>. > I used it already and it works very well. I will look at it. > > Best regards, > Sylvain > > On Thu, Jan 28, 2010 at 9:46 AM, Sylvain Pointeau < > sylvain.point...@gmail.com> wrote: > >> Hi, >> >> you can look at System.Data.SQLite <http://sqlite.phxsoftware.com/> and >> look at the sources. >> >> Best regards, >> Sylvain >> >> >> On Thu, Jan 28, 2010 at 12:23 AM, Edward Diener < >> eldlistmaili...@tropicsoft.com> wrote: >> >>> I am able to compile a C++/CLI .Net application using sqlite. But when >>> it links it complains with some linker warnings: >>> >>> xxx.obj : warning LNK4248: unresolved typeref token (0100001D) for >>> 'sqlite3'; image may not run >>> xxx.obj : warning LNK4248: unresolved typeref token (0100001F) for >>> 'sqlite3_stmt'; image may not run >>> >>> This is because the 'sqlite3' and 'sqlite3_stmt' structures are >>> completely opaque in the sqlite3.h header files, and the MSIL is >>> evidently trying to create code for it. >>> >>> Is there a workaround for this possible problem ? >>> >>> _______________________________________________ >>> sqlite-users mailing list >>> sqlite-users@sqlite.org >>> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users >>> >> > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users