Matjaž Cof wrote:
> 
> Thank's to all.
> Stupid me. But still not working. Is there any documentation how to
compile
> SQLite.NET.2010 solution with  SQLITE_DEFAULT_FOREIGN_KEYS=1.
>

This would require modifying the Visual Studio properties file for the
correct version of
Visual Studio (2010 in your case?) and then recompiling the SQLite.Interop
project.

The Visual Studio properties files are located in the source tree at the
following location:

        
http://system.data.sqlite.org/index.html/dir?name=SQLite.Interop/props

The above location corresponds to the "SQLite.Interop\props" directory
inside the root
of the local source tree.  The file that you'll need to modify is either the
"SQLite.Interop\props\sqlite3.vsprops" file (for Visual Studio 2005 or 2008)
or the
"SQLite.Interop\props\sqlite3.props" file (for Visual Studio 2010).

Either way, the SQLITE_COMMON_DEFINES macro should be modified to add the
extra preprocessor defines that you require.

>
> I think, that the problem is, that i am using
> precompiled SQLite.Interop.dll (which is compiled without
> SQLITE_DEFAULT_FOREIGN_KEYS=1 - i think - downloaded from
>
http://system.data.sqlite.org/downloads/1.0.80.0/sqlite-netFx40-binary-Win32
-2010-1.0.80.0.zip
> ).
>

Yes, that could be the problem.  The precompiled binary does not have that
preprocessor
define enabled.

> 
> Is there any documentation, how is SQLite.Interop.2010 project integraded
> into  System.Data.SQLite.2010 project?
> 

Please refer to the following web pages for details on how the
System.Data.SQLite build process
works:

        http://system.data.sqlite.org/index.html/doc/trunk/www/build.wiki

        http://system.data.sqlite.org/index.html/doc/trunk/www/faq.wiki

Other than that, having a good understanding of Visual Studio, interop with
native code, and
multi-language solutions is also very useful.

--
Joe Mistachkin

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

Reply via email to