> 1>LINK : fatal error LNK1181: cannot open input file > '..\release\sqlite.lib'
Is this filename something that you wrote yourself in configuration of your project? If you compile something as dll you don't need to mention its library as additional linking source in dependent projects. Pavel On Thu, Dec 17, 2009 at 9:01 AM, Kurt D. Knudsen <kknud...@zystemsgo.com> wrote: > Hi all, > > > > Since we're moving our project over from flat-files to an SQL DB, I've > noticed that projects that utilize SQLite3 have increased to over 500k > in size. Their original sizes were between 50-100k. Also, the build > times have increased dramatically. I have SQLite added as a separate > project in my solution (Visual Studio 2008) and have its Configuration > Type as .lib. If I set it to .dll, then the rest of the projects fail to > link properly stating: > > > > 1>LINK : fatal error LNK1181: cannot open input file > '..\release\sqlite.lib' > > > > I'm curious to know if this is normal behavior and if SQLite must be > compiled as a .lib as opposed to a .dll? The odd thing is, I have other > projects in the solution that are set to compile as a .dll and they link > fine with each other. > > > > Relevant information: > > > > Visual Studio 2008 Professional > > Compiling as Release > > > > Let me know if you need more information. > > > > Thanks, > > > > Kurt > > _______________________________________________ > 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
