I tried the first option you suggested , i get the following error log :

------ Build started: Project: Source Tagging System, Configuration: Debug
Win32 ------

Compiling...
sqlite3.c
c:\Documents and Settings\Administrator\My Documents\Visual Studio
Projects\Source Tagging System\sqlite-amalgamation\sqlite3.c(22) : fatal
error C1853: 'Debug/Source Tagging System.pch' precompiled header file is
from a previous version of the compiler, or the precompiled header is C++
and you are using it from C (or vice versa)

Build log was saved at "file://c:\Documents and Settings\Administrator\My
Documents\Visual Studio Projects\Source Tagging System\Debug\BuildLog.htm"
Source Tagging System - 1 error(s), 0 warning(s)


---------------------- Done ----------------------

    Build: 0 succeeded, 1 failed, 0 skipped


On Tue, Sep 30, 2008 at 5:15 AM, Eric Minbiole
<[EMAIL PROTECTED]>wrote:

> > Hi,
> > I am getting the following error log when i try to build sqlite source :
> >  ...
> > c:\Documents and Settings\Administrator\My Documents\Visual Studio
> > Projects\Source Tagging System\sqlite\where.c(2902): fatal error C1010:
> > unexpected end of file while looking for precompiled header directive
>
> By default, Visual Studio projects use "precompiled headers", which can
> greatly speed up compilation times.  To use this feature, you must
> include the special file, "stdafx.h", at the top of each source file.
>
> To correct this error, you can either #include "stdafx.h", or disable
> precompiled headers for sqlite project file(s).  The latter setting can
> be found in the "precompiled headers" section of the project properties.
>  Do a search on "C1010" for more info.
>
> ~Eric
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
Ciao,
Ajinkya
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to