Re: [sqlite] Compiling SQLite Encryption Extension for ARM processor

[Jens Alfke]

> On Feb 13, 2020, at 10:51 AM, Subodh Pathak  wrote:
> 
> I am looking for help to configure machine to compile SEE for ARM. I am
> using Android mobile Samsung G7.

You have to use a cross-compiler, a version of GCC that runs on your platform 
but generates ARM-Linux code. 
Specifically, to build for Android you should be using the Android Native 
Development Kit (NDK). The page Dr. Hipp linked to will show you how to do that.

—Jens
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling SQLite Encryption Extension for ARM processor

[Richard Hipp]

On 2/13/20, Subodh Pathak  wrote:
>
> I am trying to compile SEE for ARM processor.

There is a website explain how to compile SQLite for Android here:
https://www.sqlite.org/android/doc/trunk/www/index.wiki

Please review the instructions on that website and write again if they
do not work for you.

D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Compiling SQLite Encryption Extension for ARM processor

[Subodh Pathak]

Team,

I am trying to compile SEE for ARM processor.
I have followed following steps. But was not successful in generating "
*libsqliteX.so*" file which can be used on Android Samsung G7 mobile.

1.  Installed GCC compiler from “http://www.mingw.org/” reference at “
https://gcc.gnu.org/”.

2.  Installed required library specially related to lpthread.

3.  Downloaded another library “libdl.a” from “
https://github.com/dlfcn-win32/dlfcn-win32” to compile using -ldl command.
MinGW-W32 and MinGW-W64 only have dlfcn to provide libdl, but that's not a
regularly installed package. After extracting package. Copied “libdl.a” to
“C:\MinGW\lib”

* gcc -c -fPIC sqlite3.c see-aes256-ofb.c*

* gcc -shared -o libsqliteX.so -fPIC sqlite3.o see-aes256-ofb.c
-ldl –lpthread*

4.  Above mentioned command does generate "libsqliteX.so" file but not
compatible to use on Android Samsugn G7.



References:

https://gitlab.kitware.com/cmake/cmake/merge_requests/1642

https://gcc.gnu.org/install/binaries.html

https://gcc.gnu.org/

https://sqlite.org/android/doc/trunk/www/index.wiki

https://www.sqlite.org/see/doc/release/www/index.wiki

https://www.hwaci.com/sw/sqlite/see.html

https://sqlite.org/src/doc/trunk/README.md




I have also tried to do below configuration before compile but no lock.

./configure --build=x86_64-unknown-linux-gnu --host=arm-linux
--target=arm-linux
I am looking for help to configure machine to compile SEE for ARM. I am
using Android mobile Samsung G7.
Any help is much appreciated.

Regards,
Subodh
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Compiling SQLite without the database storage?

[Jens Alfke]

This may sound crazy, but is there a way to compile SQLite without its B-tree 
and table code? This would be for a use case with _only_ virtual tables — i.e. 
SQLite being used as a SQL query engine on top of a different data store*. It 
would be nice not to drag in too much unused code.

—Jens

* Yes, I happen to be experimenting with LMDB...
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Compiling SQLite dll 64 bits in MSVS

[Bart Smissaert]

> About name decoration please see
https://msdn.microsoft.com/en-us/library/56h2zst2.aspx

Thanks, that was helpful.

In the above it says: Note that in a 64-bit environment, functions are not
decorated.

Not sure what that exactly means as I know that in VBA 64 bits decorated
names are used in declarations
to access functions in a 64 bit dll. I will try the /FAs option to have a
look and see if there are decorated names.


RBS

On Wed, Apr 6, 2016 at 7:06 AM, GB  wrote:

> The top right pane shows which entry points are actually imported by the
> importing module. Since the top level module is not imported by anything
> the "imports" Pane is empty.
>
> About name decoration please see
> https://msdn.microsoft.com/en-us/library/56h2zst2.aspx
>
> Bart Smissaert schrieb am 05.04.2016 um 23:42:
>
>> I said that wrong, even in the old 32 bits Dependency Walker there is nil
>> in the top right pane.
>> Still, there are no decorated function names in the 64 bit dll to see.
>> Is this normal or do I have to alter my command line parameters?
>>
>> RBS
>>
>> On Tue, Apr 5, 2016 at 10:23 PM, Bart Smissaert > >
>> wrote:
>>
>>
>>
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

[sqlite] Compiling SQLite dll 64 bits in MSVS

[GB]

The top right pane shows which entry points are actually imported by the 
importing module. Since the top level module is not imported by anything 
the "imports" Pane is empty.

About name decoration please see 
https://msdn.microsoft.com/en-us/library/56h2zst2.aspx

Bart Smissaert schrieb am 05.04.2016 um 23:42:
> I said that wrong, even in the old 32 bits Dependency Walker there is nil
> in the top right pane.
> Still, there are no decorated function names in the 64 bit dll to see.
> Is this normal or do I have to alter my command line parameters?
>
> RBS
>
> On Tue, Apr 5, 2016 at 10:23 PM, Bart Smissaert 
> wrote:
>
>

[sqlite] Compiling SQLite dll 64 bits in MSVS

[Bart Smissaert]

Haven't I got that here:

> Additional Options:
>
> sqlite3.c /Gz -DSQLITE_API=__declspec(dllexport)

Or should I leave the D off before SQLITE_API   ?


RBS

On Tue, Apr 5, 2016 at 11:04 PM, J Decker  wrote:

> On Tue, Apr 5, 2016 at 2:09 PM, Bart Smissaert 
> wrote:
> > I am not using .def files, but use commandline settings from VS:
> >
> > All options:
> >
> > /GS /TC /W3 /Zc:wchar_t /Zi /Gm- /O2 /Fd"x64\Release\vc120.pdb"
> /fp:precise
> > /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_USRDLL" /D
> > "SQLITE3_STDCALL_EXPORTS" /D "_WINDLL" /errorReport:prompt /WX-
> > /Zc:forScope /Gz /MD /Fa"x64\Release\" /EHsc /nologo /Fo"x64\Release\"
> > /Fp"x64\Release\SQLite3_StdCall.pch"
> >
> > Additional Options:
> >
> > sqlite3.c /Gz -DSQLITE_API=__declspec(dllexport) -O2
> > -DSQLITE_ENABLE_COLUMN_METADATA=1 -DSQLITE_SYSTEM_MALLOC=1
> > -DSQLITE_THREADSAFE=0 -DSQLITE_ENABLE_EXPLAIN_COMMENTS=1
> > -DSQLITE_SQLITE_ENABLE_RTREE=1-DSQLITE_ENABLE_FTS4=1 -link -dll
> > -out:SQLite3_StdCall.dll
> >
> >
>
> add
>
> SQLITE_API=__declspec(dllexport)
>
> from like line 12...
>
>
> http://pavel.cernohorsky.name/blog/2015/09/sqlite_64-bit_binaries_for_windows_and_how_to_build_them_with_visual_studio_2015.php
>
> You missed the important part :)
>
> > RBS
> >
> > On Tue, Apr 5, 2016 at 10:05 PM, J Decker  wrote:
> >
> >> def files are obsolete.
> >> the instructions include setting SQLITE_API to __declspec(dllexport)
> >> which should do the job... unless there was a typeo
> >>
> >> On Tue, Apr 5, 2016 at 2:03 PM, GB  wrote:
> >> > Strange. Runs fine here (also Win 7 Pro x64). But version 2.1 may have
> >> > problems with post-XP OS. Try V2.2 from here:
> >> > http://www.heise.de/download/dependency-walker.html (German site, but
> >> > downloads should be easy to spot).
> >> >
> >> > But if I remember this right, you need to include the sqlite3.def file
> >> from
> >> > the binary dll-package into your project to create the exports.
> >> Depending on
> >> > your build flags you may need to comment out some exports.
> >> >
> >> >
> >> >
> >> > Bart Smissaert schrieb am 05.04.2016 um 22:01:
> >> >>
> >> >> I downloaded the 64 bit version of DependencyWalker from here:
> >> >> https://support.microsoft.com/en-us/kb/256872
> >> >> but it didn't run on my machine although it is Win 7 Pro 64 bits.
> >> >> Will have a look on the MSVS 2013 installation disc.
> >> >>
> >> >> RBS
> >> >>
> >> >>
> >> >>
> >> >> On Tue, Apr 5, 2016 at 8:17 PM, GB  wrote:
> >> >>
> >> >>> Dependency Walker comes in two different flavors, one for x86 and
> one
> >> for
> >> >>> x64. You need to use the appropriate one for your DLL.
> >> >>>
> >> >>>
> >> >>>
> >> >>> Bart Smissaert schrieb am 05.04.2016 um 09:50:
> >> >>>
> >>  Trying to compile SQLite 64 bits in MSVS 2013 from the amalgation.
> >>  Using instructions from:
> >> 
> >> 
> >> 
> >> 
> >>
> http://pavel.cernohorsky.name/blog/2015/09/sqlite_64-bit_binaries_for_windows_and_how_to_build_them_with_visual_studio_2015.php
> >> 
> >>  All compiles well, so no warnings and get a dll of about 700 kB.
> >>  Nil shows however in Dependency Walker, so it looks nil is
> exported.
> >> 
> >>  Do I need to change anything in the amalgation source to compile 64
> >> bits
> >>  or
> >>  could it be that Dependency Walker doesn't work well with 64 bit
> >> dll's?
> >>  The machine is Win 7 64 bits.
> >>  I have problem at all compiling 32 bits.
> >>  Thanks for any advice.
> >> 
> >>  RBS
> >>  ___
> >>  sqlite-users mailing list
> >>  sqlite-users at mailinglists.sqlite.org
> >> 
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> >> 
> >> 
> >> >>> ___
> >> >>> sqlite-users mailing list
> >> >>> sqlite-users at mailinglists.sqlite.org
> >> >>>
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> >> >>>
> >> >> ___
> >> >> sqlite-users mailing list
> >> >> sqlite-users at mailinglists.sqlite.org
> >> >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> >> >>
> >> >
> >> > ___
> >> > sqlite-users mailing list
> >> > sqlite-users at mailinglists.sqlite.org
> >> > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> >> ___
> >> sqlite-users mailing list
> >> sqlite-users at mailinglists.sqlite.org
> >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> >>
> > ___
> > sqlite-users mailing list
> > sqlite-users at mailinglists.sqlite.org
> > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> 

[sqlite] Compiling SQLite dll 64 bits in MSVS

[GB]

Well, last time I built sqlite3.dll myself was some years ago... I don't 
remember why we used the .def

J Decker schrieb am 05.04.2016 um 23:05:
> def files are obsolete.
> the instructions include setting SQLITE_API to __declspec(dllexport)
> which should do the job... unless there was a typeo
>
>

[sqlite] Compiling SQLite dll 64 bits in MSVS

[GB]

Strange. Runs fine here (also Win 7 Pro x64). But version 2.1 may have 
problems with post-XP OS. Try V2.2 from here: 
http://www.heise.de/download/dependency-walker.html (German site, but 
downloads should be easy to spot).

But if I remember this right, you need to include the sqlite3.def file 
from the binary dll-package into your project to create the exports. 
Depending on your build flags you may need to comment out some exports.


Bart Smissaert schrieb am 05.04.2016 um 22:01:
> I downloaded the 64 bit version of DependencyWalker from here:
> https://support.microsoft.com/en-us/kb/256872
> but it didn't run on my machine although it is Win 7 Pro 64 bits.
> Will have a look on the MSVS 2013 installation disc.
>
> RBS
>
>
>
> On Tue, Apr 5, 2016 at 8:17 PM, GB  wrote:
>
>> Dependency Walker comes in two different flavors, one for x86 and one for
>> x64. You need to use the appropriate one for your DLL.
>>
>>
>>
>> Bart Smissaert schrieb am 05.04.2016 um 09:50:
>>
>>> Trying to compile SQLite 64 bits in MSVS 2013 from the amalgation.
>>> Using instructions from:
>>>
>>>
>>> http://pavel.cernohorsky.name/blog/2015/09/sqlite_64-bit_binaries_for_windows_and_how_to_build_them_with_visual_studio_2015.php
>>>
>>> All compiles well, so no warnings and get a dll of about 700 kB.
>>> Nil shows however in Dependency Walker, so it looks nil is exported.
>>>
>>> Do I need to change anything in the amalgation source to compile 64 bits
>>> or
>>> could it be that Dependency Walker doesn't work well with 64 bit dll's?
>>> The machine is Win 7 64 bits.
>>> I have problem at all compiling 32 bits.
>>> Thanks for any advice.
>>>
>>> RBS
>>> ___
>>> sqlite-users mailing list
>>> sqlite-users at mailinglists.sqlite.org
>>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>>>
>>>
>> ___
>> sqlite-users mailing list
>> sqlite-users at mailinglists.sqlite.org
>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>>
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

[sqlite] Compiling SQLite dll 64 bits in MSVS

[Bart Smissaert]

I said that wrong, even in the old 32 bits Dependency Walker there is nil
in the top right pane.
Still, there are no decorated function names in the 64 bit dll to see.
Is this normal or do I have to alter my command line parameters?

RBS

On Tue, Apr 5, 2016 at 10:23 PM, Bart Smissaert 
wrote:

> Thanks, that V2.2 works.
> What is strange though is that I see nil in the top right pane, so
> decorated function names.
> Is this different in the 64 bits dll?
>
> RBS
>
>
> On Tue, Apr 5, 2016 at 10:03 PM, GB  wrote:
>
>> Strange. Runs fine here (also Win 7 Pro x64). But version 2.1 may have
>> problems with post-XP OS. Try V2.2 from here:
>> http://www.heise.de/download/dependency-walker.html (German site, but
>> downloads should be easy to spot).
>>
>> But if I remember this right, you need to include the sqlite3.def file
>> from the binary dll-package into your project to create the exports.
>> Depending on your build flags you may need to comment out some exports.
>>
>>
>>
>> Bart Smissaert schrieb am 05.04.2016 um 22:01:
>>
>>> I downloaded the 64 bit version of DependencyWalker from here:
>>> https://support.microsoft.com/en-us/kb/256872
>>> but it didn't run on my machine although it is Win 7 Pro 64 bits.
>>> Will have a look on the MSVS 2013 installation disc.
>>>
>>> RBS
>>>
>>>
>>>
>>> On Tue, Apr 5, 2016 at 8:17 PM, GB  wrote:
>>>
>>> Dependency Walker comes in two different flavors, one for x86 and one for
 x64. You need to use the appropriate one for your DLL.



 Bart Smissaert schrieb am 05.04.2016 um 09:50:

 Trying to compile SQLite 64 bits in MSVS 2013 from the amalgation.
> Using instructions from:
>
>
>
> http://pavel.cernohorsky.name/blog/2015/09/sqlite_64-bit_binaries_for_windows_and_how_to_build_them_with_visual_studio_2015.php
>
> All compiles well, so no warnings and get a dll of about 700 kB.
> Nil shows however in Dependency Walker, so it looks nil is exported.
>
> Do I need to change anything in the amalgation source to compile 64
> bits
> or
> could it be that Dependency Walker doesn't work well with 64 bit dll's?
> The machine is Win 7 64 bits.
> I have problem at all compiling 32 bits.
> Thanks for any advice.
>
> RBS
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
>
> ___
 sqlite-users mailing list
 sqlite-users at mailinglists.sqlite.org
 http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

 ___
>>> sqlite-users mailing list
>>> sqlite-users at mailinglists.sqlite.org
>>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>>>
>>>
>> ___
>> sqlite-users mailing list
>> sqlite-users at mailinglists.sqlite.org
>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>>
>
>

[sqlite] Compiling SQLite dll 64 bits in MSVS

[Bart Smissaert]

Thanks, that V2.2 works.
What is strange though is that I see nil in the top right pane, so
decorated function names.
Is this different in the 64 bits dll?

RBS


On Tue, Apr 5, 2016 at 10:03 PM, GB  wrote:

> Strange. Runs fine here (also Win 7 Pro x64). But version 2.1 may have
> problems with post-XP OS. Try V2.2 from here:
> http://www.heise.de/download/dependency-walker.html (German site, but
> downloads should be easy to spot).
>
> But if I remember this right, you need to include the sqlite3.def file
> from the binary dll-package into your project to create the exports.
> Depending on your build flags you may need to comment out some exports.
>
>
>
> Bart Smissaert schrieb am 05.04.2016 um 22:01:
>
>> I downloaded the 64 bit version of DependencyWalker from here:
>> https://support.microsoft.com/en-us/kb/256872
>> but it didn't run on my machine although it is Win 7 Pro 64 bits.
>> Will have a look on the MSVS 2013 installation disc.
>>
>> RBS
>>
>>
>>
>> On Tue, Apr 5, 2016 at 8:17 PM, GB  wrote:
>>
>> Dependency Walker comes in two different flavors, one for x86 and one for
>>> x64. You need to use the appropriate one for your DLL.
>>>
>>>
>>>
>>> Bart Smissaert schrieb am 05.04.2016 um 09:50:
>>>
>>> Trying to compile SQLite 64 bits in MSVS 2013 from the amalgation.
 Using instructions from:



 http://pavel.cernohorsky.name/blog/2015/09/sqlite_64-bit_binaries_for_windows_and_how_to_build_them_with_visual_studio_2015.php

 All compiles well, so no warnings and get a dll of about 700 kB.
 Nil shows however in Dependency Walker, so it looks nil is exported.

 Do I need to change anything in the amalgation source to compile 64 bits
 or
 could it be that Dependency Walker doesn't work well with 64 bit dll's?
 The machine is Win 7 64 bits.
 I have problem at all compiling 32 bits.
 Thanks for any advice.

 RBS
 ___
 sqlite-users mailing list
 sqlite-users at mailinglists.sqlite.org
 http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


 ___
>>> sqlite-users mailing list
>>> sqlite-users at mailinglists.sqlite.org
>>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>>>
>>> ___
>> sqlite-users mailing list
>> sqlite-users at mailinglists.sqlite.org
>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>>
>>
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

[sqlite] Compiling SQLite dll 64 bits in MSVS

[Bart Smissaert]

I am not using .def files, but use commandline settings from VS:

All options:

/GS /TC /W3 /Zc:wchar_t /Zi /Gm- /O2 /Fd"x64\Release\vc120.pdb" /fp:precise
/D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_USRDLL" /D
"SQLITE3_STDCALL_EXPORTS" /D "_WINDLL" /errorReport:prompt /WX-
/Zc:forScope /Gz /MD /Fa"x64\Release\" /EHsc /nologo /Fo"x64\Release\"
/Fp"x64\Release\SQLite3_StdCall.pch"

Additional Options:

sqlite3.c /Gz -DSQLITE_API=__declspec(dllexport) -O2
-DSQLITE_ENABLE_COLUMN_METADATA=1 -DSQLITE_SYSTEM_MALLOC=1
-DSQLITE_THREADSAFE=0 -DSQLITE_ENABLE_EXPLAIN_COMMENTS=1
-DSQLITE_SQLITE_ENABLE_RTREE=1-DSQLITE_ENABLE_FTS4=1 -link -dll
-out:SQLite3_StdCall.dll


RBS

On Tue, Apr 5, 2016 at 10:05 PM, J Decker  wrote:

> def files are obsolete.
> the instructions include setting SQLITE_API to __declspec(dllexport)
> which should do the job... unless there was a typeo
>
> On Tue, Apr 5, 2016 at 2:03 PM, GB  wrote:
> > Strange. Runs fine here (also Win 7 Pro x64). But version 2.1 may have
> > problems with post-XP OS. Try V2.2 from here:
> > http://www.heise.de/download/dependency-walker.html (German site, but
> > downloads should be easy to spot).
> >
> > But if I remember this right, you need to include the sqlite3.def file
> from
> > the binary dll-package into your project to create the exports.
> Depending on
> > your build flags you may need to comment out some exports.
> >
> >
> >
> > Bart Smissaert schrieb am 05.04.2016 um 22:01:
> >>
> >> I downloaded the 64 bit version of DependencyWalker from here:
> >> https://support.microsoft.com/en-us/kb/256872
> >> but it didn't run on my machine although it is Win 7 Pro 64 bits.
> >> Will have a look on the MSVS 2013 installation disc.
> >>
> >> RBS
> >>
> >>
> >>
> >> On Tue, Apr 5, 2016 at 8:17 PM, GB  wrote:
> >>
> >>> Dependency Walker comes in two different flavors, one for x86 and one
> for
> >>> x64. You need to use the appropriate one for your DLL.
> >>>
> >>>
> >>>
> >>> Bart Smissaert schrieb am 05.04.2016 um 09:50:
> >>>
>  Trying to compile SQLite 64 bits in MSVS 2013 from the amalgation.
>  Using instructions from:
> 
> 
> 
> 
> http://pavel.cernohorsky.name/blog/2015/09/sqlite_64-bit_binaries_for_windows_and_how_to_build_them_with_visual_studio_2015.php
> 
>  All compiles well, so no warnings and get a dll of about 700 kB.
>  Nil shows however in Dependency Walker, so it looks nil is exported.
> 
>  Do I need to change anything in the amalgation source to compile 64
> bits
>  or
>  could it be that Dependency Walker doesn't work well with 64 bit
> dll's?
>  The machine is Win 7 64 bits.
>  I have problem at all compiling 32 bits.
>  Thanks for any advice.
> 
>  RBS
>  ___
>  sqlite-users mailing list
>  sqlite-users at mailinglists.sqlite.org
>  http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> 
> 
> >>> ___
> >>> sqlite-users mailing list
> >>> sqlite-users at mailinglists.sqlite.org
> >>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> >>>
> >> ___
> >> sqlite-users mailing list
> >> sqlite-users at mailinglists.sqlite.org
> >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> >>
> >
> > ___
> > sqlite-users mailing list
> > sqlite-users at mailinglists.sqlite.org
> > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

[sqlite] Compiling SQLite dll 64 bits in MSVS

[GB]

Dependency Walker comes in two different flavors, one for x86 and one 
for x64. You need to use the appropriate one for your DLL.


Bart Smissaert schrieb am 05.04.2016 um 09:50:
> Trying to compile SQLite 64 bits in MSVS 2013 from the amalgation.
> Using instructions from:
>
> http://pavel.cernohorsky.name/blog/2015/09/sqlite_64-bit_binaries_for_windows_and_how_to_build_them_with_visual_studio_2015.php
>
> All compiles well, so no warnings and get a dll of about 700 kB.
> Nil shows however in Dependency Walker, so it looks nil is exported.
>
> Do I need to change anything in the amalgation source to compile 64 bits or
> could it be that Dependency Walker doesn't work well with 64 bit dll's?
> The machine is Win 7 64 bits.
> I have problem at all compiling 32 bits.
> Thanks for any advice.
>
> RBS
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

[sqlite] Compiling SQLite dll 64 bits in MSVS

[Bart Smissaert]

I downloaded the 64 bit version of DependencyWalker from here:
https://support.microsoft.com/en-us/kb/256872
but it didn't run on my machine although it is Win 7 Pro 64 bits.
Will have a look on the MSVS 2013 installation disc.

RBS



On Tue, Apr 5, 2016 at 8:17 PM, GB  wrote:

> Dependency Walker comes in two different flavors, one for x86 and one for
> x64. You need to use the appropriate one for your DLL.
>
>
>
> Bart Smissaert schrieb am 05.04.2016 um 09:50:
>
>> Trying to compile SQLite 64 bits in MSVS 2013 from the amalgation.
>> Using instructions from:
>>
>>
>> http://pavel.cernohorsky.name/blog/2015/09/sqlite_64-bit_binaries_for_windows_and_how_to_build_them_with_visual_studio_2015.php
>>
>> All compiles well, so no warnings and get a dll of about 700 kB.
>> Nil shows however in Dependency Walker, so it looks nil is exported.
>>
>> Do I need to change anything in the amalgation source to compile 64 bits
>> or
>> could it be that Dependency Walker doesn't work well with 64 bit dll's?
>> The machine is Win 7 64 bits.
>> I have problem at all compiling 32 bits.
>> Thanks for any advice.
>>
>> RBS
>> ___
>> sqlite-users mailing list
>> sqlite-users at mailinglists.sqlite.org
>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>>
>>
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

[sqlite] Compiling SQLite dll 64 bits in MSVS

[J Decker]

On Tue, Apr 5, 2016 at 2:09 PM, Bart Smissaert  
wrote:
> I am not using .def files, but use commandline settings from VS:
>
> All options:
>
> /GS /TC /W3 /Zc:wchar_t /Zi /Gm- /O2 /Fd"x64\Release\vc120.pdb" /fp:precise
> /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_USRDLL" /D
> "SQLITE3_STDCALL_EXPORTS" /D "_WINDLL" /errorReport:prompt /WX-
> /Zc:forScope /Gz /MD /Fa"x64\Release\" /EHsc /nologo /Fo"x64\Release\"
> /Fp"x64\Release\SQLite3_StdCall.pch"
>
> Additional Options:
>
> sqlite3.c /Gz -DSQLITE_API=__declspec(dllexport) -O2
> -DSQLITE_ENABLE_COLUMN_METADATA=1 -DSQLITE_SYSTEM_MALLOC=1
> -DSQLITE_THREADSAFE=0 -DSQLITE_ENABLE_EXPLAIN_COMMENTS=1
> -DSQLITE_SQLITE_ENABLE_RTREE=1-DSQLITE_ENABLE_FTS4=1 -link -dll
> -out:SQLite3_StdCall.dll
>
>

add

SQLITE_API=__declspec(dllexport)

from like line 12...

http://pavel.cernohorsky.name/blog/2015/09/sqlite_64-bit_binaries_for_windows_and_how_to_build_them_with_visual_studio_2015.php

You missed the important part :)

> RBS
>
> On Tue, Apr 5, 2016 at 10:05 PM, J Decker  wrote:
>
>> def files are obsolete.
>> the instructions include setting SQLITE_API to __declspec(dllexport)
>> which should do the job... unless there was a typeo
>>
>> On Tue, Apr 5, 2016 at 2:03 PM, GB  wrote:
>> > Strange. Runs fine here (also Win 7 Pro x64). But version 2.1 may have
>> > problems with post-XP OS. Try V2.2 from here:
>> > http://www.heise.de/download/dependency-walker.html (German site, but
>> > downloads should be easy to spot).
>> >
>> > But if I remember this right, you need to include the sqlite3.def file
>> from
>> > the binary dll-package into your project to create the exports.
>> Depending on
>> > your build flags you may need to comment out some exports.
>> >
>> >
>> >
>> > Bart Smissaert schrieb am 05.04.2016 um 22:01:
>> >>
>> >> I downloaded the 64 bit version of DependencyWalker from here:
>> >> https://support.microsoft.com/en-us/kb/256872
>> >> but it didn't run on my machine although it is Win 7 Pro 64 bits.
>> >> Will have a look on the MSVS 2013 installation disc.
>> >>
>> >> RBS
>> >>
>> >>
>> >>
>> >> On Tue, Apr 5, 2016 at 8:17 PM, GB  wrote:
>> >>
>> >>> Dependency Walker comes in two different flavors, one for x86 and one
>> for
>> >>> x64. You need to use the appropriate one for your DLL.
>> >>>
>> >>>
>> >>>
>> >>> Bart Smissaert schrieb am 05.04.2016 um 09:50:
>> >>>
>>  Trying to compile SQLite 64 bits in MSVS 2013 from the amalgation.
>>  Using instructions from:
>> 
>> 
>> 
>> 
>> http://pavel.cernohorsky.name/blog/2015/09/sqlite_64-bit_binaries_for_windows_and_how_to_build_them_with_visual_studio_2015.php
>> 
>>  All compiles well, so no warnings and get a dll of about 700 kB.
>>  Nil shows however in Dependency Walker, so it looks nil is exported.
>> 
>>  Do I need to change anything in the amalgation source to compile 64
>> bits
>>  or
>>  could it be that Dependency Walker doesn't work well with 64 bit
>> dll's?
>>  The machine is Win 7 64 bits.
>>  I have problem at all compiling 32 bits.
>>  Thanks for any advice.
>> 
>>  RBS
>>  ___
>>  sqlite-users mailing list
>>  sqlite-users at mailinglists.sqlite.org
>>  http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>> 
>> 
>> >>> ___
>> >>> sqlite-users mailing list
>> >>> sqlite-users at mailinglists.sqlite.org
>> >>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>> >>>
>> >> ___
>> >> sqlite-users mailing list
>> >> sqlite-users at mailinglists.sqlite.org
>> >> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>> >>
>> >
>> > ___
>> > sqlite-users mailing list
>> > sqlite-users at mailinglists.sqlite.org
>> > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>> ___
>> sqlite-users mailing list
>> sqlite-users at mailinglists.sqlite.org
>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>>
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Compiling SQLite dll 64 bits in MSVS

[J Decker]

def files are obsolete.
the instructions include setting SQLITE_API to __declspec(dllexport)
which should do the job... unless there was a typeo

On Tue, Apr 5, 2016 at 2:03 PM, GB  wrote:
> Strange. Runs fine here (also Win 7 Pro x64). But version 2.1 may have
> problems with post-XP OS. Try V2.2 from here:
> http://www.heise.de/download/dependency-walker.html (German site, but
> downloads should be easy to spot).
>
> But if I remember this right, you need to include the sqlite3.def file from
> the binary dll-package into your project to create the exports. Depending on
> your build flags you may need to comment out some exports.
>
>
>
> Bart Smissaert schrieb am 05.04.2016 um 22:01:
>>
>> I downloaded the 64 bit version of DependencyWalker from here:
>> https://support.microsoft.com/en-us/kb/256872
>> but it didn't run on my machine although it is Win 7 Pro 64 bits.
>> Will have a look on the MSVS 2013 installation disc.
>>
>> RBS
>>
>>
>>
>> On Tue, Apr 5, 2016 at 8:17 PM, GB  wrote:
>>
>>> Dependency Walker comes in two different flavors, one for x86 and one for
>>> x64. You need to use the appropriate one for your DLL.
>>>
>>>
>>>
>>> Bart Smissaert schrieb am 05.04.2016 um 09:50:
>>>
 Trying to compile SQLite 64 bits in MSVS 2013 from the amalgation.
 Using instructions from:



 http://pavel.cernohorsky.name/blog/2015/09/sqlite_64-bit_binaries_for_windows_and_how_to_build_them_with_visual_studio_2015.php

 All compiles well, so no warnings and get a dll of about 700 kB.
 Nil shows however in Dependency Walker, so it looks nil is exported.

 Do I need to change anything in the amalgation source to compile 64 bits
 or
 could it be that Dependency Walker doesn't work well with 64 bit dll's?
 The machine is Win 7 64 bits.
 I have problem at all compiling 32 bits.
 Thanks for any advice.

 RBS
 ___
 sqlite-users mailing list
 sqlite-users at mailinglists.sqlite.org
 http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users


>>> ___
>>> sqlite-users mailing list
>>> sqlite-users at mailinglists.sqlite.org
>>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>>>
>> ___
>> sqlite-users mailing list
>> sqlite-users at mailinglists.sqlite.org
>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>>
>
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Compiling SQLite dll 64 bits in MSVS

[Bart Smissaert]

Trying to compile SQLite 64 bits in MSVS 2013 from the amalgation.
Using instructions from:

http://pavel.cernohorsky.name/blog/2015/09/sqlite_64-bit_binaries_for_windows_and_how_to_build_them_with_visual_studio_2015.php

All compiles well, so no warnings and get a dll of about 700 kB.
Nil shows however in Dependency Walker, so it looks nil is exported.

Do I need to change anything in the amalgation source to compile 64 bits or
could it be that Dependency Walker doesn't work well with 64 bit dll's?
The machine is Win 7 64 bits.
I have problem at all compiling 32 bits.
Thanks for any advice.

RBS

[sqlite] Compiling sqlite as as library

[Prakash Premkumar]

I tried with the following flags :

gcc -arch x86_64 -o sqlite3.o sqlite3.c shell.c


  and


> gcc -m32  -o sqlite3.o sqlite3.c shell.c


but both results in the same error.

Can you please help me solve this ?

On Thu, Jul 2, 2015 at 2:47 PM, Andy Ling  wrote:

> > I get the following error while trying to compile after linking with the
> > library
> >
> > ld: warning: ignoring file
> > > /Users/prakash-2282/Downloads/sqlite-amalgamation-
> > 201506301510/libsqlite3.a,
> > > file was built for archive which is not the architecture being linked
> > > (x86_64):
> > > /Users/prakash-2282/Downloads/sqlite-amalgamation-
> > 201506301510/libsqlite3.a
> >
>
> I'm guessing, but it looks like your compiling for 64bit and linking to a
> 32bit system
> or vice versa.
>
> Regards
>
> Andy Ling
>
> ---
> This email has been scanned for email related threats and delivered safely
> by Mimecast.
> For more information please visit http://www.mimecast.com
>
> ---
>
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

[sqlite] Compiling sqlite as as library

[Prakash Premkumar]

Hi Andy,

I get the following error while trying to compile after linking with the
library

ld: warning: ignoring file
> /Users/prakash-2282/Downloads/sqlite-amalgamation-201506301510/libsqlite3.a,
> file was built for archive which is not the architecture being linked
> (x86_64):
> /Users/prakash-2282/Downloads/sqlite-amalgamation-201506301510/libsqlite3.a


Can you kindly help me resolve this ?

On Thu, Jul 2, 2015 at 1:51 PM, Andy Ling  wrote:

> > Can you please tell me how to compile it as a library on Mac OSX and
> Linux
> > platforms ?
> >
>
> Use your favourite compiler to generate sqlite3.o then use ar to wrap
> that up as a .a file. Give that file a name something like
> libsqlite3.a and you will be able to add -Lsqlite3 to your LDFLAGS.
>
> The ar command will be something like
>
> ar -rus libsqlite3.a sqlite3.o
>
> Check the man page for more information
>
> HTH
>
> Andy Ling
>
> ---
> This email has been scanned for email related threats and delivered safely
> by Mimecast.
> For more information please visit http://www.mimecast.com
>
> ---
>
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

[sqlite] Compiling sqlite as as library

[Prakash Premkumar]

Thanks a ton Andy for your reply.

can you specify how I should specify the include flags (-I).
The kore build complais that "sqlite3.h" header file is not found .

Thanks a lot for your time

On Thu, Jul 2, 2015 at 1:51 PM, Andy Ling  wrote:

> > Can you please tell me how to compile it as a library on Mac OSX and
> Linux
> > platforms ?
> >
>
> Use your favourite compiler to generate sqlite3.o then use ar to wrap
> that up as a .a file. Give that file a name something like
> libsqlite3.a and you will be able to add -Lsqlite3 to your LDFLAGS.
>
> The ar command will be something like
>
> ar -rus libsqlite3.a sqlite3.o
>
> Check the man page for more information
>
> HTH
>
> Andy Ling
>
> ---
> This email has been scanned for email related threats and delivered safely
> by Mimecast.
> For more information please visit http://www.mimecast.com
>
> ---
>
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

[sqlite] Compiling sqlite as as library

[Amit Chaudhuri]

Maybe this will help?

http://stackoverflow.com/questions/4234767/how-do-i-build-sqlite3-from-command-line

On Thu, Jul 2, 2015 at 10:25 AM, Prakash Premkumar
 wrote:
> I tried with the following flags :
>
> gcc -arch x86_64 -o sqlite3.o sqlite3.c shell.c
>
>
>   and
>
>
>> gcc -m32  -o sqlite3.o sqlite3.c shell.c
>
>
> but both results in the same error.
>
> Can you please help me solve this ?
>
> On Thu, Jul 2, 2015 at 2:47 PM, Andy Ling  wrote:
>
>> > I get the following error while trying to compile after linking with the
>> > library
>> >
>> > ld: warning: ignoring file
>> > > /Users/prakash-2282/Downloads/sqlite-amalgamation-
>> > 201506301510/libsqlite3.a,
>> > > file was built for archive which is not the architecture being linked
>> > > (x86_64):
>> > > /Users/prakash-2282/Downloads/sqlite-amalgamation-
>> > 201506301510/libsqlite3.a
>> >
>>
>> I'm guessing, but it looks like your compiling for 64bit and linking to a
>> 32bit system
>> or vice versa.
>>
>> Regards
>>
>> Andy Ling
>>
>> ---
>> This email has been scanned for email related threats and delivered safely
>> by Mimecast.
>> For more information please visit http://www.mimecast.com
>>
>> ---
>>
>> ___
>> sqlite-users mailing list
>> sqlite-users at mailinglists.sqlite.org
>> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>>
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Compiling sqlite as as library

[Prakash Premkumar]

Thanks for your reply Kees.

I am using kore web server and I want to pass sqlite library in the LDFLAGS
option to the kore webserver. ( https://kore.io/doc/#cli )

For this purpose, I would like to compile it as a library, I wont be able
to pass the sqlite3.c in the list of sources.

Can you please tell me how to compile it as a library on Mac OSX and Linux
platforms ?

On Wed, Jul 1, 2015 at 7:28 PM, Kees Nuyt  wrote:

> On Wed, 1 Jul 2015 14:28:37 +0530, Prakash Premkumar
>  wrote:
>
> >Hi,
> >
> >Can you please tell me how to compile sqlite as a library and link with
> >other applications using the "-L" flag ?
>
> That depends on the operating system you want to use it on.
> For many common platforms a precompiled binary is available on
> the download page:
> http://www.sqlite.org/download.html
>
> The link recipe depends on your platform and toolchain.
> Oftentimes, is it sufficent to add the sqlite3 amalgamation
> source (which you can make with 'make sqlite3.c') to your list
> of sources. For example the sqlite3 command line tool is build
> using:
> gcc ${CFLAGS} -o sqlite3 sqlite3.c src/shell.c
>
> More info:
> http://www.sqlite.org/howtocompile.html
>
> I hope this helps. If you need more detailed info, please reply
> with the specifications of your platform.
>
> --
> Regards,
>
> Kees Nuyt
>
> ___
> sqlite-users mailing list
> sqlite-users at mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>

[sqlite] Compiling sqlite as as library

[Andy Ling]

> I tried with the following flags :
> 
> gcc -arch x86_64 -o sqlite3.o sqlite3.c shell.c
> 
> 
>   and
> 
> 
> > gcc -m32  -o sqlite3.o sqlite3.c shell.c
> 
> 
> but both results in the same error.
> 
> Can you please help me solve this ?
> 

It's getting outside my level of expertise (and not really sqlite specific).
Try googling, there are lots of results. Maybe something like this will help

https://github.com/tpoechtrager/osxcross/issues/11

Regards

Andy Ling
---
This email has been scanned for email related threats and delivered safely by 
Mimecast.
For more information please visit http://www.mimecast.com
---

[sqlite] Compiling sqlite as as library

[Andy Ling]

> I get the following error while trying to compile after linking with the
> library
> 
> ld: warning: ignoring file
> > /Users/prakash-2282/Downloads/sqlite-amalgamation-
> 201506301510/libsqlite3.a,
> > file was built for archive which is not the architecture being linked
> > (x86_64):
> > /Users/prakash-2282/Downloads/sqlite-amalgamation-
> 201506301510/libsqlite3.a
> 

I'm guessing, but it looks like your compiling for 64bit and linking to a 32bit 
system
or vice versa.

Regards

Andy Ling
---
This email has been scanned for email related threats and delivered safely by 
Mimecast.
For more information please visit http://www.mimecast.com
---

[sqlite] Compiling sqlite as as library

[Andy Ling]

> Thanks a ton Andy for your reply.
> 
> can you specify how I should specify the include flags (-I).
> The kore build complais that "sqlite3.h" header file is not found .
> 

Sounds like you need to read a few more manuals :^)

Normally there are compiler options that let you tell it which directories
to look in. For header files it is normally -I for include directories
and for libraries it is -L. So just use these to add the directories that
contain your sqlite3.h and libsqlite3.a files.

Regards

Andy Ling
---
This email has been scanned for email related threats and delivered safely by 
Mimecast.
For more information please visit http://www.mimecast.com
---

[sqlite] Compiling sqlite as as library

[Andy Ling]

> Can you please tell me how to compile it as a library on Mac OSX and Linux
> platforms ?
> 

Use your favourite compiler to generate sqlite3.o then use ar to wrap
that up as a .a file. Give that file a name something like
libsqlite3.a and you will be able to add -Lsqlite3 to your LDFLAGS.

The ar command will be something like

ar -rus libsqlite3.a sqlite3.o

Check the man page for more information

HTH

Andy Ling
---
This email has been scanned for email related threats and delivered safely by 
Mimecast.
For more information please visit http://www.mimecast.com
---

[sqlite] Compiling sqlite as as library

[Kees Nuyt]

On Wed, 1 Jul 2015 14:28:37 +0530, Prakash Premkumar
 wrote:

>Hi,
>
>Can you please tell me how to compile sqlite as a library and link with
>other applications using the "-L" flag ?

That depends on the operating system you want to use it on.
For many common platforms a precompiled binary is available on
the download page:
http://www.sqlite.org/download.html

The link recipe depends on your platform and toolchain.
Oftentimes, is it sufficent to add the sqlite3 amalgamation
source (which you can make with 'make sqlite3.c') to your list
of sources. For example the sqlite3 command line tool is build
using:
gcc ${CFLAGS} -o sqlite3 sqlite3.c src/shell.c

More info:
http://www.sqlite.org/howtocompile.html

I hope this helps. If you need more detailed info, please reply
with the specifications of your platform.

-- 
Regards,

Kees Nuyt

[sqlite] Compiling sqlite as as library

[Prakash Premkumar]

Hi,

Can you please tell me how to compile sqlite as a library and link with
other applications using the "-L" flag ?


Thanks a lot for your time .

Re: [sqlite] Compiling SQLite on VxWorks 6.3 (DKM)

[Roger Binns]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 28/02/14 06:37, deltuo wrote:
> i compile sqlite 3.8.3 to vxworks 6.9,  i  first compile sqlite in dkm
> and get xx.a lib file, and then test it in vip project, but meet disk
> i/o error, can you help me ? thank you , my email is del...@126.com

  http://catb.org/~esr/faqs/smart-questions.html

Roger

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)

iEUEARECAAYFAlMSPxoACgkQmOOfHg372QQXIQCfT7Sa9kempGXWTYs+L6aot98I
Rw8AmJ2dp9jR0bN0FThp98ab/ZygeD0=
=T0I3
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling SQLite on VxWorks 6.3 (DKM)

[deltuo]

i compile sqlite 3.8.3 to vxworks 6.9,  i  first compile sqlite in dkm and
get xx.a lib file, and then test it in vip project, but meet disk i/o error,
can you help me ? thank you , my email is del...@126.com



--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/Compiling-SQLite-on-VxWorks-6-3-DKM-tp63955p74185.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Compiling SQLite with latest MinGW: undesired link to MinGW-specific dll.

[Jan Nijtmans]

When compiled SQLite out-of-the-box on MinGW-4.0
there are two problems. One is currently in progress
on the "mingw4x" branch, but there is one more.
For explanation and a suggested fix, see below.

When compiling sqlite3.dll, it contains a link to
libgcc_s_dw2-1.dll, which must be distributed
together with sqlite3.dll. Dit is - of course -
not desired. A workaround is easy: Add the
option "-static-libgcc" in the link line. Earlier
MinGW versions only had a static gcc library,
so it is safe to use this option always: In
MinGW 3 "-static-libgcc" was the default
anyway. Most recent MinGW-w64 versions
have exactly the same problem, only the
required dll name is different (libgcc_s_sjlj-1.dll).
This solution works for MinGW-w64 as well.

This bug is already reported to MinGW,
for details:


Regards,
Jan Nijtmans

===
--- Makefile.in
+++ Makefile.in
@@ -1001,7 +1001,7 @@
echo 'EXPORTS' >sqlite3.def
nm $(REAL_LIBOBJ) | grep ' T ' | grep ' _sqlite3_' \
| sed 's/^.* _//' >>sqlite3.def

 sqlite3.dll: $(REAL_LIBOBJ) sqlite3.def
-   $(TCC) -shared -o $@ sqlite3.def \
+   $(TCC) -shared -static-libgcc -o $@ sqlite3.def \
-Wl,"--strip-all" $(REAL_LIBOBJ)
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Compiling sqlite (amalgamation) with ICU support for windows

[Jens Helweg]

Hello, 
 
I am trying to compile sqlite db with icu support using cygwin on windows. 
 
As I am using the amalgamation version my understanding is that everthing I 
need is already included. 
 
But when I try to compile this it complains about missing header files: 
> gcc.exe -DSQLITE_ENABLE_ICU -DSQLITE_ENABLE_FTS3 -c shell.c sqlite3.c

it results in: 
> unicode/utypes.h: No such file or directory
> #include 
 
So I downloaded icu binary package (icu4c-52_1-Win64-msvc10.zip) that has the 
missing header files and included them like this: 
> gcc.exe -DSQLITE_ENABLE_ICU -DSQLITE_ENABLE_FTS3 
> -I/cygdrive/c//icu/include/ -c shell.c sqlite3.c
 
Then it is not complaining about the missing headers files anymore and produces 
an object file: 
> sqlite3.o
 
Now I am trying to create a dll out of this file with the following: 
> gcc -shared -o sqlite.dll sqlite3.o
 
But the linker complains about missing functions: 
> sqlite3.o:sqlite3.c:(.text+0x115d): undefined reference to `_localtime64'
> sqlite3.o:sqlite3.c:(.text+0x99f67): undefined reference to `u_foldCase_52'
> sqlite3.o:sqlite3.c:(.text+0x99f7d): undefined reference to `u_foldCase_52'
> sqlite3.o:sqlite3.c:(.text+0x9a17f): undefined reference to 
> `utf8_nextCharSafeBody_52'
> sqlite3.o:sqlite3.c:(.text+0x9a1f2): undefined reference to `u_errorName_52'
> sqlite3.o:sqlite3.c:(.text+0x9a255): undefined reference to `uregex_close_52
> ...
 
I need to get a dll file because I would like to put this into the JDBC driver 
for SQLite which is basically a wrapper around the native implementation. Wich 
is a dll file on windows. 
 
Did anybody sucessfully do this? Or maybe have an idea as to what I am 
missing/doing wrong?
 
Thx & regards, 
Jens
 
 
 
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling SQLite for Windows Phone 8 (revised)

[andy]

> However, running inside the WinRT sandbox will introduce some complications 
> for dynamic loading

 

For whatever it’s worth, my use case seems to work okay.  I’m building my own 
extension as a DLL and am able to deploy it with a test WP8 app, load it via 
sqlite3_load_extension, and successfully use its functionality (obviously using 
my own build of SQLite with extensions enabled).  This use case also works fine 
for me on WinRT, though there I’m also able to use the official SQLite 
distribution since it doesn’t disable extensions.

 

Thanks again Joe, I really appreciate your help!

 


From: Joe Mistachkin
Sent: ‎May‎ ‎28‎, ‎2013 ‎6‎:‎36‎ ‎PM
To: 'General Discussion of SQLite Database'
Subject: Re: [sqlite] Compiling SQLite for Windows Phone 8 (revised)



a...@sourcegear.com wrote:
>
> Why is the default to disable extensions on WP8?
>

I'm actually not sure at this point.  Previously, it was disabled due
to lack of the necessary OS APIs.

>
> Is there something about the platform that makes extensions not work?
>

If the extensions are statically linked, things may work fine.  However,
running inside the WinRT sandbox will introduce some complications for
dynamic loading, see:

http://msdn.microsoft.com/en-us/library/windows/desktop/hh447159%28v=vs.85%2
9.aspx

--
Joe Mistachkin

___
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

Re: [sqlite] Compiling SQLite for Windows Phone 8 (revised)

[Joe Mistachkin]

a...@sourcegear.com wrote:
>
> Why is the default to disable extensions on WP8?
>

I'm actually not sure at this point.  Previously, it was disabled due
to lack of the necessary OS APIs.

>
> Is there something about the platform that makes extensions not work?
>

If the extensions are statically linked, things may work fine.  However,
running inside the WinRT sandbox will introduce some complications for
dynamic loading, see:

http://msdn.microsoft.com/en-us/library/windows/desktop/hh447159%28v=vs.85%2
9.aspx

--
Joe Mistachkin

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

Re: [sqlite] Compiling SQLite for Windows Phone 8 (revised)

[andy]

Thanks Joe!

 

It looks like SQLITE_WIN32_FILEMAPPING_API=1 is what I was missing.

 

A related question: Your command includes SQLITE_OMIT_LOAD_EXTENSION=1 and the 
official WP8 build is also built this way.  One of the reasons that I wanted to 
build it myself was to allow extension loading.  Why is the default to disable 
extensions on WP8?  Is there something about the platform that makes extensions 
not work?  With the filemapping flag defined I can build successfully with 
extensions enabled, so it’s not due to a compile-time problem such as 
unsupported APIs.  Is there a runtime issue where loading/using extensions is 
asking for trouble?  I’ll try it out in the morning and see what happens, but 
I’m curious what issue(s) might be lurking.

 

Thanks again!

 


From: Joe Mistachkin
Sent: ‎May‎ ‎28‎, ‎2013 ‎3‎:‎11‎ ‎PM
To: 'General Discussion of SQLite Database'
Subject: Re: [sqlite] Compiling SQLite for Windows Phone 8 (revised)



a...@sourcegear.com wrote:
>
> What do I have to do to generate one myself?  
>

Sorry, slight revision...

>From a Visual Studio 2012 Phone Tools (you'll need the WP8 SDK) command
prompt,
the following commands should work:

SET NCRTLIBPATH=%ProgramFiles(x86)%\Microsoft Visual Studio
11.0\VC\WPSDK\WP80\lib
SET NSDKLIBPATH=%ProgramFiles(x86)%\Windows Phone Kits\8.0\lib\x86

 nmake -f Makefile.msc sqlite3.dll XCOMPILE=1 USE_NATIVE_LIBPATHS=1
NO_TCL=1 FOR_WINRT=1 USE_RC=0 OPTS="-DWINAPI_FAMILY=WINAPI_FAMILY_PHONE_APP
-DSQLITE_OMIT_LOAD_EXTENSION=1 -DSQLITE_WIN32_FILEMAPPING_API=1" 
 
--
Joe Mistachkin

___
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

Re: [sqlite] Compiling SQLite for Windows Phone 8 (revised)

[Joe Mistachkin]

a...@sourcegear.com wrote:
>
> What do I have to do to generate one myself?  
>

Sorry, slight revision...

>From a Visual Studio 2012 Phone Tools (you'll need the WP8 SDK) command
prompt,
the following commands should work:

SET NCRTLIBPATH=%ProgramFiles(x86)%\Microsoft Visual Studio
11.0\VC\WPSDK\WP80\lib
SET NSDKLIBPATH=%ProgramFiles(x86)%\Windows Phone Kits\8.0\lib\x86

nmake -f Makefile.msc sqlite3.dll XCOMPILE=1 USE_NATIVE_LIBPATHS=1
NO_TCL=1 FOR_WINRT=1 USE_RC=0 OPTS="-DWINAPI_FAMILY=WINAPI_FAMILY_PHONE_APP
-DSQLITE_OMIT_LOAD_EXTENSION=1 -DSQLITE_WIN32_FILEMAPPING_API=1" 
 
--
Joe Mistachkin

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

Re: [sqlite] Compiling SQLite for Windows Phone 8

[Joe Mistachkin]

a...@sourcegear.com wrote:
>
> What do I have to do to generate one myself?  
>

>From a Visual Studio 2012 Phone Tools (you'll need the WP8 SDK) command
prompt,
the following commands should work:

SET NCRTLIBPATH=%ProgramFiles(x86)%\Microsoft Visual Studio
11.0\VC\WPSDK\WP80\lib
SET NSDKLIBPATH=%ProgramFiles(x86)%\Windows Phone Kits\8.0\lib\x86

nmake -f Makefile.msc sqlite3.dll FOR_WINRT=1 USE_RC=0
OPTS="-DWINAPI_FAMILY=WINAPI_FAMILY_PHONE_APP -DSQLITE_OMIT_LOAD_EXTENSION=1
-DSQLITE_WIN32_FILEMAPPING_API=1" 

--
Joe Mistachkin

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

[sqlite] Compiling SQLite for Windows Phone 8

[andy]

I’d like to generate my own build of SQLite from the amalgamation source for 
use in a WP8 app, but I can’t figure out how to compile it successfully.  
Building for WinRT was as simple as defining SQLITE_OS_WINRT so I expected 
something similar for WP8, but no amount of searching has turned up anything 
like that.  All I could find were a few unanswered questions on Stack 
Overflow[1][2] about people not even being able to build it for WP8 from the 
original sources and makefiles.

 

With no additional defines, compiling against the WP8 platform fails 
spectacularly, which is not surprising.  If I define SQLITE_OS_WINRT then the 
errors are trimmed down to just three about undeclared Windows APIs related to 
file mapping (CreateFileMappingFromApp, MapViewOfFileFromApp, and 
UnmapViewOfFile).  There appears to be some ambiguity about whether or not 
those functions are supposed to be supported by WP8; the documentation for the 
first two says that they are, but the actual SDK headers obviously don’t agree. 
 There’s an MSDN thread[3] noting this mismatch which also notes that SQLite 
both uses these APIs and works on WP8.  A reply there indicates that it may be 
possible to somehow be granted an exception to use those APIs even though the 
SDK doesn’t appear to support them.  Has SQLite been granted such an exception?

 

In any case, it’s clearly possible to build SQLite for WP8 because there’s an 
official distribution of such a build.  What do I have to do to generate one 
myself?  If SQLite has an exception to use APIs not generally available, then 
is it simply not possible for anyone other than an official distributor with 
inside info/headers/something?

 

Thanks a lot!

 

 

[1] http://stackoverflow.com/questions/14074821/build-sqlite-for-windows-phone-8

[2] 
http://stackoverflow.com/questions/14785506/compiling-sqlite-for-windows-phone-8

[3] 
http://social.msdn.microsoft.com/Forums/en-US/wpdevelop/thread/6114f2fe-1543-4121-bb4e-478c36207c5b
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Compiling SQLite on VxWorks 6.3 (DKM)

[Udon Shaun]

Hi all.

Finally got Sqlite 3.7.13 working on VxWorks 6.3 in DKM.
Thanks for all the help.

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

Re: [sqlite] Compiling sqlite

[Roger Binns]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 07/13/2011 10:56 AM, Jan Hudec wrote:
> In my experience, the .o files are significantly larger than the resulting
> binary.

The size command will tell you how big the code (aka text), data and zero
initialized data (aka bss) are for object or shared library files.  Anything
beyond those is the gunk you mentioned (symbols, linker information,
comments from various tools, debug info etc).

Here is the amalgamation compiled for Linux 32 bits as both an object file
and as a shared library.  No SQLite -D flags given and -O2 used, but not -g.

$ ls -lh sqlite3.so sqlite3.o
  506K  sqlite3.o
  521K  sqlite3.so
$ size sqlite3.so sqlite3.o
   textdata bss dec hex filename
 48121166081164  488983   77617 sqlite3.so
 43372932241132  438085   6af45 sqlite3.o
$ strip sqlite3.{so,o}
$ size sqlite3.so sqlite3.o
   textdata bss dec hex filename
 48121166081164  488983   77617 sqlite3.so
 43372932241132  438085   6af45 sqlite3.o
$ ls -lh sqlite3.so sqlite3.o
  428K  sqlite3.o
  482K  sqlite3.so

If you are trying to monitor size then use the size command!

Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk4eIKsACgkQmOOfHg372QRZ+wCgscuRxOlwfQpYuHRLAqEVKfpf
mswAn2XMpVFPcmn2nJop0WpPCYguQy1K
=AHFo
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling sqlite

[Jan Hudec]

On Tue, Jul 12, 2011 at 17:37:57 +0300, Baruch Burstein wrote:
> The website (http://www.sqlite.org/about.html) says that sqlite can be
> compiled to under 300K. I am using mingw32, and with no configuration did I
> manage to get sqlite3.o below 400k. What compiler/compiler options are used
> to reach <300K?

In my experience, the .o files are significantly larger than the resulting
binary. Depending on various circumstances, the object (and static library)
can be from 20% to over 10 times larger than the resulting binary. This is
because it has to contain a lot of information the linker need to properly
put everything together, but which will not appear in the final binary.

Debugging information is usually responsible for the larger differences, so
if you compile the .o without -g, the reduction won't be that big, but it's
quite expected that 400kB .o will not add more than 300kB to the binary it's
linked to.

Also don't forget to run the final binary through strip to really get rid of
all unnecessary symbol information. It will make crash dumps from it make no
sense at all, but it's possible to use objcopy to save the information strip
would remove in a separate file which gdb can use to interpret core dumps.

-- 
 Jan 'Bulb' Hudec 
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling sqlite

[Richard Hipp]

On Tue, Jul 12, 2011 at 10:37 AM, Baruch Burstein wrote:

> The website (http://www.sqlite.org/about.html) says that sqlite can be
> compiled to under 300K. I am using mingw32, and with no configuration did I
> manage to get sqlite3.o below 400k. What compiler/compiler options are used
> to reach <300K?
>

-Os together with various -DSQLITE_OMIT_x options.  But those
-DSQLITE_OMIT_ options are incompatible with Fossil.


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



-- 
D. Richard Hipp
d...@sqlite.org
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Compiling sqlite

[Baruch Burstein]

The website (http://www.sqlite.org/about.html) says that sqlite can be
compiled to under 300K. I am using mingw32, and with no configuration did I
manage to get sqlite3.o below 400k. What compiler/compiler options are used
to reach <300K?
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling SQLite on Solaris 64bit and SPARC?

[Lynton Grice]

Hi Dave,

I turned to compiling it manually on Solaris for now and that latest version
of SQLite compiled perfectly.

Thanks for your comment though, I will give it a try later ;-)

Lynton

-Original Message-
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of David Kirkby
Sent: 08 November 2010 09:35 PM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Compiling SQLite on Solaris 64bit and SPARC?

On 8 November 2010 16:09, Lynton Grice <lynton.gr...@logosworld.com> wrote:
> Hi all,
>
> Anybody out there got the latest version of SQLite compiled on Solaris 10
64
> bit?
>
> Perhaps I must add some options to the "./configure"?
>
> Thanks for the help ;-)
>
> Lynton

I've built sqlite-3.6.22 on 64-bit SPARC and it installs ok. I can't
speak for the latest version. I added -m64 to both CFLAGS and
CXXFLAGS. I think the latter is unnecessary, but Sqlite is used as
part of the Sage project, and we tend to build most things like that.

Dave
___
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

Re: [sqlite] Compiling SQLite on Solaris 64bit and SPARC?

[David Kirkby]

On 8 November 2010 16:09, Lynton Grice  wrote:
> Hi all,
>
> Anybody out there got the latest version of SQLite compiled on Solaris 10 64
> bit?
>
> Perhaps I must add some options to the "./configure"?
>
> Thanks for the help ;-)
>
> Lynton

I've built sqlite-3.6.22 on 64-bit SPARC and it installs ok. I can't
speak for the latest version. I added -m64 to both CFLAGS and
CXXFLAGS. I think the latter is unnecessary, but Sqlite is used as
part of the Sage project, and we tend to build most things like that.

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

Re: [sqlite] Compiling SQLite on Solaris 64bit and SPARC?

[Lynton Grice]

Hi all,

Anybody out there got the latest version of SQLite compiled on Solaris 10 64
bit?

Perhaps I must add some options to the "./configure"?

Thanks for the help ;-)

Lynton

-Original Message-
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Lynton Grice
Sent: 07 November 2010 07:01 PM
To: 'General Discussion of SQLite Database'
Subject: [sqlite] Compiling SQLite on Solaris 64bit and SPARC?
Importance: High

Hi there,

 

I have just downloaded the latest version of SQLite
(sqlite-amalgamation-3.7.3.tar.gz) and am trying to compile it on my Solaris
10 64bit machine, but get an error for some reason (see below).

 

I ran a "./configure" (with no parameters) and it seemed to be fine, but
then the moment I tried to run "make install" it gave the following error
below (not too many details):

 


# make install

/bin/bash ./libtool --tag=CC --mode=link gcc -DSQLITE_THREADSAFE=1
-DSQLITE_ENA

BLE_FTS3 -DSQLITE_ENABLE_RTREE -g -O2   -o libsqlite3.la -rpath
/usr/local/lib -

no-undefined -version-info 8:6:8 sqlite3.lo

rm -fr  .libs/libsqlite3.so .libs/libsqlite3.so.0 .libs/libsqlite3.so.0.8.6

gcc -shared -Wl,-h -Wl,libsqlite3.so.0 -o .libs/libsqlite3.so.0.8.6
.libs/sqlit

e3.o  -lc

(cd .libs && rm -f libsqlite3.so.0 && ln -s libsqlite3.so.0.8.6
libsqlite3.so.0)

(cd .libs && rm -f libsqlite3.so && ln -s libsqlite3.so.0.8.6 libsqlite3.so)

false cru .libs/libsqlite3.a  sqlite3.o

make: *** [libsqlite3.la] Error 1

 

I really need to get SQLite compiled very soon on Solaris, does anyone have
any advise on how I can compile SQLite on my Solaris machine? Any help will
be greatly appreciated ;-)

 

Thanks

 

Lynton

___
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] Compiling SQLite on Solaris 64bit and SPARC?

[Lynton Grice]

Hi there,

 

I have just downloaded the latest version of SQLite
(sqlite-amalgamation-3.7.3.tar.gz) and am trying to compile it on my Solaris
10 64bit machine, but get an error for some reason (see below).

 

I ran a "./configure" (with no parameters) and it seemed to be fine, but
then the moment I tried to run "make install" it gave the following error
below (not too many details):

 


# make install

/bin/bash ./libtool --tag=CC --mode=link gcc -DSQLITE_THREADSAFE=1
-DSQLITE_ENA

BLE_FTS3 -DSQLITE_ENABLE_RTREE -g -O2   -o libsqlite3.la -rpath
/usr/local/lib -

no-undefined -version-info 8:6:8 sqlite3.lo

rm -fr  .libs/libsqlite3.so .libs/libsqlite3.so.0 .libs/libsqlite3.so.0.8.6

gcc -shared -Wl,-h -Wl,libsqlite3.so.0 -o .libs/libsqlite3.so.0.8.6
.libs/sqlit

e3.o  -lc

(cd .libs && rm -f libsqlite3.so.0 && ln -s libsqlite3.so.0.8.6
libsqlite3.so.0)

(cd .libs && rm -f libsqlite3.so && ln -s libsqlite3.so.0.8.6 libsqlite3.so)

false cru .libs/libsqlite3.a  sqlite3.o

make: *** [libsqlite3.la] Error 1

 

I really need to get SQLite compiled very soon on Solaris, does anyone have
any advise on how I can compile SQLite on my Solaris machine? Any help will
be greatly appreciated ;-)

 

Thanks

 

Lynton

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

Re: [sqlite] Compiling SQLite as .lib increases projectsizeandbuildtime?

[Kurt D. Knudsen]

Seems I need to put the following in the Preprocessor Definitions:

SQLITE_ENABLE_COLUMN_METADATA

This makes it compile just dandy. Now my file sizes are back to normal. Hoorah.

You guys are amazing, a baker's dozen internets to each of you.

Regards,

Kurt

-Original Message-
From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] 
On Behalf Of Kurt D. Knudsen
Sent: Thursday, December 17, 2009 10:31 AM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Compiling SQLite as .lib increases 
projectsizeandbuildtime?

Yeah, seems to be giving me odd Linker errors now. I'm stumped. The .def file 
is in the project's folder and is referenced in the properties page. When I 
compile SQLite3, I get the following:

1>Compiling...
1>sqlite3.c
1>Linking...
1>sqlite3.def : error LNK2001: unresolved external symbol 
sqlite3_column_database_name
1>sqlite3.def : error LNK2001: unresolved external symbol 
sqlite3_column_database_name16
1>sqlite3.def : error LNK2001: unresolved external symbol 
sqlite3_column_origin_name
1>sqlite3.def : error LNK2001: unresolved external symbol 
sqlite3_column_origin_name16
1>sqlite3.def : error LNK2001: unresolved external symbol 
sqlite3_column_table_name
1>sqlite3.def : error LNK2001: unresolved external symbol 
sqlite3_column_table_name16
1>sqlite3.def : error LNK2001: unresolved external symbol 
sqlite3_table_column_metadata
1>D:\SQLite\Release\sqlite3.lib : fatal error LNK1120: 7 unresolved externals
1>Build log was saved at "file://d:\SQLite\sqlite\Release\BuildLog.htm"
1>sqlite3 - 8 error(s), 0 warning(s)
== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==

Any ideas?

-Original Message-
From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] 
On Behalf Of Kurt D. Knudsen
Sent: Thursday, December 17, 2009 10:19 AM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Compiling SQLite as .lib increases projectsizeandbuild 
time?

Hi Pavel,

I think that's the issue. The .def file was never included. I put the .def file 
in the sqlite's project folder and am getting linker errors when I compile. I 
probably didn't reference it properly, I'll report back in a few minutes with 
success or failure.



--- Igor ---
In Sqlite project, check Properties | Linker | Advanced | Import Library. Make 
sure it's not empty (normally, you should see something like 
$(OutputDir)$(TargetName).lib in there).

Linker produces an import library (a LIB file) as a side-effect or building a 
DLL (unless this is suppressed). Projects using the DLL need the import library 
to link to.

Igor Tandetnik

--
It is set to generate a .lib according to that setting, but from what Pavel 
said, it never does because the .def file is missing from the project. I've 
never heard of .def files before so this is a new issue for me. This is all 
quite exciting :)

Thanks,

Kurt

-Original Message-
From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] 
On Behalf Of Pavel Ivanov
Sent: Thursday, December 17, 2009 10:04 AM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Compiling SQLite as .lib increases project sizeandbuild 
time?

> If I remove the dependency on sqlite from HouseKeeper, it gives linker
> errors with unresolved symbols for sqlite3_* functions. Adding sqlite as
> a dependency to HouseKeeper causes it to look for the sqlite.lib file.

Make sure that .def file is included in you Sqlite project. When
compiling project as dll, compiler generates stub .lib file anyway for
linking with anybody who will need this dll. But if you don't include
.def file and thus don't define any functions to export from dll,
compiler doesn't generate .lib file and it can cause the error you
see.

Pavel

On Thu, Dec 17, 2009 at 9:49 AM, Kurt D. Knudsen <kknud...@zystemsgo.com> wrote:
> Pavel,
>
> I have not defined it in the Linker properties. I have a solution called
> 'SQLite Test' and inside it consists of 4 projects:
>
> HouseKeeper - compiles as .dll
> Common - compiles as .dll
> SQLiteTest - compiles as .exe
> Sqlite - forced to compile as .lib (Why?!)
>
> Under Project Dependencies:
> * HouseKeeper is dependent on Common and sqlite.
> * Common is dependent on just sqlite
> * SQLiteTest is dependent on HouseKeeper, Common, and sqlite
>
> If I remove the dependency on sqlite from HouseKeeper, it gives linker
> errors with unresolved symbols for sqlite3_* functions. Adding sqlite as
> a dependency to HouseKeeper causes it to look for the sqlite.lib file.
>
> ---
>
> Teg,
>
> I'd like to keep it an external .dll file if possible, it doesn't make
> sense to me to have it added to each project that uses SQLite. SQLite
> is, as stated above, its own project inside of the solution.
>
> How do I go about making the other projects reference t

Re: [sqlite] Compiling SQLite as .lib increases projectsizeandbuild time?

[Pavel Ivanov]

This API is available in SQLite only if you compile with
SQLITE_ENABLE_COLUMN_METADATA defined. Obviously you don't compile
with this option and don't need it, so just remove these function
names from .def file.

Pavel

On Thu, Dec 17, 2009 at 10:30 AM, Kurt D. Knudsen
<kknud...@zystemsgo.com> wrote:
> Yeah, seems to be giving me odd Linker errors now. I'm stumped. The .def file 
> is in the project's folder and is referenced in the properties page. When I 
> compile SQLite3, I get the following:
>
> 1>Compiling...
> 1>sqlite3.c
> 1>Linking...
> 1>sqlite3.def : error LNK2001: unresolved external symbol 
> sqlite3_column_database_name
> 1>sqlite3.def : error LNK2001: unresolved external symbol 
> sqlite3_column_database_name16
> 1>sqlite3.def : error LNK2001: unresolved external symbol 
> sqlite3_column_origin_name
> 1>sqlite3.def : error LNK2001: unresolved external symbol 
> sqlite3_column_origin_name16
> 1>sqlite3.def : error LNK2001: unresolved external symbol 
> sqlite3_column_table_name
> 1>sqlite3.def : error LNK2001: unresolved external symbol 
> sqlite3_column_table_name16
> 1>sqlite3.def : error LNK2001: unresolved external symbol 
> sqlite3_table_column_metadata
> 1>D:\SQLite\Release\sqlite3.lib : fatal error LNK1120: 7 unresolved externals
> 1>Build log was saved at "file://d:\SQLite\sqlite\Release\BuildLog.htm"
> 1>sqlite3 - 8 error(s), 0 warning(s)
> == Rebuild All: 0 succeeded, 1 failed, 0 skipped ==
>
> Any ideas?
>
> -Original Message-
> From: sqlite-users-boun...@sqlite.org 
> [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Kurt D. Knudsen
> Sent: Thursday, December 17, 2009 10:19 AM
> To: General Discussion of SQLite Database
> Subject: Re: [sqlite] Compiling SQLite as .lib increases projectsizeandbuild 
> time?
>
> Hi Pavel,
>
> I think that's the issue. The .def file was never included. I put the .def 
> file in the sqlite's project folder and am getting linker errors when I 
> compile. I probably didn't reference it properly, I'll report back in a few 
> minutes with success or failure.
>
>
> --- Igor ---
> In Sqlite project, check Properties | Linker | Advanced | Import Library. 
> Make sure it's not empty (normally, you should see something like 
> $(OutputDir)$(TargetName).lib in there).
>
> Linker produces an import library (a LIB file) as a side-effect or building a 
> DLL (unless this is suppressed). Projects using the DLL need the import 
> library to link to.
>
> Igor Tandetnik
>
> --
> It is set to generate a .lib according to that setting, but from what Pavel 
> said, it never does because the .def file is missing from the project. I've 
> never heard of .def files before so this is a new issue for me. This is all 
> quite exciting :)
>
> Thanks,
>
> Kurt
>
> -Original Message-
> From: sqlite-users-boun...@sqlite.org 
> [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Pavel Ivanov
> Sent: Thursday, December 17, 2009 10:04 AM
> To: General Discussion of SQLite Database
> Subject: Re: [sqlite] Compiling SQLite as .lib increases project sizeandbuild 
> time?
>
>> If I remove the dependency on sqlite from HouseKeeper, it gives linker
>> errors with unresolved symbols for sqlite3_* functions. Adding sqlite as
>> a dependency to HouseKeeper causes it to look for the sqlite.lib file.
>
> Make sure that .def file is included in you Sqlite project. When
> compiling project as dll, compiler generates stub .lib file anyway for
> linking with anybody who will need this dll. But if you don't include
> .def file and thus don't define any functions to export from dll,
> compiler doesn't generate .lib file and it can cause the error you
> see.
>
> Pavel
>
> On Thu, Dec 17, 2009 at 9:49 AM, Kurt D. Knudsen <kknud...@zystemsgo.com> 
> wrote:
>> Pavel,
>>
>> I have not defined it in the Linker properties. I have a solution called
>> 'SQLite Test' and inside it consists of 4 projects:
>>
>> HouseKeeper - compiles as .dll
>> Common - compiles as .dll
>> SQLiteTest - compiles as .exe
>> Sqlite - forced to compile as .lib (Why?!)
>>
>> Under Project Dependencies:
>> * HouseKeeper is dependent on Common and sqlite.
>> * Common is dependent on just sqlite
>> * SQLiteTest is dependent on HouseKeeper, Common, and sqlite
>>
>> If I remove the dependency on sqlite from HouseKeeper, it gives linker
>> errors with unresolved symbols for sqlite3_* functions. Adding sqlite as
>> a dependency to HouseKeeper causes it to look for the sqlite.lib file.
>>
>> ---
>>
>> Teg,
>>
>> I'd like to keep i

Re: [sqlite] Compiling SQLite as .lib increases projectsizeandbuild time?

[Kurt D. Knudsen]

Yeah, seems to be giving me odd Linker errors now. I'm stumped. The .def file 
is in the project's folder and is referenced in the properties page. When I 
compile SQLite3, I get the following:

1>Compiling...
1>sqlite3.c
1>Linking...
1>sqlite3.def : error LNK2001: unresolved external symbol 
sqlite3_column_database_name
1>sqlite3.def : error LNK2001: unresolved external symbol 
sqlite3_column_database_name16
1>sqlite3.def : error LNK2001: unresolved external symbol 
sqlite3_column_origin_name
1>sqlite3.def : error LNK2001: unresolved external symbol 
sqlite3_column_origin_name16
1>sqlite3.def : error LNK2001: unresolved external symbol 
sqlite3_column_table_name
1>sqlite3.def : error LNK2001: unresolved external symbol 
sqlite3_column_table_name16
1>sqlite3.def : error LNK2001: unresolved external symbol 
sqlite3_table_column_metadata
1>D:\SQLite\Release\sqlite3.lib : fatal error LNK1120: 7 unresolved externals
1>Build log was saved at "file://d:\SQLite\sqlite\Release\BuildLog.htm"
1>sqlite3 - 8 error(s), 0 warning(s)
== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==

Any ideas?

-Original Message-
From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] 
On Behalf Of Kurt D. Knudsen
Sent: Thursday, December 17, 2009 10:19 AM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Compiling SQLite as .lib increases projectsizeandbuild 
time?

Hi Pavel,

I think that's the issue. The .def file was never included. I put the .def file 
in the sqlite's project folder and am getting linker errors when I compile. I 
probably didn't reference it properly, I'll report back in a few minutes with 
success or failure.


--- Igor ---
In Sqlite project, check Properties | Linker | Advanced | Import Library. Make 
sure it's not empty (normally, you should see something like 
$(OutputDir)$(TargetName).lib in there).

Linker produces an import library (a LIB file) as a side-effect or building a 
DLL (unless this is suppressed). Projects using the DLL need the import library 
to link to.

Igor Tandetnik

--
It is set to generate a .lib according to that setting, but from what Pavel 
said, it never does because the .def file is missing from the project. I've 
never heard of .def files before so this is a new issue for me. This is all 
quite exciting :)

Thanks,

Kurt

-Original Message-
From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] 
On Behalf Of Pavel Ivanov
Sent: Thursday, December 17, 2009 10:04 AM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Compiling SQLite as .lib increases project sizeandbuild 
time?

> If I remove the dependency on sqlite from HouseKeeper, it gives linker
> errors with unresolved symbols for sqlite3_* functions. Adding sqlite as
> a dependency to HouseKeeper causes it to look for the sqlite.lib file.

Make sure that .def file is included in you Sqlite project. When
compiling project as dll, compiler generates stub .lib file anyway for
linking with anybody who will need this dll. But if you don't include
.def file and thus don't define any functions to export from dll,
compiler doesn't generate .lib file and it can cause the error you
see.

Pavel

On Thu, Dec 17, 2009 at 9:49 AM, Kurt D. Knudsen <kknud...@zystemsgo.com> wrote:
> Pavel,
>
> I have not defined it in the Linker properties. I have a solution called
> 'SQLite Test' and inside it consists of 4 projects:
>
> HouseKeeper - compiles as .dll
> Common - compiles as .dll
> SQLiteTest - compiles as .exe
> Sqlite - forced to compile as .lib (Why?!)
>
> Under Project Dependencies:
> * HouseKeeper is dependent on Common and sqlite.
> * Common is dependent on just sqlite
> * SQLiteTest is dependent on HouseKeeper, Common, and sqlite
>
> If I remove the dependency on sqlite from HouseKeeper, it gives linker
> errors with unresolved symbols for sqlite3_* functions. Adding sqlite as
> a dependency to HouseKeeper causes it to look for the sqlite.lib file.
>
> ---
>
> Teg,
>
> I'd like to keep it an external .dll file if possible, it doesn't make
> sense to me to have it added to each project that uses SQLite. SQLite
> is, as stated above, its own project inside of the solution.
>
> How do I go about making the other projects reference the .dll instead
> of requiring the .lib? I should note that I am not the original author
> of this solution, just modifying it to use SQLite instead of flat-files.
> So I am unsure how the other developer set the solution up since
> HouseKeeper and Common both compile as .dll.
>
> I've been trying to contact the original developer that we hired but
> can't seem to get a hold of him since we're in different time zones.
> I'll try again to see if he can help me properly set up the solution if
> I am making no sense here :)
>

Re: [sqlite] Compiling SQLite as .lib increases project sizeandbuild time?

[Kurt D. Knudsen]

Hi Pavel,

I think that's the issue. The .def file was never included. I put the .def file 
in the sqlite's project folder and am getting linker errors when I compile. I 
probably didn't reference it properly, I'll report back in a few minutes with 
success or failure.

--- Igor ---
In Sqlite project, check Properties | Linker | Advanced | Import Library. Make 
sure it's not empty (normally, you should see something like 
$(OutputDir)$(TargetName).lib in there).

Linker produces an import library (a LIB file) as a side-effect or building a 
DLL (unless this is suppressed). Projects using the DLL need the import library 
to link to.

Igor Tandetnik

--
It is set to generate a .lib according to that setting, but from what Pavel 
said, it never does because the .def file is missing from the project. I've 
never heard of .def files before so this is a new issue for me. This is all 
quite exciting :)

Thanks,

Kurt

-Original Message-
From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] 
On Behalf Of Pavel Ivanov
Sent: Thursday, December 17, 2009 10:04 AM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Compiling SQLite as .lib increases project sizeandbuild 
time?

> If I remove the dependency on sqlite from HouseKeeper, it gives linker
> errors with unresolved symbols for sqlite3_* functions. Adding sqlite as
> a dependency to HouseKeeper causes it to look for the sqlite.lib file.

Make sure that .def file is included in you Sqlite project. When
compiling project as dll, compiler generates stub .lib file anyway for
linking with anybody who will need this dll. But if you don't include
.def file and thus don't define any functions to export from dll,
compiler doesn't generate .lib file and it can cause the error you
see.

Pavel

On Thu, Dec 17, 2009 at 9:49 AM, Kurt D. Knudsen <kknud...@zystemsgo.com> wrote:
> Pavel,
>
> I have not defined it in the Linker properties. I have a solution called
> 'SQLite Test' and inside it consists of 4 projects:
>
> HouseKeeper - compiles as .dll
> Common - compiles as .dll
> SQLiteTest - compiles as .exe
> Sqlite - forced to compile as .lib (Why?!)
>
> Under Project Dependencies:
> * HouseKeeper is dependent on Common and sqlite.
> * Common is dependent on just sqlite
> * SQLiteTest is dependent on HouseKeeper, Common, and sqlite
>
> If I remove the dependency on sqlite from HouseKeeper, it gives linker
> errors with unresolved symbols for sqlite3_* functions. Adding sqlite as
> a dependency to HouseKeeper causes it to look for the sqlite.lib file.
>
> ---
>
> Teg,
>
> I'd like to keep it an external .dll file if possible, it doesn't make
> sense to me to have it added to each project that uses SQLite. SQLite
> is, as stated above, its own project inside of the solution.
>
> How do I go about making the other projects reference the .dll instead
> of requiring the .lib? I should note that I am not the original author
> of this solution, just modifying it to use SQLite instead of flat-files.
> So I am unsure how the other developer set the solution up since
> HouseKeeper and Common both compile as .dll.
>
> I've been trying to contact the original developer that we hired but
> can't seem to get a hold of him since we're in different time zones.
> I'll try again to see if he can help me properly set up the solution if
> I am making no sense here :)
>
> I hope you guys can help me out; it'd make life quite a bit easier.
>
> Thanks,
>
> Kurt
>
> -Original Message-
>> 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
>
> -Original Message-
> From: sqlite-users-boun...@sqlite.org
> [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Teg
> Sent: Thursday, December 17, 2009 9:13 AM
> To: General Discussion of SQLite Database
> Subject: Re: [sqlite] Compiling SQLite as .lib increases project size
> andbuild time?
>
> Hello Kurt,
>
> The size increase is because you're including code IN the program
> instead of having it in a DLL. That's one of the benefits of DLLs. The
> second thing, the build time thing is because you've chosen to build
> SQLite each and every time you build the entire project. That's purely
> a design choice in how you build. It's how I do it too. Your other
> option is to make Sqlite it's own project and only build it when it
> changes but, link it in by manually adding the lib path and lib name
> to the linker.
>
> I have some projects I build every time when doing a release, like
> SQlite and I have

Re: [sqlite] Compiling SQLite as .lib increases project size andbuild time?

[Pavel Ivanov]

> If I remove the dependency on sqlite from HouseKeeper, it gives linker
> errors with unresolved symbols for sqlite3_* functions. Adding sqlite as
> a dependency to HouseKeeper causes it to look for the sqlite.lib file.

Make sure that .def file is included in you Sqlite project. When
compiling project as dll, compiler generates stub .lib file anyway for
linking with anybody who will need this dll. But if you don't include
.def file and thus don't define any functions to export from dll,
compiler doesn't generate .lib file and it can cause the error you
see.

Pavel

On Thu, Dec 17, 2009 at 9:49 AM, Kurt D. Knudsen <kknud...@zystemsgo.com> wrote:
> Pavel,
>
> I have not defined it in the Linker properties. I have a solution called
> 'SQLite Test' and inside it consists of 4 projects:
>
> HouseKeeper - compiles as .dll
> Common - compiles as .dll
> SQLiteTest - compiles as .exe
> Sqlite - forced to compile as .lib (Why?!)
>
> Under Project Dependencies:
> * HouseKeeper is dependent on Common and sqlite.
> * Common is dependent on just sqlite
> * SQLiteTest is dependent on HouseKeeper, Common, and sqlite
>
> If I remove the dependency on sqlite from HouseKeeper, it gives linker
> errors with unresolved symbols for sqlite3_* functions. Adding sqlite as
> a dependency to HouseKeeper causes it to look for the sqlite.lib file.
>
> ---
>
> Teg,
>
> I'd like to keep it an external .dll file if possible, it doesn't make
> sense to me to have it added to each project that uses SQLite. SQLite
> is, as stated above, its own project inside of the solution.
>
> How do I go about making the other projects reference the .dll instead
> of requiring the .lib? I should note that I am not the original author
> of this solution, just modifying it to use SQLite instead of flat-files.
> So I am unsure how the other developer set the solution up since
> HouseKeeper and Common both compile as .dll.
>
> I've been trying to contact the original developer that we hired but
> can't seem to get a hold of him since we're in different time zones.
> I'll try again to see if he can help me properly set up the solution if
> I am making no sense here :)
>
> I hope you guys can help me out; it'd make life quite a bit easier.
>
> Thanks,
>
> Kurt
>
> -Original Message-
>> 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
>
> -Original Message-
> From: sqlite-users-boun...@sqlite.org
> [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Teg
> Sent: Thursday, December 17, 2009 9:13 AM
> To: General Discussion of SQLite Database
> Subject: Re: [sqlite] Compiling SQLite as .lib increases project size
> andbuild time?
>
> Hello Kurt,
>
> The size increase is because you're including code IN the program
> instead of having it in a DLL. That's one of the benefits of DLLs. The
> second thing, the build time thing is because you've chosen to build
> SQLite each and every time you build the entire project. That's purely
> a design choice in how you build. It's how I do it too. Your other
> option is to make Sqlite it's own project and only build it when it
> changes but, link it in by manually adding the lib path and lib name
> to the linker.
>
> I have some projects I build every time when doing a release, like
> SQlite and I have some projects like OpenSLL where I build once and
> only reference the lib.
>
> I find that SQlite builds very quickly. Takes about 20 seconds in
> release 64 bits with full optimization. I could make it faster if I
> turned on pre-compiled headers but, it doesn't seem worth the effort.
> During development, it only build when it changes.
>
> Perhaps you only have one project and you've lumped everything
> together? I'd break SQlite out into it's own project then use project
> dependencies to make the linker include it.
>
> C
>
> Thursday, December 17, 2009, 9:01:04 AM, you wrote:
>
> KDK> Hi all,
>
> KDK>
>
> KDK> Since we're moving our project over from flat-files to an SQL DB,
> I've
> KDK> noticed that projects that utilize SQLite3 have increased to over
> 500k
> KDK> in size. Their original sizes were between 50-100k. Also, the build
> KDK> times have increased dramatically. I have SQLite added as a
> separate
> KDK> project in my solution (Visual Studio 2008) and have its
> Configuration
> KDK> Type as .lib. If I set it to .dll, then the rest of the projects
> fail to
> KDK> link prop

Re: [sqlite] Compiling SQLite as .lib increases project sizeandbuild time?

[Igor Tandetnik]

Kurt D. Knudsen wrote:
> I have not defined it in the Linker properties. I have a solution called
> 'SQLite Test' and inside it consists of 4 projects:
> 
> HouseKeeper - compiles as .dll
> Common - compiles as .dll
> SQLiteTest - compiles as .exe
> Sqlite - forced to compile as .lib (Why?!)

In Sqlite project, check Properties | Linker | Advanced | Import Library. Make 
sure it's not empty (normally, you should see something like 
$(OutputDir)$(TargetName).lib in there).

Linker produces an import library (a LIB file) as a side-effect or building a 
DLL (unless this is suppressed). Projects using the DLL need the import library 
to link to.

Igor Tandetnik


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

Re: [sqlite] Compiling SQLite as .lib increases project size andbuild time?

[Kurt D. Knudsen]

Pavel,

I have not defined it in the Linker properties. I have a solution called
'SQLite Test' and inside it consists of 4 projects:

HouseKeeper - compiles as .dll
Common - compiles as .dll
SQLiteTest - compiles as .exe
Sqlite - forced to compile as .lib (Why?!)

Under Project Dependencies:
* HouseKeeper is dependent on Common and sqlite.
* Common is dependent on just sqlite
* SQLiteTest is dependent on HouseKeeper, Common, and sqlite

If I remove the dependency on sqlite from HouseKeeper, it gives linker
errors with unresolved symbols for sqlite3_* functions. Adding sqlite as
a dependency to HouseKeeper causes it to look for the sqlite.lib file.

---

Teg,

I'd like to keep it an external .dll file if possible, it doesn't make
sense to me to have it added to each project that uses SQLite. SQLite
is, as stated above, its own project inside of the solution.

How do I go about making the other projects reference the .dll instead
of requiring the .lib? I should note that I am not the original author
of this solution, just modifying it to use SQLite instead of flat-files.
So I am unsure how the other developer set the solution up since
HouseKeeper and Common both compile as .dll.

I've been trying to contact the original developer that we hired but
can't seem to get a hold of him since we're in different time zones.
I'll try again to see if he can help me properly set up the solution if
I am making no sense here :)

I hope you guys can help me out; it'd make life quite a bit easier.

Thanks,

Kurt

-Original Message-
> 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

-Original Message-
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Teg
Sent: Thursday, December 17, 2009 9:13 AM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Compiling SQLite as .lib increases project size
andbuild time?

Hello Kurt,

The size increase is because you're including code IN the program
instead of having it in a DLL. That's one of the benefits of DLLs. The
second thing, the build time thing is because you've chosen to build
SQLite each and every time you build the entire project. That's purely
a design choice in how you build. It's how I do it too. Your other
option is to make Sqlite it's own project and only build it when it
changes but, link it in by manually adding the lib path and lib name
to the linker.

I have some projects I build every time when doing a release, like
SQlite and I have some projects like OpenSLL where I build once and
only reference the lib.

I find that SQlite builds very quickly. Takes about 20 seconds in
release 64 bits with full optimization. I could make it faster if I
turned on pre-compiled headers but, it doesn't seem worth the effort.
During development, it only build when it changes.

Perhaps you only have one project and you've lumped everything
together? I'd break SQlite out into it's own project then use project
dependencies to make the linker include it.

C

Thursday, December 17, 2009, 9:01:04 AM, you wrote:

KDK> Hi all,

KDK>  

KDK> Since we're moving our project over from flat-files to an SQL DB,
I've
KDK> noticed that projects that utilize SQLite3 have increased to over
500k
KDK> in size. Their original sizes were between 50-100k. Also, the build
KDK> times have increased dramatically. I have SQLite added as a
separate
KDK> project in my solution (Visual Studio 2008) and have its
Configuration
KDK> Type as .lib. If I set it to .dll, then the rest of the projects
fail to
KDK> link properly stating: 

KDK>  

1>>LINK : fatal error LNK1181: cannot open input file
KDK> '..\release\sqlite.lib'

KDK>  

KDK> I'm curious to know if this is normal behavior and if SQLite must
be
KDK> compiled as a .lib as opposed to a .dll? The odd thing is, I have
other
KDK> projects in the solution that are set to compile as a .dll and they
link
KDK> fine with each other.

KDK>  

KDK> Relevant information:

KDK>  

KDK> Visual Studio 2008 Professional

KDK> Compiling as Release

KDK>  

KDK> Let me know if you need more information.

KDK>  

KDK> Thanks,

KDK>  

KDK> Kurt

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



-- 
Best regards,
 Tegmailto:t...@djii.com

___
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

Re: [sqlite] Compiling SQLite as .lib increases project size and build time?

[Teg]

Hello Kurt,

The size increase is because you're including code IN the program
instead of having it in a DLL. That's one of the benefits of DLLs. The
second thing, the build time thing is because you've chosen to build
SQLite each and every time you build the entire project. That's purely
a design choice in how you build. It's how I do it too. Your other
option is to make Sqlite it's own project and only build it when it
changes but, link it in by manually adding the lib path and lib name
to the linker.

I have some projects I build every time when doing a release, like
SQlite and I have some projects like OpenSLL where I build once and
only reference the lib.

I find that SQlite builds very quickly. Takes about 20 seconds in
release 64 bits with full optimization. I could make it faster if I
turned on pre-compiled headers but, it doesn't seem worth the effort.
During development, it only build when it changes.

Perhaps you only have one project and you've lumped everything
together? I'd break SQlite out into it's own project then use project
dependencies to make the linker include it.

C

Thursday, December 17, 2009, 9:01:04 AM, you wrote:

KDK> Hi all,

KDK>  

KDK> Since we're moving our project over from flat-files to an SQL DB, I've
KDK> noticed that projects that utilize SQLite3 have increased to over 500k
KDK> in size. Their original sizes were between 50-100k. Also, the build
KDK> times have increased dramatically. I have SQLite added as a separate
KDK> project in my solution (Visual Studio 2008) and have its Configuration
KDK> Type as .lib. If I set it to .dll, then the rest of the projects fail to
KDK> link properly stating: 

KDK>  

1>>LINK : fatal error LNK1181: cannot open input file
KDK> '..\release\sqlite.lib'

KDK>  

KDK> I'm curious to know if this is normal behavior and if SQLite must be
KDK> compiled as a .lib as opposed to a .dll? The odd thing is, I have other
KDK> projects in the solution that are set to compile as a .dll and they link
KDK> fine with each other.

KDK>  

KDK> Relevant information:

KDK>  

KDK> Visual Studio 2008 Professional

KDK> Compiling as Release

KDK>  

KDK> Let me know if you need more information.

KDK>  

KDK> Thanks,

KDK>  

KDK> Kurt

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



-- 
Best regards,
 Tegmailto:t...@djii.com

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

Re: [sqlite] Compiling SQLite as .lib increases project size and build time?

[Pavel Ivanov]

> 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  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

[sqlite] Compiling SQLite as .lib increases project size and build time?

[Kurt D. Knudsen]

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

Re: [sqlite] compiling Sqlite with ICU

[Sylvain Pointeau]

Hi,

thank you very much,

I enjoy so much sqlite with ICU,
I even installed the latest version of readline to enjoy characters like öäü
and with the ICU collation the sort order is right with those characters.

sqlite is really splendid!
Thank you so much for having made this software.

Best regards,
Sylvain

On Thu, Dec 10, 2009 at 9:30 PM, Roger Binns  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Sylvain Pointeau wrote:
> > just one last thing:
> > -lpthread -lm   -L/usr/local/lib -licui18n -licuuc -licudata  -lpthread
> -lm
> >
> >
> > could it be annoying for sqlite to be linked against pthread?
>
> Unless you compiled SQLite with SQLITE_THREADSAFE=0 then it has to use
> pthread.  In any event if that -lpthread came from icu-config then your ICU
> was deliberately compiled to use pthread so you can't avoid it.  (This is
> the whole point of pkg-config and icu-config - you don't have to know how
> they were compiled.)
>
> But the way libraries work means you do not need to be concerned.  The
> linker looks for symbols used by the program in each library.  If none of
> the symbols are found in a particular library then that library is ignored.
>  This means you could add the X windows libraries, the Python shared
> library
> and the ones for you favourite IM framework to the list and it won't make
> any difference on the final binary.
>
> Roger
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkshWmUACgkQmOOfHg372QSPEgCg0HqyVL971Hnn3MlPm2ap9rQf
> K3MAn2lj8GzIGwHKYdAs6HXTZPmaNo52
> =Sfj5
> -END PGP SIGNATURE-
> ___
> 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

Re: [sqlite] compiling Sqlite with ICU

[Roger Binns]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Sylvain Pointeau wrote:
> just one last thing:
> -lpthread -lm   -L/usr/local/lib -licui18n -licuuc -licudata  -lpthread -lm
> 
> 
> could it be annoying for sqlite to be linked against pthread?

Unless you compiled SQLite with SQLITE_THREADSAFE=0 then it has to use
pthread.  In any event if that -lpthread came from icu-config then your ICU
was deliberately compiled to use pthread so you can't avoid it.  (This is
the whole point of pkg-config and icu-config - you don't have to know how
they were compiled.)

But the way libraries work means you do not need to be concerned.  The
linker looks for symbols used by the program in each library.  If none of
the symbols are found in a particular library then that library is ignored.
 This means you could add the X windows libraries, the Python shared library
and the ones for you favourite IM framework to the list and it won't make
any difference on the final binary.

Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkshWmUACgkQmOOfHg372QSPEgCg0HqyVL971Hnn3MlPm2ap9rQf
K3MAn2lj8GzIGwHKYdAs6HXTZPmaNo52
=Sfj5
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] compiling Sqlite with ICU

[Sylvain Pointeau]

super thank you! :-D

just one last thing:
-lpthread -lm   -L/usr/local/lib -licui18n -licuuc -licudata  -lpthread -lm


could it be annoying for sqlite to be linked against pthread?

Many thanks,
Sylvain

On Thu, Dec 10, 2009 at 7:45 PM, Roger Binns  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Sylvain Pointeau wrote:
> > seems I found:
> >
> > ./configure CFLAGS="-DSQLITE_ENABLE_ICU" LDFLAGS="-L/usr/local/lib"
> > LIBS="-licudata -licui18n -licuio -licule -liculx -licutu -licuuc"
> >
> > is there any way to not list all the icu libs?
>
> Use icu-config.
>
> ./configure CFLAGS="-DSQLITE_ENABLE_ICU `icu-config --cppflags`"
> LDFLAGS="`icu-config --ldflags`"
>
> Roger
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkshQdsACgkQmOOfHg372QRF1wCfXLYH6fA7IpQ0dlxSq2hEImw0
> Q+AAniTKzfM3qx9Jm9d8TnZUAJHylJIP
> =nSJM
> -END PGP SIGNATURE-
> ___
> 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

Re: [sqlite] compiling Sqlite with ICU

[Roger Binns]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Sylvain Pointeau wrote:
> seems I found:
> 
> ./configure CFLAGS="-DSQLITE_ENABLE_ICU" LDFLAGS="-L/usr/local/lib"
> LIBS="-licudata -licui18n -licuio -licule -liculx -licutu -licuuc"
> 
> is there any way to not list all the icu libs?

Use icu-config.

./configure CFLAGS="-DSQLITE_ENABLE_ICU `icu-config --cppflags`"
LDFLAGS="`icu-config --ldflags`"

Roger
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkshQdsACgkQmOOfHg372QRF1wCfXLYH6fA7IpQ0dlxSq2hEImw0
Q+AAniTKzfM3qx9Jm9d8TnZUAJHylJIP
=nSJM
-END PGP SIGNATURE-
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] compiling Sqlite with ICU

[Sylvain Pointeau]

seems I found:

./configure CFLAGS="-DSQLITE_ENABLE_ICU" LDFLAGS="-L/usr/local/lib"
LIBS="-licudata -licui18n -licuio -licule -liculx -licutu -licuuc"

is there any way to not list all the icu libs?

Best regards,
Sylvain

On Thu, Dec 10, 2009 at 4:09 PM, Sylvain Pointeau <
sylvain.point...@gmail.com> wrote:

> ./configure CFLAGS="-DSQLITE_ENABLE_ICU
>
> but after I have a linker problem:
>
> /bin/sh ./libtool --tag=CC --mode=link gcc -DSQLITE_THREADSAFE=1
>  -DSQLITE_ENABLE_ICU -I/usr/local/include  -L/usr/local/lib -o
> libsqlite3.la -rpath /usr/local/lib -no-undefined -version-info 8:6:8
> sqlite3.lo
> gcc -dynamiclib  -o .libs/libsqlite3.0.8.6.dylib  .libs/sqlite3.o
>  -L/usr/local/lib  -install_name  /usr/local/lib/libsqlite3.0.dylib
> -compatibility_version 9 -current_version 9.6
> Undefined symbols:
>   "_u_strToLower_4_2", referenced from:
>   _icuCaseFunc16 in sqlite3.o
>   "_u_strToUpper_4_2", referenced from:
>   _icuCaseFunc16 in sqlite3.o
>   "_u_errorName_4_2", referenced from:
>   _icuFunctionError in sqlite3.o
>   "_utf8_nextCharSafeBody_4_2", referenced from:
>   _icuLikeFunc in sqlite3.o
>   "_ucol_strcoll_4_2", referenced from:
>   _icuCollationColl in sqlite3.o
>   "_u_foldCase_4_2", referenced from:
>   _icuLikeCompare in sqlite3.o
>   _icuLikeCompare in sqlite3.o
>   "_utf8_countTrailBytes_4_2", referenced from:
>   _icuLikeCompare in sqlite3.o
>   _icuLikeCompare in sqlite3.o
>   _icuLikeCompare in sqlite3.o
>   _icuLikeCompare in sqlite3.o
>   _icuLikeCompare in sqlite3.o
>   "_ucol_close_4_2", referenced from:
>
>
> On Thu, Dec 10, 2009 at 3:55 PM, Sylvain Pointeau <
> sylvain.point...@gmail.com> wrote:
>
>> ... I don't have this line in my Makefile.in ...
>> Are you sure there is not an option to put in the "configure" command?
>>
>> Best regards,
>> Sylvain
>>
>>
>> On Thu, Dec 10, 2009 at 3:44 PM, Alexey Pechnikov > > wrote:
>>
>>> Hello!
>>>
>>> On Thursday 10 December 2009 17:40:24 Sylvain Pointeau wrote:
>>> > Thank you very much.
>>> > How should I do exactly with configure to enable this define ?
>>>
>>> You can simple replace the string
>>> TCC += -D_HAVE_SQLITE_CONFIG_H
>>> to
>>> TCC += -D_HAVE_SQLITE_CONFIG_H -DSQLITE_ENABLE_ICU
>>> in the Makefine.in
>>>
>>> Best regards, Alexey Pechnikov.
>>> http://pechnikov.tel/
>>> ___
>>> 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

Re: [sqlite] compiling Sqlite with ICU

[Sylvain Pointeau]

./configure CFLAGS="-DSQLITE_ENABLE_ICU

but after I have a linker problem:

/bin/sh ./libtool --tag=CC --mode=link gcc -DSQLITE_THREADSAFE=1
 -DSQLITE_ENABLE_ICU -I/usr/local/include  -L/usr/local/lib -o
libsqlite3.la-rpath /usr/local/lib -no-undefined -version-info 8:6:8
sqlite3.lo
gcc -dynamiclib  -o .libs/libsqlite3.0.8.6.dylib  .libs/sqlite3.o
 -L/usr/local/lib  -install_name  /usr/local/lib/libsqlite3.0.dylib
-compatibility_version 9 -current_version 9.6
Undefined symbols:
  "_u_strToLower_4_2", referenced from:
  _icuCaseFunc16 in sqlite3.o
  "_u_strToUpper_4_2", referenced from:
  _icuCaseFunc16 in sqlite3.o
  "_u_errorName_4_2", referenced from:
  _icuFunctionError in sqlite3.o
  "_utf8_nextCharSafeBody_4_2", referenced from:
  _icuLikeFunc in sqlite3.o
  "_ucol_strcoll_4_2", referenced from:
  _icuCollationColl in sqlite3.o
  "_u_foldCase_4_2", referenced from:
  _icuLikeCompare in sqlite3.o
  _icuLikeCompare in sqlite3.o
  "_utf8_countTrailBytes_4_2", referenced from:
  _icuLikeCompare in sqlite3.o
  _icuLikeCompare in sqlite3.o
  _icuLikeCompare in sqlite3.o
  _icuLikeCompare in sqlite3.o
  _icuLikeCompare in sqlite3.o
  "_ucol_close_4_2", referenced from:


On Thu, Dec 10, 2009 at 3:55 PM, Sylvain Pointeau <
sylvain.point...@gmail.com> wrote:

> ... I don't have this line in my Makefile.in ...
> Are you sure there is not an option to put in the "configure" command?
>
> Best regards,
> Sylvain
>
>
> On Thu, Dec 10, 2009 at 3:44 PM, Alexey Pechnikov 
> wrote:
>
>> Hello!
>>
>> On Thursday 10 December 2009 17:40:24 Sylvain Pointeau wrote:
>> > Thank you very much.
>> > How should I do exactly with configure to enable this define ?
>>
>> You can simple replace the string
>> TCC += -D_HAVE_SQLITE_CONFIG_H
>> to
>> TCC += -D_HAVE_SQLITE_CONFIG_H -DSQLITE_ENABLE_ICU
>> in the Makefine.in
>>
>> Best regards, Alexey Pechnikov.
>> http://pechnikov.tel/
>> ___
>> 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

Re: [sqlite] compiling Sqlite with ICU

[Sylvain Pointeau]

... I don't have this line in my Makefile.in ...
Are you sure there is not an option to put in the "configure" command?

Best regards,
Sylvain

On Thu, Dec 10, 2009 at 3:44 PM, Alexey Pechnikov wrote:

> Hello!
>
> On Thursday 10 December 2009 17:40:24 Sylvain Pointeau wrote:
> > Thank you very much.
> > How should I do exactly with configure to enable this define ?
>
> You can simple replace the string
> TCC += -D_HAVE_SQLITE_CONFIG_H
> to
> TCC += -D_HAVE_SQLITE_CONFIG_H -DSQLITE_ENABLE_ICU
> in the Makefine.in
>
> Best regards, Alexey Pechnikov.
> http://pechnikov.tel/
> ___
> 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

Re: [sqlite] compiling Sqlite with ICU

[Alexey Pechnikov]

Hello!

On Thursday 10 December 2009 17:40:24 Sylvain Pointeau wrote:
> Thank you very much.
> How should I do exactly with configure to enable this define ?

You can simple replace the string
TCC += -D_HAVE_SQLITE_CONFIG_H
to
TCC += -D_HAVE_SQLITE_CONFIG_H -DSQLITE_ENABLE_ICU
in the Makefine.in

Best regards, Alexey Pechnikov.
http://pechnikov.tel/
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] compiling Sqlite with ICU

[Sylvain Pointeau]

Hi,

Thank you very much.
How should I do exactly with configure to enable this define ?

Cheers,
Sylvain

On Thu, Dec 10, 2009 at 11:31 AM, Simon Davies <
simon.james.dav...@googlemail.com> wrote:

> 2009/12/10 Sylvain Pointeau :
> > Hi,
> >
> > I would like to use ICU with sqlite, I am on mac os x 10.6.2
> > How should I do? I installed ICU but sqlite3 seems to not check ICU when
> > compiling.
> > I would like to use ICU via the sqlite shell.
> >
> > Please could someone explain me how to use ICU with sqlite3 ?
>
> Have you found this compilation option?
>
> http://www.sqlite.org/compile.html#enable_icu
>
> >
> > Cheers,
> > Sylvain
>
> Regards,
> Simon
> ___
> 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

Re: [sqlite] compiling Sqlite with ICU

[Simon Davies]

2009/12/10 Sylvain Pointeau :
> Hi,
>
> I would like to use ICU with sqlite, I am on mac os x 10.6.2
> How should I do? I installed ICU but sqlite3 seems to not check ICU when
> compiling.
> I would like to use ICU via the sqlite shell.
>
> Please could someone explain me how to use ICU with sqlite3 ?

Have you found this compilation option?

http://www.sqlite.org/compile.html#enable_icu

>
> Cheers,
> Sylvain

Regards,
Simon
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] compiling Sqlite with ICU

[Sylvain Pointeau]

Hi,

I would like to use ICU with sqlite, I am on mac os x 10.6.2
How should I do? I installed ICU but sqlite3 seems to not check ICU when
compiling.
I would like to use ICU via the sqlite shell.

Please could someone explain me how to use ICU with sqlite3 ?

Cheers,
Sylvain
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Compiling SQLite on Windows from the basic sources

[Eli]

The preferred and recommended way of compiling SQLite on Windows is using the
single .C "amalgamation" file.

However, this isn't a suitable method when I want to tinker with the source code
of SQLite and compile it to see the effects. The single .C file isn't convenient
for development.

I can't find anywhere what is needed to compile SQLite on Windows from the basic
tarball (where all the C & H files are separate and not pre-processed). Has
anyone set up a SQLite development environment on Windows and can share which
tools are needed?

P.S. One example is the Lemon parser generator which should be probably compiled
separately and then used to help assembling SQLite.


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

[sqlite] Compiling SQLite with custom readline

[Alberto Simões]

Hello

I am trying to find out why my SQLite does not accept non ascii characters.
So, I compiled readline 6.0 and tried to compile sqlite with it.
As you might imagine at first SQLite detects the system (MAC OS) readline
library.

To use a custom readline I noticed in the configure script:
  --with-readline-lib specify readline library
  --with-readline-inc specify readline include paths

But I found out these flags not working as one usually expect on a configure
script.
I was expecting something like:

  --with-readline-lib=/opt/local/lib
--with-readline-inc=/opt/local/include/readline

but what the configure script was expecting was something like

  --with-readline-lib="-L/opt/local/lib -lreadline"
--with-readline-inc="-I/opt/local/include/readline"

(well, at least it compiled this way)

Therefore, this mail is a suggestion of making that two documentation line
clearer, probably with an example of what is expected.

Oh, by the way, the non-ascii characters are now recognized :)

Cheers
Alberto
-- 
Alberto Simões
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] Compiling sqlite using chars unsigned by default

[Axel Mammes]

Great! Thanks.

On May 8, 2009, at 3:34 PM, Axel Mammes wrote:

> Hi, I am using the ARM RVDS 2.0.1 compiler to try to get SQLite on a
> VeriFone Vx570 point of sale terminal running VerixV operating
> system. I am
> still working on getting it to work, but before I continue I need to
> know if
> the fact that chars are unsigned by default will break sqlite build.


It should work fine.

D. Richard Hipp
d...@hwaci.com
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling sqlite using chars unsigned by default

[D. Richard Hipp]

On May 8, 2009, at 3:34 PM, Axel Mammes wrote:

> Hi, I am using the ARM RVDS 2.0.1 compiler to try to get SQLite on a
> VeriFone Vx570 point of sale terminal running VerixV operating  
> system. I am
> still working on getting it to work, but before I continue I need to  
> know if
> the fact that chars are unsigned by default will break sqlite build.


It should work fine.

D. Richard Hipp
d...@hwaci.com



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

[sqlite] Compiling sqlite using chars unsigned by default

[Axel Mammes]

Hi, I am using the ARM RVDS 2.0.1 compiler to try to get SQLite on a
VeriFone Vx570 point of sale terminal running VerixV operating system. I am
still working on getting it to work, but before I continue I need to know if
the fact that chars are unsigned by default will break sqlite build.

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

[sqlite] compiling sqlite-3.4.0: undefined reference to `dlclose'

[Makavy, Erez (Erez)]

Hi,
 
The problem:
==
When cross-compiling sqlite-3.4.0, I encounter this linkage error:
 
./.libs/libsqlite3.so: undefined reference to `dlclose'
./.libs/libsqlite3.so: undefined reference to `dlopen'
./.libs/libsqlite3.so: undefined reference to `dlsym'
 
The solution:
===
I added in Makefile.in the "-ldl" at the end of the line.

sqlite3$(TEXE): $(TOP)/src/shell.c libsqlite3.la sqlite3.h
$(LTLINK) $(READLINE_FLAGS) $(LIBPTHREAD) \
-o $@ $(TOP)/src/shell.c libsqlite3.la \
$(LIBREADLINE) $(TLIBS) -ldl


It seems to fix the problem, but I'm sure this is not the appropriate
way.
 
The question:
==
Any idea what a propper solution would be?
 
 
More details:
=
I'm compiling on Linux, for target PPC.
 
The full compilation line (before the fix) is:

/home/lira/toolchain/gnu/3.4.4-wrlinux-1.2/x86-linux2/bin/powerpc-wrs-li
nux-gnu-powerpc-gpp-gcc
 -O3
 -mcpu=603e
 -mtune=603e
 -mfull-toc
 -mcall-linux
 -fomit-frame-pointer
 -funroll-loops
 -DOS_UNIX=1
 -DHAVE_USLEEP=1
 -I.
 -I./src
 -I/export/target/root/usr/local/include
 -DHAVE_READLINE=0
 -o .libs/sqlite3
 ./src/shell.c
 -L/export/target/root/usr/local/lib
 -L/home/cfi/export_for_linkage/target/root/lib
 -L/home/cfi/export_for_linkage/target/root/usr/lib
 -L/home/cfi/export_for_linkage/target/root/usr/local/lib
 ./.libs/libsqlite3.so
 -lpthread
 -Wl,--rpath
 -Wl,/usr/local/lib

My configure command is:
--
./configure
'--build=i686-linux' \
--host=powerpc-wrs-linux-gnu \
--prefix=/usr/local \
'--disable-tcl' \
'--disable-debug' \
'--with-gnu-ld' \
'--enable-threadsafe' \
'--enable-releasemode' \
--disable-static

 
 
Thanks,
Erez

Re: [sqlite] Compiling SQLite under Mac OS (was: unsupported file format)

[Alberto Simões]

On 5/12/07, Alberto Simões <[EMAIL PROTECTED]> wrote:

I am compiling *manually* sqlite3 in my Mac OS.

Configured without tcl, and with prefix /usr/local.
  (--disable-tcl --prefix=/usr/local)

I get this while compiling:

...
gcc -L/sw/lib -I/sw/include -g -O2 -I. -I./src -DNDEBUG -DTHREADSAFE=0
-DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -c
./src/alter.c  -fno-common -DPIC -o .libs/alter.o
In file included from ./src/alter.c:17:
./src/sqliteInt.h:516: error: parse error before 'sqlite3_vtab'
./src/sqliteInt.h:516: warning: no semicolon at end of struct or union
./src/sqliteInt.h:528: error: parse error before '}' token
...


Solved
Removed those -L and -I for fink libraries.
Thanks
Alberto


--
Alberto Simões

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] Compiling SQLite under Mac OS (was: unsupported file format)

[Alberto Simões]

Ok, I didn't explain correctly. This time I am not using fink :)

Argh. Not being native english speaker sometimes sucks. Let start again.

I am compiling *manually* sqlite3 in my Mac OS.

Configured without tcl, and with prefix /usr/local.
 (--disable-tcl --prefix=/usr/local)

I get this while compiling:

...
gcc -L/sw/lib -I/sw/include -g -O2 -I. -I./src -DNDEBUG -DTHREADSAFE=0
-DSQLITE_THREAD_OVERRIDE_LOCK=-1 -DSQLITE_OMIT_LOAD_EXTENSION=1 -c
./src/alter.c  -fno-common -DPIC -o .libs/alter.o
In file included from ./src/alter.c:17:
./src/sqliteInt.h:516: error: parse error before 'sqlite3_vtab'
./src/sqliteInt.h:516: warning: no semicolon at end of struct or union
./src/sqliteInt.h:528: error: parse error before '}' token
...

Hints, please?
Thanks
Alberto
--
Alberto Simões

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] Compiling SQLite under Mac OS (was: unsupported file format)

[Alberto Simões]

On 5/12/07, P Kishor <[EMAIL PROTECTED]> wrote:

On 5/12/07, Alberto Simões <[EMAIL PROTECTED]> wrote:
> On 5/11/07, P Kishor <[EMAIL PROTECTED]> wrote:
>
> > Just download the latest source code and compile a new sqlite3 with
> > it. All will be well.
>
> I am trying to compile SQLite under Mac OS. Normally I use fink but it
> includes an old version of SQLite.

Don't use fink. I used fink once about a few years ago, and promptly
deleted anything to do with it because it (as well as darwinports) was
more trouble than worth it. SQLite (and many other software packages)
compiles on my Mac (10.4.x) with nary a hiccup.


Ok, I didn't explain correctly. This time I am not using fink :)


> Configured without tcl, and with prefix /usr/local.
> I get this while compiling:
>
>  gcc -L/sw/lib -I/sw/include -g -O2 -I. -I./src -DNDEBUG
> -DTHREADSAFE=0 -DSQLITE_THREAD_OVERRIDE_LOCK=-1
> -DSQLITE_OMIT_LOAD_EXTENSION=1 -c ./src/alter.c  -fno-common -DPIC -o
> .libs/alter.o
> In file included from ./src/alter.c:17:
> ./src/sqliteInt.h:516: error: parse error before 'sqlite3_vtab'
> ./src/sqliteInt.h:516: warning: no semicolon at end of struct or union
> ./src/sqliteInt.h:528: error: parse error before '}' token
> ...
>
>
> Hints, please?
> Thanks
> Alberto

--
Alberto Simões

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] Compiling SQLite under Mac OS (was: unsupported file format)

[P Kishor]

On 5/12/07, Alberto Simões <[EMAIL PROTECTED]> wrote:

On 5/11/07, P Kishor <[EMAIL PROTECTED]> wrote:

> Just download the latest source code and compile a new sqlite3 with
> it. All will be well.

I am trying to compile SQLite under Mac OS. Normally I use fink but it
includes an old version of SQLite.


Don't use fink. I used fink once about a few years ago, and promptly
deleted anything to do with it because it (as well as darwinports) was
more trouble than worth it. SQLite (and many other software packages)
compiles on my Mac (10.4.x) with nary a hiccup.

Do as I suggested above and all will be well.



Configured without tcl, and with prefix /usr/local.
I get this while compiling:

 gcc -L/sw/lib -I/sw/include -g -O2 -I. -I./src -DNDEBUG
-DTHREADSAFE=0 -DSQLITE_THREAD_OVERRIDE_LOCK=-1
-DSQLITE_OMIT_LOAD_EXTENSION=1 -c ./src/alter.c  -fno-common -DPIC -o
.libs/alter.o
In file included from ./src/alter.c:17:
./src/sqliteInt.h:516: error: parse error before 'sqlite3_vtab'
./src/sqliteInt.h:516: warning: no semicolon at end of struct or union
./src/sqliteInt.h:528: error: parse error before '}' token
...


Hints, please?
Thanks
Alberto

--
Alberto Simões

-
To unsubscribe, send email to [EMAIL PROTECTED]
-





--
Puneet Kishor http://punkish.eidesis.org/
Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/
Open Source Geospatial Foundation http://www.osgeo.org/education/
-
collaborate, communicate, compete
=

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

[sqlite] Compiling SQLite under Mac OS (was: unsupported file format)

[Alberto Simões]

On 5/11/07, P Kishor <[EMAIL PROTECTED]> wrote:


Just download the latest source code and compile a new sqlite3 with
it. All will be well.


I am trying to compile SQLite under Mac OS. Normally I use fink but it
includes an old version of SQLite.

Configured without tcl, and with prefix /usr/local.
I get this while compiling:

gcc -L/sw/lib -I/sw/include -g -O2 -I. -I./src -DNDEBUG
-DTHREADSAFE=0 -DSQLITE_THREAD_OVERRIDE_LOCK=-1
-DSQLITE_OMIT_LOAD_EXTENSION=1 -c ./src/alter.c  -fno-common -DPIC -o
.libs/alter.o
In file included from ./src/alter.c:17:
./src/sqliteInt.h:516: error: parse error before 'sqlite3_vtab'
./src/sqliteInt.h:516: warning: no semicolon at end of struct or union
./src/sqliteInt.h:528: error: parse error before '}' token
...


Hints, please?
Thanks
Alberto

--
Alberto Simões

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] Compiling Sqlite with Openwatcom

[Arjen Markus]

[EMAIL PROTECTED] wrote:


Hi Arjen

Unfortunately I am still using f77 not f90...

 


Hello Victor,

any specific reason? There are lots of (free) Fortran 90 compilers around,
and unless I am mistaken the Openwatcom compiler supports Fortran 90
(after all, the standard is more than 20 years old).

The good thing is that any FORTRAN 77 that complies to that standard
is also a valid Fortran 90 program, so if you decide to move to Fortran 90
you can do the transition in small steps.

The sample code by Danial is a good attempt to do it in FORTRAN 77,
but it is rather involved due to the limitations of that standard (computers
30 years ago were very different beasts).

Regards,

Arjen

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] Compiling Sqlite with Openwatcom

[victor . camus]

Hi Arjen

Unfortunately I am still using f77 not f90...

Selon Arjen Markus <[EMAIL PROTECTED]>:

> [EMAIL PROTECTED] wrote:
>
> >Hi All,
> >
> >I wonder whether anyone has already compiled Sqlite with Openwatcom (a free
> >compiler suite available at www.openwatcom.org including a C/C++/Fortran
> >compiler).
> >
> >Since when I tried, I got the following compiling error on line 95 of the
> file
> >sqlite3ext.h: invalid declarator i.e. corresponding to the line
> >  void  (*interrupt)(sqlite3*);
> >
> >This is the first step to generate a library that I will use to access
> Sqlite
> >from Fortran following the instructions given by Danial at
> >http://danial.org/sqlite/fortran/(my next step)
> >
> >
> >
> Hello Victor,
>
> I know almost nothing about the Open Watcom compiler, but if you are
> interested in using Sqlite from Fortran, see my flibs project on
> SourceForge:
> http://flibs.sf.net - I created the interface library you will find
> there (insufficient
> documentation, I am afraid, and some loose ends) after being inspired by
> that same example.
>
> Regards,
>
> Arjen
>
> -
> To unsubscribe, send email to [EMAIL PROTECTED]
> -
>
>



-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] Compiling Sqlite with Openwatcom

[Arjen Markus]

[EMAIL PROTECTED] wrote:


Hi All,

I wonder whether anyone has already compiled Sqlite with Openwatcom (a free
compiler suite available at www.openwatcom.org including a C/C++/Fortran
compiler).

Since when I tried, I got the following compiling error on line 95 of the file
sqlite3ext.h: invalid declarator i.e. corresponding to the line
 void  (*interrupt)(sqlite3*);

This is the first step to generate a library that I will use to access Sqlite
from Fortran following the instructions given by Danial at
http://danial.org/sqlite/fortran/(my next step)

 


Hello Victor,

I know almost nothing about the Open Watcom compiler, but if you are
interested in using Sqlite from Fortran, see my flibs project on 
SourceForge:
http://flibs.sf.net - I created the interface library you will find 
there (insufficient

documentation, I am afraid, and some loose ends) after being inspired by
that same example.

Regards,

Arjen

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

[sqlite] Compiling Sqlite with Openwatcom

[victor . camus]

Hi All,

I wonder whether anyone has already compiled Sqlite with Openwatcom (a free
compiler suite available at www.openwatcom.org including a C/C++/Fortran
compiler).

Since when I tried, I got the following compiling error on line 95 of the file
sqlite3ext.h: invalid declarator i.e. corresponding to the line
  void  (*interrupt)(sqlite3*);

This is the first step to generate a library that I will use to access Sqlite
from Fortran following the instructions given by Danial at
http://danial.org/sqlite/fortran/(my next step)

Any help is welcome

Victor

-
To unsubscribe, send email to [EMAIL PROTECTED]
-

Re: [sqlite] Compiling SQLite 3 on Windows

[drh]

Shawn Walker <[EMAIL PROTECTED]> wrote:
> Do I need to compile SQLite 3 source code with "-DNDEBUG" for the no debug 
> version?  I see "NDEBUG" in the source, but wasn't sure.
> 

No.
--
D. Richard Hipp   <[EMAIL PROTECTED]>

[sqlite] Compiling SQLite 3 on Windows

[Shawn Walker]

Do I need to compile SQLite 3 source code with "-DNDEBUG" for the no debug 
version?  I see "NDEBUG" in the source, but wasn't sure.


Thanks,
Shawn

Re: [sqlite] compiling sqlite

[Nuno Lucas]

On 6/21/06, Robin Cook <[EMAIL PROTECTED]> wrote:

Tried to compile 2.8.16 but got the below errors.  Any suggestions?
Thanks.

C:\Windows CE Tools\wce211\PDT7200\Samples\sqlite\btree_rb.c(314) :
warning C4013: 'printf' undefined; assuming extern returning int


This is unused debug code. You can #ifdef the whole function.


C:\Windows CE Tools\wce211\PDT7200\Samples\sqlite\vdbe.c(389) : warning
C4013: 'getc' undefined; assuming extern returning int
C:\Windows CE Tools\wce211\PDT7200\Samples\sqlite\vdbe.c(395) : warning
C4013: 'ungetc' undefined; assuming extern returning int


It seems sqlite is using it's own fgets implementation for the vdbe
now, but using C functions not found in the (very poor) 2.11 C
runtime.
If I remember correctly, you can use fgetc instead of getc, but don't
think there is an ungetc replacement, so you'll need to reimplement
the function.


C:\Windows CE Tools\wce211\PDT7200\Samples\sqlite\vdbe.c(4140) : warning
C4013: 'fopen' undefined; assuming extern returning int


You'll have to replace this with wfopen (WinCE 2.11 only implements
the unicode variant of this functions). Look at wStrDup() in the os.c
file for how to transform the path to Unicode.


C:\Windows CE Tools\wce211\PDT7200\Samples\sqlite\vdbe.c(4140) : warning
C4047: '=' : 'void *' differs in levels of indirection from 'int '


This are the "normal" sqlite warnings ;-)


I don't have Windows to test this, but you should now know what to do.

Best regards,
~Nuno Lucas

Re: [sqlite] compiling sqlite

[Robin Cook]

Tried to compile 2.8.16 but got the below errors.  Any suggestions?
Thanks.

C:\Windows CE Tools\wce211\PDT7200\Samples\sqlite\btree_rb.c(314) :
warning C4013: 'printf' undefined; assuming extern returning int
C:\Windows CE Tools\wce211\PDT7200\Samples\sqlite\vdbe.c(389) : warning
C4013: 'getc' undefined; assuming extern returning int
C:\Windows CE Tools\wce211\PDT7200\Samples\sqlite\vdbe.c(395) : warning
C4013: 'ungetc' undefined; assuming extern returning int
C:\Windows CE Tools\wce211\PDT7200\Samples\sqlite\vdbe.c(4140) : warning
C4013: 'fopen' undefined; assuming extern returning int
C:\Windows CE Tools\wce211\PDT7200\Samples\sqlite\vdbe.c(4140) : warning
C4047: '=' : 'void *' differs in levels of indirection from 'int '

Linking...

vdbe.obj : error LNK2001: unresolved external symbol _fopen
vdbe.obj : error LNK2001: unresolved external symbol _ungetc
vdbe.obj : error LNK2001: unresolved external symbol _getc
X86Rel/sqlite.dll : fatal error LNK1120: 3 unresolved externals


On Mon, 2006-06-19 at 10:22 +0100, Nuno Lucas wrote:
> On 6/19/06, Robin Cook <[EMAIL PROTECTED]> wrote:
> > Is it possible to compile sqlite on embedded visual c 3.0 for wince 2.11
> > without MFC and TCL/TK on a Symbol PDT7242 barcode scanner.
> 
> You should be able to use the 2.8.16 source in the sqlite-wince.sf.net
> site (maybe with one or other tweak as it's been a while since I last
> tested it on 2.11).
> 
> You will not have file locking support, but I guess you will not need it.
> 
> As for Tcl/Tk, you are on your own, sorry.
> 
> > I have tried with the already preprocessed windows source but keep
> > getting error with missing header files like assert.h etc.
> 
> The port includes dummy assert.h and time.h files exactly because of this.
> 
> > I am unable to use the dll as it requires msvcrt which is not available
> > on it.
> 
> You can't use a windows DLL on CE, even if msvcrt was available. You
> will need to compile your own.
> 
> Best regards,
> ~Nuno Lucas
> 
> > Thanks
> > Robin Cook
> 


signature.asc
Description: This is a digitally signed message part

Re: [sqlite] compiling sqlite

[Nuno Lucas]

On 6/19/06, Robin Cook <[EMAIL PROTECTED]> wrote:

Is it possible to compile sqlite on embedded visual c 3.0 for wince 2.11
without MFC and TCL/TK on a Symbol PDT7242 barcode scanner.


You should be able to use the 2.8.16 source in the sqlite-wince.sf.net
site (maybe with one or other tweak as it's been a while since I last
tested it on 2.11).

You will not have file locking support, but I guess you will not need it.

As for Tcl/Tk, you are on your own, sorry.


I have tried with the already preprocessed windows source but keep
getting error with missing header files like assert.h etc.


The port includes dummy assert.h and time.h files exactly because of this.


I am unable to use the dll as it requires msvcrt which is not available
on it.


You can't use a windows DLL on CE, even if msvcrt was available. You
will need to compile your own.

Best regards,
~Nuno Lucas


Thanks
Robin Cook

[sqlite] compiling sqlite

[Robin Cook]

Is it possible to compile sqlite on embedded visual c 3.0 for wince 2.11
without MFC and TCL/TK on a Symbol PDT7242 barcode scanner.

I have tried with the already preprocessed windows source but keep
getting error with missing header files like assert.h etc.

I am unable to use the dll as it requires msvcrt which is not available
on it.

Thanks
Robin Cook


signature.asc
Description: This is a digitally signed message part

Re: [sqlite] Compiling Sqlite JDBC driver (Compiler question)

[Christian Werner]

[EMAIL PROTECTED] wrote:
> 
> Christian,
> 
> I understand Windows is poor, but I do not fully understand the
> compilation process. The mkopc3.exe is actually created- so this itself
> cannot be the problem. Not having awk doesn't seem to be an issue for
> compiling the 3.2.1-based driver either (see 1).
> 
> Sorry, I'm confused :(

Andi,

from SQLite 3.2.1 to 3.3.5 some automagic in creating opcodes.h and parse.h
has changed significantly. The mkopc3.exe does on Windows what main.mk in
the SQLite source does by using the awk scripts mkopcode{c,h}.awk and
addopcodes.awk. The mkopc3 source in the latest javasqlite is not up to
date and not ready for 3.3.5 (but mkopc3 in the latest ODBC driver is). 
You have two options: setup your make of the Java wrapper to use sqlite.dll
or (as in my original tarballs) build SQLite as a link library and link it
directly into sqlite_jni.dll. The former is maybe easier to achieve, the
latter does not require to have sqlite.dll installed in the right place.

Hope that helps,
Christian

RE: [sqlite] Compiling Sqlite JDBC driver (Compiler question)

[andreas.goetz]

Christian,

I understand Windows is poor, but I do not fully understand the
compilation process. The mkopc3.exe is actually created- so this itself
cannot be the problem. Not having awk doesn't seem to be an issue for
compiling the 3.2.1-based driver either (see 1).

Sorry, I'm confused :(
Andi

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christian
Werner
Sent: Dienstag, 16. Mai 2006 09:04
To: sqlite-users@sqlite.org
Subject: Re: [sqlite] Compiling Sqlite JDBC driver (Compiler question)

[EMAIL PROTECTED] wrote:
> 
> After I've been able to overcome the initial compiler problem (missing

> library installation), I'm faced with a new one:
> 
> 1) Compiling JDBC wrapper for 3.2.1 works fine
> 
> 2) Compiling JDBC wrapper for 3.3.5 fails:
> 
> cl -Gs -EHsc -D_WIN32 -nologo -Zi -DOS_WIN=1 
> -D_CRT_SECURE_NO_DEPRECATE
> -DNDEBUG=1 -DSQLITE_OMIT_CURSOR=1 -DWIN32=1 -DTHREADSAFE=1 -DOS_WIN=1 
> -DSQLITE_S
> OUNDEX=1  -I. -I..\sqlite-3.3.5/src -D_DLL -c 
> ...\sqlite-3.3.5/src/alter.c alter.c
> ...\sqlite-3.3.5/src/alter.c(70) : error C2065: 'TK_SPACE' : 
> undeclared identifier
> 
> Regarding TK_SPACE, I've found that parse.y has changed between the 
> two version, where 3.3.5 version now omits these lines:
> 
> %nonassoc END_OF_FILE ILLEGAL SPACE UNCLOSED_STRING COMMENT FUNCTION
>   COLUMN AGG_FUNCTION.
> 
> I've not been able to figure out where or how TK_SPACE should be 
> generated for the parse.h

Please use the mkopc3.c source from the sqlite odbc driver instead.
It should deal with this issue (poor MSWindows development systems
weren't born with an awk :( another reason to switch to cygwin or
mingw). Anybody volunteering for creating the build environment of
javasqlite with the cygwin or mingw toolchain ?

Regards,
Christian


This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information.  If you have received it in 
error, please notify the sender immediately and delete the original.  Any other 
use of the email by you is prohibited.

Re: [sqlite] Compiling Sqlite JDBC driver (Compiler question)

[Christian Werner]

[EMAIL PROTECTED] wrote:
> 
> After I've been able to overcome the initial compiler problem (missing
> library installation), I'm faced with a new one:
> 
> 1) Compiling JDBC wrapper for 3.2.1 works fine
> 
> 2) Compiling JDBC wrapper for 3.3.5 fails:
> 
> cl -Gs -EHsc -D_WIN32 -nologo -Zi -DOS_WIN=1 -D_CRT_SECURE_NO_DEPRECATE
> -DNDEBUG=1 -DSQLITE_OMIT_CURSOR=1 -DWIN32=1 -DTHREADSAFE=1 -DOS_WIN=1
> -DSQLITE_S
> OUNDEX=1  -I. -I..\sqlite-3.3.5/src -D_DLL -c
> ...\sqlite-3.3.5/src/alter.c
> alter.c
> ...\sqlite-3.3.5/src/alter.c(70) : error C2065: 'TK_SPACE' : undeclared
> identifier
> 
> Regarding TK_SPACE, I've found that parse.y has changed between the two
> version, where 3.3.5 version now omits these lines:
> 
> %nonassoc END_OF_FILE ILLEGAL SPACE UNCLOSED_STRING COMMENT FUNCTION
>   COLUMN AGG_FUNCTION.
> 
> I've not been able to figure out where or how TK_SPACE should be
> generated for the parse.h

Please use the mkopc3.c source from the sqlite odbc driver instead.
It should deal with this issue (poor MSWindows development systems
weren't born with an awk :( another reason to switch to cygwin or
mingw). Anybody volunteering for creating the build environment of
javasqlite with the cygwin or mingw toolchain ?

Regards,
Christian

RE: [sqlite] Compiling Sqlite JDBC driver (Compiler question)

[andreas.goetz]

After I've been able to overcome the initial compiler problem (missing
library installation), I'm faced with a new one:

1) Compiling JDBC wrapper for 3.2.1 works fine

2) Compiling JDBC wrapper for 3.3.5 fails:

cl -Gs -EHsc -D_WIN32 -nologo -Zi -DOS_WIN=1 -D_CRT_SECURE_NO_DEPRECATE
-DNDEBUG=1 -DSQLITE_OMIT_CURSOR=1 -DWIN32=1 -DTHREADSAFE=1 -DOS_WIN=1
-DSQLITE_S
OUNDEX=1  -I. -I..\sqlite-3.3.5/src -D_DLL -c
..\sqlite-3.3.5/src/alter.c
alter.c
..\sqlite-3.3.5/src/alter.c(70) : error C2065: 'TK_SPACE' : undeclared
identifier


Regarding TK_SPACE, I've found that parse.y has changed between the two
version, where 3.3.5 version now omits these lines:

%nonassoc END_OF_FILE ILLEGAL SPACE UNCLOSED_STRING COMMENT FUNCTION
  COLUMN AGG_FUNCTION.

I've not been able to figure out where or how TK_SPACE should be
generated for the parse.h

Any ideas?

Thanks,
Andi

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Donnerstag, 11. Mai 2006 11:26
To: sqlite-users@sqlite.org
Subject: [sqlite] Compiling Sqlite JDBC driver (Compiler question)

Hello,

I hope this isn't too off-topic, really more a compiler question than
SQLITE.

I'm trying to compile Christian Werner's Sqlite JDBC driver under WinXP
using Platform SDK and VS2005. This process breaks with the follwing
error message:

Microsoft (R) Program Maintenance Utility Version 8.00.50727.42
Copyright (C) Microsoft Corporation.  All rights reserved.

cl -I. -Isqlite-3.3.5 -I"C:\Program Files\Microsoft Platform SDK\Include
\crt" -DHAVE_SQLITE3=1 -Gs -GX -D_WIN32 -nologo native/fixup.c cl :
Command line warning D9035 : option 'GX' has been deprecated and will be
re moved in a future release cl : Command line warning D9036 : use
'EHsc' instead of 'GX'
fixup.c
LINK : fatal error LNK1104: cannot open file 'LIBCMT.lib'
NMAKE : fatal error U1077: '.\cl.EXE' : return code '0x2'
Stop.

Problem is that LIBCMT.lib (included due to the -D_MT Switch?) that
doesn't exist in the SDK folders. The library only exists in the 64bit
subfolders (IA64, AM64).

Any ideas if the MT switch has been deprecated or where the library
should be found? Any better place to ask?

Thanks a lot,
Andreas


This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information.  If you have
received it in error, please notify the sender immediately and delete
the original.  Any other use of the email by you is prohibited.


This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information.  If you have received it in 
error, please notify the sender immediately and delete the original.  Any other 
use of the email by you is prohibited.

Re: [sqlite] Compiling Sqlite JDBC driver (Compiler question)

[Anders Persson]

I don't know if this helps but when i was building a static version for 
Windows
1. maked a static dll project and added all files but NOT precompiled 
WIndows stufff..

If i added use precompiled windowsfile it never compiled..

// Anders


[EMAIL PROTECTED] skrev:

Hello,

I hope this isn't too off-topic, really more a compiler question than
SQLITE.

I'm trying to compile Christian Werner's Sqlite JDBC driver under WinXP
using Platform SDK and VS2005. This process breaks with the follwing
error message:

Microsoft (R) Program Maintenance Utility Version 8.00.50727.42
Copyright (C) Microsoft Corporation.  All rights reserved.

cl -I. -Isqlite-3.3.5 -I"C:\Program Files\Microsoft Platform SDK\Include
\crt" -DHAVE_SQLITE3=1 -Gs -GX -D_WIN32 -nologo native/fixup.c cl :
Command line warning D9035 : option 'GX' has been deprecated and will be
re moved in a future release cl : Command line warning D9036 : use
'EHsc' instead of 'GX'
fixup.c
LINK : fatal error LNK1104: cannot open file 'LIBCMT.lib'
NMAKE : fatal error U1077: '.\cl.EXE' : return code '0x2'
Stop.

Problem is that LIBCMT.lib (included due to the -D_MT Switch?) that
doesn't exist in the SDK folders. The library only exists in the 64bit
subfolders (IA64, AM64).

Any ideas if the MT switch has been deprecated or where the library
should be found? Any better place to ask?

Thanks a lot,
Andreas


This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information.  If you have received it in 
error, please notify the sender immediately and delete the original.  Any other 
use of the email by you is prohibited.


  

[sqlite] Compiling Sqlite JDBC driver (Compiler question)

[andreas.goetz]

Hello,

I hope this isn't too off-topic, really more a compiler question than
SQLITE.

I'm trying to compile Christian Werner's Sqlite JDBC driver under WinXP
using Platform SDK and VS2005. This process breaks with the follwing
error message:

Microsoft (R) Program Maintenance Utility Version 8.00.50727.42
Copyright (C) Microsoft Corporation.  All rights reserved.

cl -I. -Isqlite-3.3.5 -I"C:\Program Files\Microsoft Platform SDK\Include
\crt" -DHAVE_SQLITE3=1 -Gs -GX -D_WIN32 -nologo native/fixup.c cl :
Command line warning D9035 : option 'GX' has been deprecated and will be
re moved in a future release cl : Command line warning D9036 : use
'EHsc' instead of 'GX'
fixup.c
LINK : fatal error LNK1104: cannot open file 'LIBCMT.lib'
NMAKE : fatal error U1077: '.\cl.EXE' : return code '0x2'
Stop.

Problem is that LIBCMT.lib (included due to the -D_MT Switch?) that
doesn't exist in the SDK folders. The library only exists in the 64bit
subfolders (IA64, AM64).

Any ideas if the MT switch has been deprecated or where the library
should be found? Any better place to ask?

Thanks a lot,
Andreas


This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information.  If you have received it in 
error, please notify the sender immediately and delete the original.  Any other 
use of the email by you is prohibited.

Re: [sqlite] Compiling SQLite and MAX_ATTACHED databases

[Dan Kennedy]

> #define MAX_ATTACHED 10
>  
> Is this a per-process limit, or a per-sqlite3 handle limit?

It's per-handle.

Also, if you haven't found it already, this page has some of 
the compilation options you can set:

http://www.sqlite.org/compile.html



__ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

Re: [sqlite] Compiling sqlite 3.0.8 on SuSE 9.2

[die-bru]

Hi,
the failure was sitting before the monitor ;-)

I've removed the unpacked sqlite folder and unpacked it again. Now the 
compilation of version 3 was successfully. 
My fault was to unpack and compile sqlite Version2 and then to unpack and 
compile Version3. In consequence that the folder for sqlite version 2 and 
version 3 is called both sqlite and I didn't remove the old one, I've got 
this strange error indication during compilation.

I thought the folders for sqlite version 2 and version 3 unpacked, shouldn`t 
have the same name. 

Regards 
Holger Brunck  



On Friday 12 November 2004 17:16, [EMAIL PROTECTED] wrote:
> Hi,
> the Makefile.linux-gcc renamed in Makefile produces the same error output.
> Now I've tried to install the rpm, but this results to another failure:
>
> rpm -i sqlite-3.0.8-1.i386.rpm
> error: Failed dependencies:
> libreadline.so.4 is needed by sqlite-3.0.8-1
>
> SuSE 9.2 has libreadline.so.5 installed. Did I have to downgrade to
> libreadline.so.4 ?
>
> Regards
> Holger Brunck
>
> On Friday 12 November 2004 01:12, [EMAIL PROTECTED] wrote:
> > Hi,
> > I have problems to compile sqlite version 3 on SuSE 9.2. The 2.8.15
> > Version compiled successfully.
> >
> > Configure seems to work fine but when I invoke make the compilation stops
> > with following error output:
> >
> > ./libtool --mode=compile gcc -g -O2 -DOS_UNIX=1 -DHAVE_USLEEP=1 -I.
> > -I./src -DNDEBUG -c ./src/build.c gcc -g -O2 -DOS_UNIX=1 -DHAVE_USLEEP=1
> > -I. -I./src -DNDEBUG -c ./src/build.c -fPIC -DPIC -o .libs/build.o
> > src/build.c: In function `sqlite3BeginTransaction':
> > src/build.c:2409: error: `TK_EXCLUSIVE' undeclared (first use in this
> > function)
> > src/build.c:2409: error: (Each undeclared identifier is reported only
> > once src/build.c:2409: error: for each function it appears in.)
> > make: *** [build.lo] Error 1
> >
> > Any help?
> >
> > Regards
> > Holger Brunck
> >
> >
> > Arcor-DSL: die echte Flatrate für alle Bandbreiten. Jetzt ohne
> > Einrichtungspreis einsteigen oder wechseln. Arcor-DSL ist in vielen
> > Anschlussgebieten verfügbar. http://www.arcor.de/home/redir.php/emf-dsl-1

Re: [sqlite] Compiling sqlite 3.0.8 on SuSE 9.2

[die-bru]

Hi,
the Makefile.linux-gcc renamed in Makefile produces the same error output. 
Now I've tried to install the rpm, but this results to another failure:

rpm -i sqlite-3.0.8-1.i386.rpm
error: Failed dependencies:
libreadline.so.4 is needed by sqlite-3.0.8-1

SuSE 9.2 has libreadline.so.5 installed. Did I have to downgrade to 
libreadline.so.4 ?

Regards 
Holger Brunck




On Friday 12 November 2004 01:12, [EMAIL PROTECTED] wrote:
> Hi,
> I have problems to compile sqlite version 3 on SuSE 9.2. The 2.8.15 Version
> compiled successfully.
>
> Configure seems to work fine but when I invoke make the compilation stops
> with following error output:
>
> ./libtool --mode=compile gcc -g -O2 -DOS_UNIX=1 -DHAVE_USLEEP=1 -I. -I./src
> -DNDEBUG -c ./src/build.c gcc -g -O2 -DOS_UNIX=1 -DHAVE_USLEEP=1 -I.
> -I./src -DNDEBUG -c ./src/build.c -fPIC -DPIC -o .libs/build.o
> src/build.c: In function `sqlite3BeginTransaction':
> src/build.c:2409: error: `TK_EXCLUSIVE' undeclared (first use in this
> function)
> src/build.c:2409: error: (Each undeclared identifier is reported only once
> src/build.c:2409: error: for each function it appears in.)
> make: *** [build.lo] Error 1
>
> Any help?
>
> Regards
> Holger Brunck
>
>
> Arcor-DSL: die echte Flatrate für alle Bandbreiten. Jetzt ohne
> Einrichtungspreis einsteigen oder wechseln. Arcor-DSL ist in vielen
> Anschlussgebieten verfügbar. http://www.arcor.de/home/redir.php/emf-dsl-1

Re: [sqlite] Compiling sqlite 3.0.8 on SuSE 9.2

[John Dean]

Hi Richard
May I suggest that you take a look at scons. Scons is much better than 
autotools and it doesn't suffer from any of the compatibility problems. 
Scons can be download from http://www.scons.org/

I would like to offer our services in writing a scons script for you. BTW 
scons is a Python application so you would need at least Python 2.3.x installed

At 13:53 12/11/2004, you wrote:
[EMAIL PROTECTED] wrote:
Hi,
I have problems to compile sqlite version 3 on SuSE 9.2. The 2.8.15 Version
compiled successfully.
Configure seems to work fine but when I invoke make the compilation stops 
with
following error output:
./libtool --mode=compile gcc -g -O2 -DOS_UNIX=1 -DHAVE_USLEEP=1 -I. -I./src
-DNDEBUG -c ./src/build.c gcc -g -O2 -DOS_UNIX=1 -DHAVE_USLEEP=1 -I. -I./src
-DNDEBUG -c ./src/build.c -fPIC -DPIC -o .libs/build.o
src/build.c: In function `sqlite3BeginTransaction':
src/build.c:2409: error: `TK_EXCLUSIVE' undeclared (first use in this
function)
src/build.c:2409: error: (Each undeclared identifier is reported only once
src/build.c:2409: error: for each function it appears in.)
make: *** [build.lo] Error 1
Any help?
The configure script is really hosed up because I do not understand
autoconf nor can I find anybody who does understand autoconf who is
willing to work on it.  If it does not work for you, I suggest making
a copy of the Makefile.linux-gcc into Makefile, manually editing the
header to set up parameters appropriately for your system, then typing
"make".
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565

---
Regards
John Dean,
co-author of Rekall,
the only alternative
to MS Access 

Re: [sqlite] Compiling sqlite 3.0.8 on SuSE 9.2

[D. Richard Hipp]

[EMAIL PROTECTED] wrote:
Hi,
I have problems to compile sqlite version 3 on SuSE 9.2. The 2.8.15 Version
compiled successfully.
Configure seems to work fine but when I invoke make the compilation stops with
following error output:
./libtool --mode=compile gcc -g -O2 -DOS_UNIX=1 -DHAVE_USLEEP=1 -I. -I./src
-DNDEBUG -c ./src/build.c gcc -g -O2 -DOS_UNIX=1 -DHAVE_USLEEP=1 -I. -I./src
-DNDEBUG -c ./src/build.c -fPIC -DPIC -o .libs/build.o
src/build.c: In function `sqlite3BeginTransaction':
src/build.c:2409: error: `TK_EXCLUSIVE' undeclared (first use in this
function)
src/build.c:2409: error: (Each undeclared identifier is reported only once
src/build.c:2409: error: for each function it appears in.)
make: *** [build.lo] Error 1
Any help?
The configure script is really hosed up because I do not understand
autoconf nor can I find anybody who does understand autoconf who is
willing to work on it.  If it does not work for you, I suggest making
a copy of the Makefile.linux-gcc into Makefile, manually editing the
header to set up parameters appropriately for your system, then typing
"make".
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565