subject:"\[sqlite\] compiling"

Re: [sqlite] Compiling on AIX OS

2020-02-26 Thread Domingo Alvarez Duarte


Hello and thank you for reply !

As I said it's an exercise to know the peculiarities of compiling on 
this platform and I'm exposing this experience here in hope it can help 
others and improve sqlite build system.


If what you mention is correct about requiring tcl 8.5 or newer then the 
configure procedure probably should check this and report the problem.


Cheers !

On 26/2/20 10:27, Shawn Wagner wrote:

I'm pretty sure the full build scripts require tcl 8.5 or newer. Maybe try
the -amalgamation or -autoconf versions?

On Wed, Feb 26, 2020 at 1:21 AM Domingo Alvarez Duarte 
wrote:


Hello !



$ uname -a
AIX minimal 1 7 00C63E504B00
$ tclsh
% puts $tcl_patchLevel
8.4.7
%


On 26/2/20 10:19, Shawn Wagner wrote:

puts $tcl_patchLevel

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


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

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

Re: [sqlite] Compiling on AIX OS

2020-02-26 Thread Shawn Wagner

I'm pretty sure the full build scripts require tcl 8.5 or newer. Maybe try
the -amalgamation or -autoconf versions?

On Wed, Feb 26, 2020 at 1:21 AM Domingo Alvarez Duarte 
wrote:

> Hello !
>
> 
>
> $ uname -a
> AIX minimal 1 7 00C63E504B00
> $ tclsh
> % puts $tcl_patchLevel
> 8.4.7
> %
> 
>
> On 26/2/20 10:19, Shawn Wagner wrote:
> > puts $tcl_patchLevel
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling on AIX OS

2020-02-26 Thread Domingo Alvarez Duarte


Hello !



$ uname -a
AIX minimal 1 7 00C63E504B00
$ tclsh
% puts $tcl_patchLevel
8.4.7
%


On 26/2/20 10:19, Shawn Wagner wrote:

puts $tcl_patchLevel

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

Re: [sqlite] Compiling on AIX OS

2020-02-26 Thread Shawn Wagner

What version of tcl do you have installed?

(At the tclsh prompt, do a `puts $tcl_patchLevel`)

On Wed, Feb 26, 2020 at 1:05 AM Domingo Alvarez Duarte 
wrote:

> Hello !
>
> Trying to compile https://sqlite.org/2020/sqlite-src-3310100.zip on AIX
> 7.1 operating system for exercise and to know the peculiarities of
> building software on this OS and I'm getting this error, somehow tclsh
> that is installed on this OS do not wrap/hide OS incompatibilities.
>
> 
>
> tclsh /home/mingo/dev/sqlite-src-3310100/tool/mkshellc.tcl >shell.c
> illegal access mode "rb"
>  while executing
> "open $topdir/src/shell.c.in rb"
>  invoked from within
> "set in [open $topdir/src/shell.c.in rb]"
>  (file "/home/mingo/dev/sqlite-src-3310100/tool/mkshellc.tcl" line 32)
> gmake: *** [Makefile:1079: shell.c] Error 1
>
> 
>
> Cheers !
>
> ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling on AIX OS

2020-02-26 Thread Domingo Alvarez Duarte

Going forward after fixing the access mode from "rb" to "r" we get this 
error (tclsh8.4):




tclsh /home/mingo/dev/sqlite-src-3310100/tool/mkshellc.tcl >shell.c
cp /home/mingo/dev/sqlite-src-3310100/ext/fts5/fts5parse.y .
rm -f fts5parse.h
./lemon  -S fts5parse.y
tclsh /home/mingo/dev/sqlite-src-3310100/ext/fts5/tool/mkfts5c.tcl
bad index "19-1": must be integer or end?-integer?
    while executing
"string range $date 0 [string last . $date]-1"
    (procedure "fts5_source_id" line 7)
    invoked from within
"fts5_source_id $::srcdir"
    (procedure "fts5c_printfile" line 7)
    invoked from within
"fts5c_printfile $f "
    ("foreach" body line 1)
    invoked from within
"foreach f $G(src) { fts5c_printfile $f }"
    (file 
"/home/mingo/dev/sqlite-src-3310100/ext/fts5/tool/mkfts5c.tcl" line 112)

gmake: *** [Makefile:1188: fts5.c] Error 1


On 26/2/20 10:05, Domingo Alvarez Duarte wrote:

Hello !

Trying to compile https://sqlite.org/2020/sqlite-src-3310100.zip on 
AIX 7.1 operating system for exercise and to know the peculiarities of 
building software on this OS and I'm getting this error, somehow tclsh 
that is installed on this OS do not wrap/hide OS incompatibilities.




tclsh /home/mingo/dev/sqlite-src-3310100/tool/mkshellc.tcl >shell.c
illegal access mode "rb"
    while executing
"open $topdir/src/shell.c.in rb"
    invoked from within
"set in [open $topdir/src/shell.c.in rb]"
    (file "/home/mingo/dev/sqlite-src-3310100/tool/mkshellc.tcl" line 32)
gmake: *** [Makefile:1079: shell.c] Error 1



Cheers !


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

[sqlite] Compiling on AIX OS

2020-02-26 Thread Domingo Alvarez Duarte


Hello !

Trying to compile https://sqlite.org/2020/sqlite-src-3310100.zip on AIX 
7.1 operating system for exercise and to know the peculiarities of 
building software on this OS and I'm getting this error, somehow tclsh 
that is installed on this OS do not wrap/hide OS incompatibilities.




tclsh /home/mingo/dev/sqlite-src-3310100/tool/mkshellc.tcl >shell.c
illegal access mode "rb"
    while executing
"open $topdir/src/shell.c.in rb"
    invoked from within
"set in [open $topdir/src/shell.c.in rb]"
    (file "/home/mingo/dev/sqlite-src-3310100/tool/mkshellc.tcl" line 32)
gmake: *** [Makefile:1079: shell.c] Error 1



Cheers !

___
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

2020-02-13 Thread 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

2020-02-13 Thread 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

2020-02-13 Thread 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?

2019-12-21 Thread 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 System.Data.SQLite and using it across VS versions...

2019-06-08 Thread Sam Carleton

So my system using SQLite consists of multiple executables. One is a VS2015
.Net 4.6.2 app, there are two more that are VS2008 C++ applications.

At the moment I am using the officially compiled version
of System.Data.SQLite for the VS2015 program, and compiling sqlite.dll for
the VS2008 C++ programs to my liking.

My current task is to consolidate things better with the ultimate goal
being to do away with the VS2008 C++ programs and move everything to
VS2015.  I am thinking that step one should be to get ALL the programs
using the EXACT same copy of SQLite.  So I have questions:

   1. Is it better for unmanaged code to use the  SQLite.Interop.dll or
   have the managed code use a sqlite.dll?
   2. Is there a way to compile System.Data.SQLite.2015 such that the
   SQLite.Interop dll can be used by the older VS2008 C++ Programs?  What
   about compiling SQLite by itself such that it can be used by unmanaged
   VS2008 code and by managed VS2015 code?


Compile question:

Looking at the sqlite-netFx-source-1.0.110.0 projects, there are lots and
lots of options, too many for me to get my head around, so I have questions
there, too:

   1. I assume I should be using the SQLite.NET.2012.MSBuild.sln, not
   the SQLite.NET.2012.sln, correct?
   2. I see three configurations: Release, ReleaseManagedOnly,
   ReleaseNativeOnly.  Which one should I be using?
   3. The reason for compiling the SQLite is I need to compile some
   optional features to the settings I need them, I assume I put that into
   the  SQLite.Interop.2015 project, correct?

Thanks for your help

Pax vobiscum,
Sam Carleton
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling / building SQLite to include regex

2017-12-21 Thread Keith Medcalf


Compile and load the regexp extension (ext/misc/regexp.c in the full source 
distribution or the commit tracker).  Or append the extension to SQLite3.c and 
load it, or also create a routine that does the initialization for you and 
aappend that to the SQLite3.c code as well, and use the SQLITE_EXTRA_INIT 
define so that the extra initialization routine is executed for each connection 
that is created.

In other words, you just define a function with the correct name and cause it 
to be linked and loaded, and then you will have a REGEXP function and operator.

---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a 
lot about anticipated traffic volume.


>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of Paul Hoffman
>Sent: Thursday, 21 December, 2017 10:57
>To: sqlite-users@mailinglists.sqlite.org
>Subject: [sqlite] Compiling / building SQLite to include regex
>
>Greetings. I understand that SQLite doesn't come natively with regex
>support, but that it can be added. My question is how to do so when I
>install. I'm building from source from
><http://www.sqlite.org/download.html>.
>Is there a simple recipe for "make REGEX work after installation"?
>___
>sqlite-users mailing list
>sqlite-users@mailinglists.sqlite.org
>http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users



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

Re: [sqlite] Compiling / building SQLite to include regex

2017-12-21 Thread jungle Boogie

On 21 December 2017 at 10:18, Richard Hipp  wrote:
> On 12/21/17, Paul Hoffman  wrote:
>> Greetings. I understand that SQLite doesn't come natively with regex
>> support, but that it can be added. My question is how to do so when I
>> install. I'm building from source from
>> .
>> Is there a simple recipe for "make REGEX work after installation"?
>
> There is a loadable REGEXP extension here:
> https://www.sqlite.org/src/artifact/a68d25c659bd2d89
>

And information to compile here:
https://www.sqlite.org/loadext.html

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

Re: [sqlite] Compiling / building SQLite to include regex

2017-12-21 Thread Richard Hipp

On 12/21/17, Paul Hoffman  wrote:
> Greetings. I understand that SQLite doesn't come natively with regex
> support, but that it can be added. My question is how to do so when I
> install. I'm building from source from
> .
> Is there a simple recipe for "make REGEX work after installation"?

There is a loadable REGEXP extension here:
https://www.sqlite.org/src/artifact/a68d25c659bd2d89

-- 
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 / building SQLite to include regex

2017-12-21 Thread Paul Hoffman

Greetings. I understand that SQLite doesn't come natively with regex
support, but that it can be added. My question is how to do so when I
install. I'm building from source from .
Is there a simple recipe for "make REGEX work after installation"?
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling on Xcode

2017-12-04 Thread Jens Alfke

> On Nov 24, 2017, at 10:14 AM, Lifepillar  wrote:
> 
> When building sqlite-amalgamation-321 using Xcode 9.1 in a newly
> created project, I get a few dozen warnings

Yup, and this is an FAQ. SQLite is very thoroughly tested but the developers do 
not use compiler warnings.

> To avoid missing potential problems in the rest of your code, I'd
> recommend suppressing the warnings only for the Release
> configuration and only for the specific target.

I recommend building SQLite as a separate static-library target, and linking 
the library into your app target. That way you can turn off warnings for SQLite 
without affecting your own code.

—Jens

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

Re: [sqlite] Compiling on Xcode

2017-11-25 Thread Lifepillar


>Hi, ALL,
>Right now my C Language option on the Xcode 5.1.1 is set to "GNU99".
>When using this option I am getting a lot of different warnings like:
>
>Value Conversion Issue
>Implicit conversion loses integer precision.
>
>I know its just a warning, but I prefer the code to be compiled clean.
>I would guess that I need a change the option to get a clean compile.
>
>Which one I should use?

Hi,
I am resurrecting this old thread, because I recently had a similar
issue and didn't find an answer in this list.

When building sqlite-amalgamation-321 using Xcode 9.1 in a newly
created project, I get a few dozen warnings, mostly about value
conversion issues as mentioned above, a few about ambiguous MIN/MAX
macro definitions, unreachable code, possible misuse of comma
operator, and one about a (not C99-compliant) over-length string.

Most warnings are easily seen to be harmless (e.g., unreachable code
depends on compile-time flags, and ambiguous macros likely depend on
merging multiple files into one—but the various macro definitions
are equivalent). Besides, I get the same warnings if I add suitable
-W flags to sqlite-autoconf-321's Makefile, which otherwise
builds cleanly. This gives me confidence that the warnings may
indeed be ignored—although I am a bit scared of ignoring “implicit
conversion loses integer precision” warnings: I'd like someone
familiar with the code to confirm that that is no cause of concern.

So, you may silence all the warnings by setting the following items
in the target's build settings:

Apple LLVM 9.0 - Warnings - All Languages
  - Implicit Conversion to 32 Bit Type: No
  - Suspicious Commas: No
  - Unreachable Code: No

Apple LLVM 9.0 - Custom Compiler Flags
  - Other Warning Flags: -Wno-ambiguous-macro -Wno-overlength-strings

To avoid missing potential problems in the rest of your code, I'd
recommend suppressing the warnings only for the Release
configuration and only for the specific target.

Hope this may be helpful to others as well,
Life.


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

Re: [sqlite] compiling for android

2017-09-11 Thread Christian Czech


Hi,

it guess it must be some special settings. We used sqlite quite some 
time now and the last build problem we got with ndk is quite long time ago.


Regards,
Christian

---
derago e. K., Gartenstr. 4, D-79807 Lottstetten, Amtsgericht Freiburg/Br. 
HRA621012, weitere Informationen unter http://www.derago.com/Impressum. Diese 
E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn 
Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese 
E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail 
ist nicht gestattet.

Am 11.09.2017 um 17:28 schrieb Dan Kennedy:

On 09/11/2017 05:20 AM, Mark Sibly wrote:

Hi,

I just encountered a problem trying to build the sqlite amalgamation
package for android with the latest NDK (v15.2.4203891) on windows 10.

The compiler couldn't find mmap, which was causing a ton of errors.

I solved it by sticking this at the top-ish of sqlite3.c

#if __ANDROID__
#include 
#endif


Thanks for reporting this. Which version are you trying to build?

Are you building with any special options - SQLITE_OMIT_WAL or similar?

When things are working right, sys/mman.h should be included if 
required by the amalgamation equivalent of this line:


  http://www.sqlite.org/src/artifact/489aa972ccc34?ln=99

Can you post the first couple of compiler errors?

Dan.

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


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

Re: [sqlite] compiling for android

2017-09-11 Thread Dan Kennedy


On 09/11/2017 05:20 AM, Mark Sibly wrote:

Hi,

I just encountered a problem trying to build the sqlite amalgamation
package for android with the latest NDK (v15.2.4203891) on windows 10.

The compiler couldn't find mmap, which was causing a ton of errors.

I solved it by sticking this at the top-ish of sqlite3.c

#if __ANDROID__
#include 
#endif


Thanks for reporting this. Which version are you trying to build?

Are you building with any special options - SQLITE_OMIT_WAL or similar?

When things are working right, sys/mman.h should be included if required 
by the amalgamation equivalent of this line:


  http://www.sqlite.org/src/artifact/489aa972ccc34?ln=99

Can you post the first couple of compiler errors?

Dan.

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

[sqlite] compiling for android

2017-09-11 Thread Mark Sibly

Hi,

I just encountered a problem trying to build the sqlite amalgamation
package for android with the latest NDK (v15.2.4203891) on windows 10.

The compiler couldn't find mmap, which was causing a ton of errors.

I solved it by sticking this at the top-ish of sqlite3.c

#if __ANDROID__
#include 
#endif

Bye!
Mark
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-26 Thread curmudgeon

Thanks for those explanations Keith and Richard. I always thought the <> were
the ones supplied by the language.



--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/Compiling-spellfix-for-sqlite3-tp70656p97122.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-25 Thread Richard Damon


On 8/25/17 2:15 PM, Keith Medcalf wrote:

When the included file is in " " then the file is expected to be located relative to the current directory.  If the 
included file is in < > then it is relative to one of the directories specified in the "include search path".  This 
search may or may not include the "current directory" but to have "current directory" included, you have to 
specify the directory location specifically to the compiler -- it does not automatically look in the current directory for files 
included with the < > syntax.
This is incorrect. The Standard doesn't even require the that Standard 
define includes even actually be 'C files', and the header files don't 
need to be in 'directory'


What the standard does say is that includes specified with <> look in a 
set of implementation defined places, and that includes with "" look in 
another set of implementation defined places, with the addition that if 
it doesn't find them there, it looks in the places defined for <>


Generally, and traditionally, the <> list of places is thought of as the 
'system' include path, and the "" list of places are the user include 
path, and it is fairly normal that the "" list includes the current 
directory.



--
Richard Damon

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

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-25 Thread Keith Medcalf


When the included file is in " " then the file is expected to be located 
relative to the current directory.  If the included file is in < > then it is 
relative to one of the directories specified in the "include search path".  
This search may or may not include the "current directory" but to have "current 
directory" included, you have to specify the directory location specifically to 
the compiler -- it does not automatically look in the current directory for 
files included with the < > syntax.

So for example, GCC sets several default search locations based on the location 
of the compiler executable itself (so it can find the headers included with the 
compiler).  It then "appends" the directories specified in the INCLUDE 
environment variable to that list.  Command line options (and compilers with 
GUI interfaces will have the same options somewhere) allow the specification of 
"prepends" and "appends" to that list of directories.  Most compilers work the 
same way.

There is also a "LIB search path" that works the same way for linking the 
object files and libraries together.  GCC has defaults set according to the 
location of the compiler executable, then appends the paths found in the LIB 
environment variable, and then has Command line (located in the GUI options for 
other compilers) that let you prepend and append additional paths to the list.

The include and lib paths work the same way for almost all compilers, though 
there are a few exceptions.  For example, there is an old Fortran compiler that 
looks specifically in the "F99INCLUDE" environment variable for included 
Fortran code (actually, anything that is not a .h file), and the "INCLUDE" 
environment variable only for .h files.  Most compilers, however, only use one 
set of "include" and "lib" paths and know how to search for the files 
specifically.

Because the INCLUDE and LIB paths are a list of multiple directories to search, 
order is important.  Only the first file found matching the specified name/type 
will be used.  (Similar to the PATH environment variable on Windows used to 
search for executables).  This is why the compiler itself will usually have a 
pre-set location list as a starting point, to ensure that those files and 
libraries specific to the compiler are used in preference to any you might add 
later.

So if you were to find a copy of zlib prebuilt for your platform and compiler 
you would get at least a .h and .lib (headers and pre-compiled library file).  
You can stick those anywhere you like and add the directory where you put then 
to the INCLUDE search path (so the #include  will find it) and the LIB 
path (so you can specify that Z.LIB or whatever it is named for you) can be 
located when you add the z.lib library to be linked to your project.

In many cases these path additions are done by adding them (and may be done 
automatically for you when you install the library) to the INCLUDE and LIB 
environment variables.  That way whenever you need/reference the 
library/headers they will be found.

---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a 
lot about anticipated traffic volume.


>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of curmudgeon
>Sent: Friday, 25 August, 2017 11:35
>To: sqlite-users@mailinglists.sqlite.org
>Subject: Re: [sqlite] Compiling spellfix for sqlite3
>
>Thanks Keith, the config info is most welcome. I wasn't sure if I was
>supposed to download zlib.h the fact it was inside <> instead of ""
>but
>understand now.
>
>Is the include  in csv.c not a bug though, or is it
>again down
>to my compiler?
>
>
>
>--
>View this message in context:
>http://sqlite.1065341.n5.nabble.com/Compiling-spellfix-for-sqlite3-
>tp70656p97105.html
>Sent from the SQLite mailing list archive at Nabble.com.
>___
>sqlite-users mailing list
>sqlite-users@mailinglists.sqlite.org
>http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users



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

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-25 Thread curmudgeon

Thanks Keith, the config info is most welcome. I wasn't sure if I was
supposed to download zlib.h the fact it was inside <> instead of "" but
understand now.

Is the include  in csv.c not a bug though, or is it again down
to my compiler?



--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/Compiling-spellfix-for-sqlite3-tp70656p97105.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-25 Thread Keith Medcalf

uce 
Synchronous to NORMAL in WAL mode
#define SQLITE_LIKE_DOESNT_MATCH_BLOBS  1   // Disable LIKE 
matching for BLOBS
// #define SQLITE_MAX_EXPR_DEPTH   0   // Disable 
Parser Depth Checking
// #define SQLITE_OMIT_DECLTYPE1   // Omit 
Declaration Type from Cursors
// #define SQLITE_OMIT_DEPRECATED  1   // Omit 
Deprecated Code
// #define SQLITE_OMIT_PROGRESS_CALLBACK   1   // Omit 
Progress Callback loop counter
// #define SQLITE_OMIT_SHARED_CACHE1   // Omit 
Shared Cache

// Compiler and Platform specifics

#define HAVE_FDATASYNC 1
#define HAVE_GMTIME_R 1
#define HAVE_LOCALTIME_S 1
#define HAVE_USLEEP 1
#define HAVE_UTIME 1
#define HAVE_MALLOC_USABLE_SIZE 1

#if defined(_WIN32) && defined(__GNUC__)
#define UNICODE_STRING_MAX_BYTES ((WORD)65534)
#define UNICODE_STRING_MAX_CHARS (32766)
#define HAVE_ISNAN 1
#endif

#if defined(__GNUC__) && defined(SQLITE_USE_QUADMATH)
#define LONGDOUBLE_TYPE __float128
#endif
#endif
---//-- snip --//--

and that is how I end up with this after building the shell:

SQLite version 3.21.0 2017-08-25 13:34:18
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> pragma compile_options;
ALLOW_COVERING_INDEX_SCAN
ALLOW_URI_AUTHORITY
COMPILER=gcc-7.1.0
DEFAULT_CACHE_SIZE=262144
DEFAULT_FOREIGN_KEYS
DEFAULT_MMAP_SIZE=0
DEFAULT_PAGE_SIZE=4096
DEFAULT_PROXYDIR_PERMISSIONS=0755
DEFAULT_RECURSIVE_TRIGGERS
DEFAULT_WAL_AUTOCHECKPOINT=256
DEFAULT_WAL_SYNCHRONOUS=1
ENABLE_8_3_NAMES=1
ENABLE_API_ARMOR
ENABLE_COLUMN_METADATA
ENABLE_COSTMULT
ENABLE_CURSOR_HINTS
ENABLE_DBSTAT_VTAB
ENABLE_FTS3
ENABLE_FTS3_PARENTHESIS
ENABLE_FTS4
ENABLE_FTS5
ENABLE_JSON1
ENABLE_LOAD_EXTENSION
ENABLE_LOCKING_STYLE=1
ENABLE_MEMORY_MANAGEMENT
ENABLE_MEMSYS3
ENABLE_MEMSYS5
ENABLE_PREUPDATE_HOOK
ENABLE_RBU
ENABLE_RTREE
ENABLE_SESSION
ENABLE_STAT4
ENABLE_STMTVTAB
EXTRA_INIT=core_init
HAVE_ISNAN
LIKE_DOESNT_MATCH_BLOBS
MAX_ATTACHED=15
SOUNDEX
STAT4_SAMPLES=64
TEMP_STORE=2
THREADSAFE=1
USE_URI
WIN32_MALLOC

(the EXTRA_INIT being set separately so I can build an "unmodified" version 
without all the extra extensions for debugging ..)

---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a 
lot about anticipated traffic volume.

>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of curmudgeon
>Sent: Friday, 25 August, 2017 07:41
>To: sqlite-users@mailinglists.sqlite.org
>Subject: Re: [sqlite] Compiling spellfix for sqlite3
>
>While testing I appended the following code to the end of sqlite3.c.
>
>#include "csv.c"
>#include "stmt.c"
>#include "compress.c"
>#include "eval.c"
>#include "carray.c"
>
>int core_init(const char* dummy)
>{
>   int nErr = 0;
>   nErr +=
>sqlite3_auto_extension((void(*)())sqlite3_compress_init);
>   nErr += sqlite3_auto_extension((void(*)())sqlite3_eval_init);
>#ifndef SQLITE_OMIT_VIRTUALTABLE
>   nErr += sqlite3_auto_extension((void(*)())sqlite3_csv_init);
>   nErr += sqlite3_auto_extension((void(*)())sqlite3_stmt_init);
>   nErr += sqlite3_auto_extension((void(*)())sqlite3_carray_init);
>#endif
>   return nErr ? SQLITE_ERROR : SQLITE_OK;
>}
>
>
>My compiler gave the following errors/warnings.
>
>[bcc32 Error] csv.c(42): E2209 Unable to open include file
>'sqlite3ext.h'
>I fixed this error by changing  to "sqlite3ext.h"
>
>[bcc32 Error] sqlite3.c(204450): E2451 Undefined symbol
>'sqlite3_stmt_init'
>Not sure if this is to do with the fact that stmt.c is already
>present in
>sqlite3.c
>
>[bcc32 Error] compress.c(18): E2209 Unable to open include file
>'zlib.h'
>Above error appears even if I change  to "zlib.h"
>[bcc32 Warning] compress.c(54): W8065 Call to function 'compress'
>with no
>prototype
>[bcc32 Error] compress.c(55): E2451 Undefined symbol 'Z_OK'
>[bcc32 Warning] compress.c(87): W8065 Call to function 'uncompress'
>with no
>prototype
>[bcc32 Error] compress.c(88): E2451 Undefined symbol 'Z_OK'
>
>
>
>
>
>
>--
>View this message in context:
>http://sqlite.1065341.n5.nabble.com/Compiling-spellfix-for-sqlite3-
>tp70656p97100.html
>Sent from the SQLite mailing list archive at Nabble.com.
>___
>sqlite-users mailing list
>sqlite-users@mailinglists.sqlite.org
>http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users



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

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-25 Thread curmudgeon

While testing I appended the following code to the end of sqlite3.c.

#include "csv.c"
#include "stmt.c"
#include "compress.c"
#include "eval.c"
#include "carray.c"

int core_init(const char* dummy)
{
int nErr = 0;
nErr += sqlite3_auto_extension((void(*)())sqlite3_compress_init);
nErr += sqlite3_auto_extension((void(*)())sqlite3_eval_init);
#ifndef SQLITE_OMIT_VIRTUALTABLE
nErr += sqlite3_auto_extension((void(*)())sqlite3_csv_init);
nErr += sqlite3_auto_extension((void(*)())sqlite3_stmt_init);
nErr += sqlite3_auto_extension((void(*)())sqlite3_carray_init);
#endif
return nErr ? SQLITE_ERROR : SQLITE_OK;
}


My compiler gave the following errors/warnings.

[bcc32 Error] csv.c(42): E2209 Unable to open include file 'sqlite3ext.h'
I fixed this error by changing  to "sqlite3ext.h"

[bcc32 Error] sqlite3.c(204450): E2451 Undefined symbol 'sqlite3_stmt_init'
Not sure if this is to do with the fact that stmt.c is already present in
sqlite3.c

[bcc32 Error] compress.c(18): E2209 Unable to open include file 'zlib.h'
Above error appears even if I change  to "zlib.h"
[bcc32 Warning] compress.c(54): W8065 Call to function 'compress' with no
prototype
[bcc32 Error] compress.c(55): E2451 Undefined symbol 'Z_OK'
[bcc32 Warning] compress.c(87): W8065 Call to function 'uncompress' with no
prototype
[bcc32 Error] compress.c(88): E2451 Undefined symbol 'Z_OK'






--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/Compiling-spellfix-for-sqlite3-tp70656p97100.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-24 Thread Dominique Devienne

On Thu, Aug 24, 2017 at 1:24 AM, Keith Medcalf  wrote:

> >On Wed, Aug 23, 2017 at 6:11 PM, Keith Medcalf 
> wrote:
> >Where's that pragma from Keith? Thanks, --DD
>
> They were added "experimentally" on July 7, 2017

Oh cool, that's great! thanks for the heads-up.

> You will note that for example the returned rows show both the builtin and
> user-defined function names,

even though one may be overriding the other in various circumstances,

and also no differentiation between scalar functions, aggregates, and no
> flags or argument numbers/types.

I hope this is added eventually, fwiw. All that info exists in the
in-memory data-model,
so there's no reason the evtable wouldn't expose it IMHO. Then again, I've
thought for years
there's no reason SQLite didn't have this pragma either, so who knows
if/when that might come :)

> They appeared in the 3.20.0 release code although turned off by default --

you need to "build your own" with the preprocessor symbol
> SQLITE_INTROSPECTION_PRAGMAS defined.
>
> The commit to trunk can be found here:
> https://www.sqlite.org/src/info/e0b6ae92adfae46f

Thanks again for the detailed info. Cheers, --DD
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-23 Thread Keith Medcalf

On Wednesday, 23 August, 2017 16:28, Dominique Devienne  
wrote:

>On Wed, Aug 23, 2017 at 6:11 PM, Keith Medcalf  wrote:

>> sqlite> pragma function_list;
>> group_concat|1
>> group_concat|1
>> julianday|1
>> julianday|1
>> nullif|1
>> nullif|1
>> sqlite_compileoption_get|1
>> sqlite_compileoption_get|1
>> current_timestamp|1
>> current_timestamp|1
>> sqlite_compileoption_used|1
>> sqlite_compileoption_used|1

>Where's that pragma from Keith? Thanks, --DD

>There's no such pragma at https://sqlite.org/pragma.html
>and below you can see it's just as good as another, which pragma
>happily ignores.

They were added "experimentally" on July 7, 2017 -- meaning they do not show up 
in the documentation yet, and presumably that the implementation may change 
(and may currently be perhaps a little buggy or inconsistent -- if it breaks 
you own both halves when you use undocumented/pre-release features).  

You will note that for example the returned rows show both the builtin and 
user-defined function names, even though one may be overriding the other in 
various circumstances, and also no differentiation between scalar functions, 
aggregates, and no flags or argument numbers/types.  However if all you are 
looking for is whether or not a certain module or function is loaded (by name) 
on a connection then it returns that information.  Anything more specific is 
not returned though -- so you have to assume that the function you want is the 
one you see.

They appeared in the 3.20.0 release code although turned off by default -- you 
need to "build your own" with the preprocessor symbol 
SQLITE_INTROSPECTION_PRAGMAS defined.

The commit to trunk can be found here:

https://www.sqlite.org/src/info/e0b6ae92adfae46f

---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a 
lot about anticipated traffic volume.

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

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-23 Thread Dominique Devienne

On Wed, Aug 23, 2017 at 6:11 PM, Keith Medcalf  wrote:

>
> sqlite> pragma function_list;
> group_concat|1
> group_concat|1
> julianday|1
> julianday|1
> nullif|1
> nullif|1
> sqlite_compileoption_get|1
> sqlite_compileoption_get|1
> current_timestamp|1
> current_timestamp|1
> sqlite_compileoption_used|1
> sqlite_compileoption_used|1
>

Where's that pragma from Keith? Thanks, --DD

There's no such pragma at https://sqlite.org/pragma.html
and below you can see it's just as good as another, which pragma happily
ignores.

I've requested at least twice on this list for this pragma to be added, so
of course you picked my interested.
Given all the other pragmas to introspect SQLite, I'm still baffled SQLite
doesn't have this one.

If it was a security concern, there are ways to mitigate it IMHO
(authorizer, register "hidden" functions, etc...).

C:\Users\ddevienne>sqlite3
SQLite version 3.10.2 2016-01-20 15:27:19
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> pragma function_list;
sqlite> pragma foobar;
sqlite>
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-23 Thread curmudgeon

Thanks for the explanation Keith and the help. I've learned a lot the last
few days.



--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/Compiling-spellfix-for-sqlite3-tp70656p97040.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-23 Thread Keith Medcalf


Excellent!

That format is because the program that gets them is written in Python and the 
"list" format is the native "tuple" output format of Python (for the returned 
row objects).  For example, if in the command line shell you issue this command:

SQLite version 3.21.0 2017-08-21 02:20:57
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> select name as function_name, builtin from pragma_function_list() group 
by name collate nocase, builtin order by name collate nocase asc, builtin desc;
aavg|0
abs|1
acos|0
aggmd2|0
aggmd4|0
aggmd5|0
aggsha1|0
aggsha256|0
aggsha2_256|0

which is the table-valued function version of this:

sqlite> pragma function_list;
group_concat|1
group_concat|1
julianday|1
julianday|1
nullif|1
nullif|1
sqlite_compileoption_get|1
sqlite_compileoption_get|1
current_timestamp|1
current_timestamp|1
sqlite_compileoption_used|1
sqlite_compileoption_used|1



But in Python (with the standard dbapi module) if I execute something like (cn 
is the database connection object):

for row in cn.cursor().execute('select name as function_name, builtin from 
pragma_function_list() group by name collate nocase, builtin order by name 
collate nocase asc, builtin desc;'):
print('pragma_function_list() row=', row)

the printed output looks like this:

pragma_function_list() row= (u'aavg', 0)
pragma_function_list() row= (u'abs', 1)
pragma_function_list() row= (u'acos', 0)
pragma_function_list() row= (u'aggmd2', 0)
pragma_function_list() row= (u'aggmd4', 0)
pragma_function_list() row= (u'aggmd5', 0)
pragma_function_list() row= (u'aggsha1', 0)
pragma_function_list() row= (u'aggsha256', 0)
pragma_function_list() row= (u'aggsha2_256', 0)
pragma_function_list() row= (u'aggsha2_384', 0)
pragma_function_list() row= (u'aggsha2_512', 0)
pragma_function_list() row= (u'aggsha384', 0)
pragma_function_list() row= (u'aggsha3_224', 0)


The pragma's are documented on the SQLite3 documentation pages.
https://sqlite.org/pragma.html

pragma function_list;
pragma module_list;
pragma pragma_list;

are new in SQLite3 3.20.0 if you compile the amalgamation with 
SQLITE_INTROSPECTION_PRAGMAS defined.


---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a 
lot about anticipated traffic volume.

>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of curmudgeon
>Sent: Wednesday, 23 August, 2017 02:55
>To: sqlite-users@mailinglists.sqlite.org
>Subject: Re: [sqlite] Compiling spellfix for sqlite3
>
>Keith, I finally managed to use carray this morning. The C++ builder
>IDE had
>a facility for entering conditional defines in Project|Options. I had
>noticed this before asking the question on the c++ builder forum but
>hadn't
>realised the -D part of -DSQLITE_EXTRA_INIT=cor_init wasn't required.
>
>Thanks for all your help but would you mind if I haunted you just a
>little
>bit longer to clear something up?
>
>You sent me an email with SampleExts.zip and wrote
>
>When I build my sqlite3.dll (on windows with gcc) I get the following
>functions for every connection:
>
>collation_list row = (0, u'ROT13')
>collation_list row = (1, u'NUMERICS')
>...
>
>pragma_function_list() row= (u'aavg', 0)
>pragma_function_list() row= (u'abs', 1)
>pragma_function_list() row= (u'acos', 0)
>
>
>I don't recognise the above 'list' notation and could find nothing on
>it
>when googled. Could you point me to any documentation as I would like
>to add
>some functions/collations that would be automatically attached to
>every
>database connection.
>
>
>
>
>Keith Medcalf wrote
>> On Tuesday, 22 August, 2017 09:30, curmudgeon 
>
>> tam118118@
>
>>  wrote:
>>
>>>Your cast did the trick Keith and it compiled fine once I removed
>the
>>>'-DSQLITE_EXTRA_INIT=core_init' line but I have no idea how to get
>>>that directive into the c++ builder application. I've put up a
>question
>>>on the c++ builder forum but unanswered as yet.
>>
>> Yeah, it must be in there somewhere.  Can't help though as I have a
>deadly
>> allergy to IDE's.
>>
>> In a non-GUI you would specify it as a command line option to the
>compiler
>> (actually, to the pre-processor), as in:
>>
>> gcc -DSQLITE_EXTRA_INIT=core_init sqlite3.c
>>
>> ---
>> The fact that there's a Highway to Hell but only a Stairway to
>Heaven says
>> a lot about anticipated traffic volume.
>>
>>
>>
>>
>> ___
>> sqlite-users mailing list
>
>> sqlite-users@.sqlite
>
>> http://mailinglists.sqlite.org/cgi-bin/

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-23 Thread curmudgeon

Keith, I finally managed to use carray this morning. The C++ builder IDE had
a facility for entering conditional defines in Project|Options. I had
noticed this before asking the question on the c++ builder forum but hadn't
realised the -D part of -DSQLITE_EXTRA_INIT=cor_init wasn't required.

Thanks for all your help but would you mind if I haunted you just a little
bit longer to clear something up?

You sent me an email with SampleExts.zip and wrote

When I build my sqlite3.dll (on windows with gcc) I get the following
functions for every connection:

collation_list row = (0, u'ROT13')
collation_list row = (1, u'NUMERICS')
...

pragma_function_list() row= (u'aavg', 0)
pragma_function_list() row= (u'abs', 1)
pragma_function_list() row= (u'acos', 0)

I don't recognise the above 'list' notation and could find nothing on it
when googled. Could you point me to any documentation as I would like to add
some functions/collations that would be automatically attached to every
database connection.

Keith Medcalf wrote
> On Tuesday, 22 August, 2017 09:30, curmudgeon 

> tam118118@

>  wrote:
> 
>>Your cast did the trick Keith and it compiled fine once I removed the
>>'-DSQLITE_EXTRA_INIT=core_init' line but I have no idea how to get
>>that directive into the c++ builder application. I've put up a question 
>>on the c++ builder forum but unanswered as yet.
> 
> Yeah, it must be in there somewhere.  Can't help though as I have a deadly
> allergy to IDE's.
> 
> In a non-GUI you would specify it as a command line option to the compiler
> (actually, to the pre-processor), as in:
> 
> gcc -DSQLITE_EXTRA_INIT=core_init sqlite3.c
> 
> ---
> The fact that there's a Highway to Hell but only a Stairway to Heaven says
> a lot about anticipated traffic volume.
> 
> 
> 
> 
> ___
> sqlite-users mailing list

> sqlite-users@.sqlite

> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/Compiling-spellfix-for-sqlite3-tp70656p97036.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-22 Thread Keith Medcalf


On Tuesday, 22 August, 2017 09:30, curmudgeon  wrote:

>Your cast did the trick Keith and it compiled fine once I removed the
>'-DSQLITE_EXTRA_INIT=core_init' line but I have no idea how to get
>that directive into the c++ builder application. I've put up a question 
>on the c++ builder forum but unanswered as yet.

Yeah, it must be in there somewhere.  Can't help though as I have a deadly 
allergy to IDE's.

In a non-GUI you would specify it as a command line option to the compiler 
(actually, to the pre-processor), as in:

gcc -DSQLITE_EXTRA_INIT=core_init sqlite3.c

---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a 
lot about anticipated traffic volume.




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

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-22 Thread curmudgeon

Your cast did the trick Keith and it compiled fine once I removed the
'-DSQLITE_EXTRA_INIT=core_init' line but I have no idea how to get that
directive into the c++ builder application. I've put up a question on the
c++ builder forum but unanswered as yet.



--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/Compiling-spellfix-for-sqlite3-tp70656p97028.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-21 Thread Keith Medcalf

On Monday, 21 August, 2017 11:44, curmudgeon wrote:

>Thanks Keith. I followed your instructions but I'm now getting the
>following compiler errors

>[bcc32 Error] carray.c(412): E2342 Type mismatch in parameter 'xInit'
>(wanted 'void (*)()', got 'void *')
>// on the 'nErr +=
>sqlite3_auto_extension((void*)sqlite3_carray_init); line'

This is because you are compiling with a C++ compiler and C++ is picky about 
types (or your compiler is too picky about types when processing C files).  In 
C, a void* can be used anywhere for anything -- it is a completely generic 
pointer -- and you are supposed to know what you are doing if you use one 
(since there is actually no such thing as a "void" that can be pointed at).

You need to change the cast to the expected type:

nErr += sqlite3_auto_extension((void(*)())sqlite3_carray_init);

>[bcc32 Error] carray.c(430): E2040 Declaration terminated incorrectly
>// on the '-DSQLITE_EXTRA_INIT=core_init' line

This is because these are compiler directives and do not go in the source code. 
 They are defines that you pass to the compiler as command line arguments.  IE, 
to have the equivalent of "#define SQLITE_EXTRA_INIT core_init" in effect 
before the sqlite3.c is compiled.  If your compiler has a hooey-gooey, then 
there is some place in it for you to create defines.  You need to define 
SQLITE_EXTRA_INIT=core_init.

>I assume carray.c wasn't being compiled at all the other way and
>that's why there were no errors reported. I tried wrapping the 
>carray.c code in extern "C" {...carray.c code...} in case it was 
>something to do with that but then I got a 'Declaration terminated 
>incorrectly' error on the first line which contains extern "C" {

Yeah.  Compiling C code in C++ mode is a dogs breakfast.  Actually, if 
sqlite3.c is being processed as C++ code I am surprised you are not getting 
billions of errors because many of the rules for incomplete types are different 
in C++ vs C.  When compiling C code the compiler you are using must be  
half-way C compliant and half-way C++ compliant ...

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

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-21 Thread curmudgeon

Thanks Keith. I followed your instructions but I'm now getting the following
compiler errors

[bcc32 Error] carray.c(412): E2342 Type mismatch in parameter 'xInit'
(wanted 'void (*)()', got 'void *')
// on the 'nErr += sqlite3_auto_extension((void*)sqlite3_carray_init); line'

[bcc32 Error] carray.c(430): E2040 Declaration terminated incorrectly
// on the '-DSQLITE_EXTRA_INIT=core_init' line

I assume carray.c wasn't being compiled at all the other way and that's why
there were no errors reported. I tried wrapping the carray.c code in extern
"C" {...carray.c code...} in case it was something to do with that but then
I got a 'Declaration terminated incorrectly' error on the first line which
contains extern "C" {



--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/Compiling-spellfix-for-sqlite3-tp70656p97006.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-21 Thread Keith Medcalf


You have to add the carray.c and core_init functions right at the end of the 
file (not inside any other code blocks).

The way you have it the carray.c is included only if SQLITE_ENABLE_STMTVTAB is 
enabled.

So it should look like this:

#endif /* SQLITE_CORE */
#endif /* !defined(SQLITE_CORE) || defined(SQLITE_ENABLE_STMTVTAB) */

/** End of stmt.c
/

#include carray.c

>
>
>I then added the following code to the end of carray.c
>
>int core_init(const char* dummy)
>{
>   int nErr = 0;
>
>   nErr += sqlite3_auto_extension((void*)sqlite3_carray_init);
>
>   return nErr ? SQLITE_ERROR : SQLITE_OK;
>}
>

These are specified as defines to the compiler correct?  I don't think that the 
-DSQLITE_CORE is required because technically the amalgamation sqlite3.c 
defines it automatically ... I just specify it for the greater certainty.

-DSQLITE_CORE
-DSQLITE_EXTRA_INIT=core_init


---
The fact that there's a Highway to Hell but only a Stairway to Heaven says a 
lot about anticipated traffic volume.


>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of curmudgeon
>Sent: Monday, 21 August, 2017 09:13
>To: sqlite-users@mailinglists.sqlite.org
>Subject: Re: [sqlite] Compiling spellfix for sqlite3
>
>Keith, I know this is an old post but it refers to something we
>discussed
>recently.
>
>I tried the following
>
>I added the #include carray.c line to just above the bottom of the
>amalgamation such that the last few lines are
>
>#include carray.c
>
>#endif /* SQLITE_CORE */
>#endif /* !defined(SQLITE_CORE) || defined(SQLITE_ENABLE_STMTVTAB) */
>
>/** End of stmt.c
>/
>
>
>
>I then added the following code to the end of carray.c
>
>int core_init(const char* dummy)
>{
>   int nErr = 0;
>
>   nErr += sqlite3_auto_extension((void*)sqlite3_carray_init);
>
>   return nErr ? SQLITE_ERROR : SQLITE_OK;
>}
>
>-DSQLITE_CORE
>-DSQLITE_EXTRA_INIT=core_init
>
>
>Everything compiled OK but when I tried to access carray in a query I
>got a
>"no such table" error. To be honest I had no idea where to put what
>and,
>through debugging, I know the core_init function was never entered.
>Can you
>tell me where I'm going wrong?
>
>
>
>
>--
>View this message in context:
>http://sqlite.1065341.n5.nabble.com/Compiling-spellfix-for-sqlite3-
>tp70656p97003.html
>Sent from the SQLite mailing list archive at Nabble.com.
>___
>sqlite-users mailing list
>sqlite-users@mailinglists.sqlite.org
>http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users



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

Re: [sqlite] Compiling spellfix for sqlite3

2017-08-21 Thread curmudgeon

Keith, I know this is an old post but it refers to something we discussed
recently.

I tried the following

I added the #include carray.c line to just above the bottom of the
amalgamation such that the last few lines are

#include carray.c

#endif /* SQLITE_CORE */
#endif /* !defined(SQLITE_CORE) || defined(SQLITE_ENABLE_STMTVTAB) */

/** End of stmt.c
/



I then added the following code to the end of carray.c

int core_init(const char* dummy)
{
int nErr = 0;

nErr += sqlite3_auto_extension((void*)sqlite3_carray_init);

return nErr ? SQLITE_ERROR : SQLITE_OK;
}

-DSQLITE_CORE
-DSQLITE_EXTRA_INIT=core_init


Everything compiled OK but when I tried to access carray in a query I got a
"no such table" error. To be honest I had no idea where to put what and,
through debugging, I know the core_init function was never entered. Can you
tell me where I'm going wrong?




--
View this message in context: 
http://sqlite.1065341.n5.nabble.com/Compiling-spellfix-for-sqlite3-tp70656p97003.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling issue

2016-08-01 Thread Miroslav Rajcic


Thanks Richard.

Regards,
  Miroslav

On 1.8.2016. 20:38, Richard Hipp wrote:

On 8/1/16, Miroslav Rajcic  wrote:

Hello,

just tried to compile "sqlite-snapshot-201607290155.tar.gz" (amalgam) on
OS X and I got these errors:

sqlite/sqlite3.c:108772: error: redefinition of typedef
'sqlite3_api_routines'
sqlite/sqlite3.c:5970: error: previous declaration of
'sqlite3_api_routines' was here

A new snapshot has been uploaded that fixes this problem.



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

Re: [sqlite] Compiling issue

2016-08-01 Thread Richard Hipp

On 8/1/16, Miroslav Rajcic  wrote:
> Hello,
>
> just tried to compile "sqlite-snapshot-201607290155.tar.gz" (amalgam) on
> OS X and I got these errors:
>
> sqlite/sqlite3.c:108772: error: redefinition of typedef
> 'sqlite3_api_routines'
> sqlite/sqlite3.c:5970: error: previous declaration of
> 'sqlite3_api_routines' was here

A new snapshot has been uploaded that fixes this problem.
-- 
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

Re: [sqlite] Compiling issue

2016-08-01 Thread Miroslav Rajcic


Sorry for the typo, correct sentence would be:
Removing the definition at line 108772 solved the problem.

Regards,
  Miroslav

On 1.8.2016. 20:25, Miroslav Rajcic wrote:

Hello,

just tried to compile "sqlite-snapshot-201607290155.tar.gz" (amalgam) 
on OS X and I got these errors:


sqlite/sqlite3.c:108772: error: redefinition of typedef 
'sqlite3_api_routines'
sqlite/sqlite3.c:5970: error: previous declaration of 
'sqlite3_api_routines' was here


Removing the error at line 108772 solved the problem.

Regards,

  Miroslav


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


-
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7690 / Virus Database: 4633/12725 - Release Date: 
08/01/16



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

[sqlite] Compiling issue

2016-08-01 Thread Miroslav Rajcic


Hello,

just tried to compile "sqlite-snapshot-201607290155.tar.gz" (amalgam) on 
OS X and I got these errors:


sqlite/sqlite3.c:108772: error: redefinition of typedef 
'sqlite3_api_routines'
sqlite/sqlite3.c:5970: error: previous declaration of 
'sqlite3_api_routines' was here


Removing the error at line 108772 solved the problem.

Regards,

  Miroslav


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

Re: [sqlite] Compiling on Xcode

2016-07-23 Thread Igor Korot

Simon et al,

On Sat, Jul 23, 2016 at 2:20 AM, Simon Slavin  wrote:
>
> On 23 Jul 2016, at 4:26am, Igor Korot  wrote:
>
>> "Ambiguous expansion of macro MIN/MAX"
>
> Sorry, I don't recognise this problem.  I would try Googling it.

Trying to google I found this:
http://stackoverflow.com/questions/24950240/warnings-with-a-new-xcode-project-using-fmdb-sqlitecipher-and-cocoapods

So it does look like SQLite is trying to define the macro twice, but only
for the OSX..
Anybody else can comment?

Thank you.

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

Re: [sqlite] Compiling on Xcode

2016-07-23 Thread Simon Slavin


On 23 Jul 2016, at 4:26am, Igor Korot  wrote:

> "Ambiguous expansion of macro MIN/MAX"

Sorry, I don't recognise this problem.  I would try Googling it.

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

Re: [sqlite] Compiling on Xcode

2016-07-22 Thread Igor Korot

Simon,
Sorry for the long delay. I was trying to catch up on some other stuff.

On Thu, Jul 14, 2016 at 10:01 AM, Igor Korot  wrote:
> On Thu, Jul 14, 2016 at 9:38 AM, Simon Slavin  wrote:
>>
>> On 14 Jul 2016, at 12:44pm, Igor Korot  wrote:
>>
>>> Is there anything else to check?
>>
>> No.  Those look correct.  You looked at the right place and it had the right 
>> options selected.
>>
>> Although the SQLite team goes to some lengths to avoid errors which prevent 
>> compilation, trying to get rid of every warning generated under every 
>> combination of compiler/OS/hardware that SQLite is used for would be a 
>> never-ending task.
>>
>> I looked up the warning messages you're seeing.  They are all harmless to 
>> your particular way of working.  They're caused by the fact that different 
>> types are different between different compilers, even when running on the 
>> same OS and hardware.  For instance, as far as your compiler is concerned, 
>> under the 64-bit OS X "unsigned long" is a 64-bit unsigned integer but "int" 
>> is a 32-bit integer.
>>
>> There may be a set of compiler options which get rid of those messages but 
>> I'm not an expert on that level and I don't think it matters much anyway.  
>> So I think you can proceed with your setup and expect SQLite to perform 
>> without problems.
>
> OK, thx.
> There are also other warnings reported, however I'm currently at work
> and don't have access to my Mac.
>
> I will post them later to make sure that those are harmless as well.
>
> Thank you.

So the other warning I am seeing is:

"Ambiguous expansion of macro MIN/MAX"

Can those be safely ignored?

Thank you.

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

Re: [sqlite] Compiling on Xcode

2016-07-14 Thread Igor Korot

On Thu, Jul 14, 2016 at 9:38 AM, Simon Slavin  wrote:
>
> On 14 Jul 2016, at 12:44pm, Igor Korot  wrote:
>
>> Is there anything else to check?
>
> No.  Those look correct.  You looked at the right place and it had the right 
> options selected.
>
> Although the SQLite team goes to some lengths to avoid errors which prevent 
> compilation, trying to get rid of every warning generated under every 
> combination of compiler/OS/hardware that SQLite is used for would be a 
> never-ending task.
>
> I looked up the warning messages you're seeing.  They are all harmless to 
> your particular way of working.  They're caused by the fact that different 
> types are different between different compilers, even when running on the 
> same OS and hardware.  For instance, as far as your compiler is concerned, 
> under the 64-bit OS X "unsigned long" is a 64-bit unsigned integer but "int" 
> is a 32-bit integer.
>
> There may be a set of compiler options which get rid of those messages but 
> I'm not an expert on that level and I don't think it matters much anyway.  So 
> I think you can proceed with your setup and expect SQLite to perform without 
> problems.

OK, thx.
There are also other warnings reported, however I'm currently at work
and don't have access to my Mac.

I will post them later to make sure that those are harmless as well.

Thank you.

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

Re: [sqlite] Compiling on Xcode

2016-07-14 Thread Simon Slavin


On 14 Jul 2016, at 12:44pm, Igor Korot  wrote:

> Is there anything else to check?

No.  Those look correct.  You looked at the right place and it had the right 
options selected.

Although the SQLite team goes to some lengths to avoid errors which prevent 
compilation, trying to get rid of every warning generated under every 
combination of compiler/OS/hardware that SQLite is used for would be a 
never-ending task.

I looked up the warning messages you're seeing.  They are all harmless to your 
particular way of working.  They're caused by the fact that different types are 
different between different compilers, even when running on the same OS and 
hardware.  For instance, as far as your compiler is concerned, under the 64-bit 
OS X "unsigned long" is a 64-bit unsigned integer but "int" is a 32-bit integer.

There may be a set of compiler options which get rid of those messages but I'm 
not an expert on that level and I don't think it matters much anyway.  So I 
think you can proceed with your setup and expect SQLite to perform without 
problems.

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

Re: [sqlite] Compiling on Xcode

2016-07-14 Thread Igor Korot

Simon,

On Wed, Jul 13, 2016 at 11:51 PM, Simon Slavin  wrote:
>
> On 14 Jul 2016, at 4:43am, Igor Korot  wrote:
>
>> Right now my C Language option on the Xcode 5.1.1 is set to "GNU99".
>> When using this option I am getting a lot of different warnings like:
>>
>> Value Conversion Issue
>> Implicit conversion loses integer precision.
>
> Check the properties for the sqlite3.h and sqlite3.c files and make sure 
> Xcode understands that they're C code.  It has a bad habit of assuming that 
> .c files are C++ or Objective-C files.

When I select sqlite3.c in the Xcode project pane on the left, on the
right in the "Identity and Type" I see:

[quote]
Name: sqlite3.c
Type: Default - C Source
[/quote

Doing the same for sqlite3.h I get:

[quote]
Name: sqlite3.h
Type: Default - C Header
[/quote]

Is there anything else to check?

Thank you.

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

Re: [sqlite] Compiling on Xcode

2016-07-13 Thread Simon Slavin

On 14 Jul 2016, at 4:43am, Igor Korot  wrote:

> Right now my C Language option on the Xcode 5.1.1 is set to "GNU99".
> When using this option I am getting a lot of different warnings like:
> 
> Value Conversion Issue
> Implicit conversion loses integer precision.

Check the properties for the sqlite3.h and sqlite3.c files and make sure Xcode 
understands that they're C code.  It has a bad habit of assuming that .c files 
are C++ or Objective-C files.

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

[sqlite] Compiling on Xcode

2016-07-13 Thread Igor Korot

Hi, ALL,
Right now my C Language option on the Xcode 5.1.1 is set to "GNU99".
When using this option I am getting a lot of different warnings like:

Value Conversion Issue
Implicit conversion loses integer precision.

I know its just a warning, but I prefer the code to be compiled clean.
I would guess that I need a change the option to get a clean compile.

Which one I should use?

Thank you.
___
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

2016-04-06 Thread 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

2016-04-06 Thread 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

2016-04-06 Thread 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

2016-04-06 Thread 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

2016-04-06 Thread 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

2016-04-05 Thread 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

2016-04-05 Thread 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

2016-04-05 Thread 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

2016-04-05 Thread 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

2016-04-05 Thread 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

2016-04-05 Thread 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

2016-04-05 Thread 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

2016-04-05 Thread 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 3.11.1

2016-03-10 Thread Tim Uy

found it - old copy of cerod slipped into my sqlite3.c!

On Wed, Mar 9, 2016 at 10:44 PM, Tim Uy  wrote:

> yup must be just me, it works fine on a clean fossil clone
>
> On Wed, Mar 9, 2016 at 10:15 PM, Tim Uy  wrote:
>
>> It is probably just something I mangled - but oddly my tsrc/fts5.c has no
>> trace of sqlite3PagerGet and no more than 2 or so lines.
>>
>> On Wed, Mar 9, 2016 at 10:07 PM, Tim Uy  wrote:
>>
>>> I'm getting
>>>
>>> tsrc/fts5.c(23549): error C2198: 'sqlite3PagerGet': too few arguments
>>> for call
>>> tsrc/fts5.c(23568): error C2198: 'sqlite3PagerGet': too few arguments
>>> for call
>>>
>>> What am I missing? :P
>>>
>>
>>
>

[sqlite] compiling 3.11.1

2016-03-09 Thread Tim Uy

yup must be just me, it works fine on a clean fossil clone

On Wed, Mar 9, 2016 at 10:15 PM, Tim Uy  wrote:

> It is probably just something I mangled - but oddly my tsrc/fts5.c has no
> trace of sqlite3PagerGet and no more than 2 or so lines.
>
> On Wed, Mar 9, 2016 at 10:07 PM, Tim Uy  wrote:
>
>> I'm getting
>>
>> tsrc/fts5.c(23549): error C2198: 'sqlite3PagerGet': too few arguments for
>> call
>> tsrc/fts5.c(23568): error C2198: 'sqlite3PagerGet': too few arguments for
>> call
>>
>> What am I missing? :P
>>
>
>

[sqlite] compiling 3.11.1

2016-03-09 Thread Tim Uy

It is probably just something I mangled - but oddly my tsrc/fts5.c has no
trace of sqlite3PagerGet and no more than 2 or so lines.

On Wed, Mar 9, 2016 at 10:07 PM, Tim Uy  wrote:

> I'm getting
>
> tsrc/fts5.c(23549): error C2198: 'sqlite3PagerGet': too few arguments for
> call
> tsrc/fts5.c(23568): error C2198: 'sqlite3PagerGet': too few arguments for
> call
>
> What am I missing? :P
>

[sqlite] compiling 3.11.1

2016-03-09 Thread Tim Uy

I'm getting

tsrc/fts5.c(23549): error C2198: 'sqlite3PagerGet': too few arguments for
call
tsrc/fts5.c(23568): error C2198: 'sqlite3PagerGet': too few arguments for
call

What am I missing? :P

[sqlite] compiling sqlite3 with FTS5 support

2015-10-09 Thread Dan Kennedy

On 10/09/2015 10:18 AM, chromedout64 at yahoo.com wrote:
> I noticed there was talk in the other thread of including FTS5 support in the 
> amalgamation. That would be great and it seems like that might solve my 
> problem. Is that correct?
>
> Also, I noticed what may be a couple typos in the FTS5 documentation at 
> https://www.sqlite.org/fts5.html.
> In the external content table section, the example states:
> CREATE TABLE fts USING fts5(a, c, content=tbl, content_rowid=d);
> I think it should be CREATE VIRTUAL TABLE instead of CREATE TABLE.
>
> Also, in the overview section, the text says:
> The expression to the right of the MATCH operator must be the nameof the FTS5 
> table. The expression on the left must be a text value specifyingthe term to 
> search for.I think the right and left's are backwards.

Thanks for these. Now fixed.

Dan.

[sqlite] compiling sqlite3 with FTS5 support

2015-10-09 Thread chromedou...@yahoo.com

I noticed there was talk in the other thread of including FTS5 support in the 
amalgamation. That would be great and it seems like that might solve my 
problem. Is that correct?

Also, I noticed what may be a couple typos in the FTS5 documentation at 
https://www.sqlite.org/fts5.html.
In the external content table section, the example states:
CREATE TABLE fts USING fts5(a, c, content=tbl, content_rowid=d);
I think it should be CREATE VIRTUAL TABLE instead of CREATE TABLE.

Also, in the overview section, the text says:
The expression to the right of the MATCH operator must be the nameof the FTS5 
table. The expression on the left must be a text value specifyingthe term to 
search for.I think the right and left's are backwards.

[sqlite] compiling sqlite3 with FTS5 support

2015-10-07 Thread chromedou...@yahoo.com

 Is there a way to build the sqlite3 command line utility with integrated FTS5 
support? I have been compiling and installing the latest version by downloading 
the latest 'autoconf' file, such as sqlite-autoconf-3081101.tar.gz, and 
building and installing that. However, I noticed that this is only configured 
for FTS3/FTS4 support.
As a separate process, I was able to compile a 'fts5.so' loadable module by 
downloading the full sqlite-src-3081101.zip file and compiling just the module. 
This can then be loaded and used successfully using the '.load fts5' command in 
the command line interface.
I'm just looking to see how to integrate FTS5 support directly into the sqlite3 
install from the first step. Any help would be appreciated.

[sqlite] Compiling sqlite as as library

2015-07-02 Thread 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

2015-07-02 Thread 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

2015-07-02 Thread 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

2015-07-02 Thread 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

2015-07-02 Thread 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

2015-07-02 Thread 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

2015-07-02 Thread 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

2015-07-02 Thread 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

2015-07-02 Thread 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

2015-07-01 Thread 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

2015-07-01 Thread 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 error on Cygwin on Windows 8.1: 3.8.7.4 and 3.8.8

2015-01-23 Thread Jan Nijtmans

2015-01-19 11:01 GMT+01:00 Frank Ho :
> I compiled the SQLite on the Cygwin 1.7.33 running on a Windows 8.1, here's 
> the error:
>
> .libs/sqlite3.o: In function `sqlite3ThreadProc':
> ../sqlite-autoconf-3080800/sqlite3.c:22471: undefined reference to 
> `_endthreadex'
> .libs/sqlite3.o: In function `sqlite3ThreadCreate':
> ../sqlite-autoconf-3080800/sqlite3.c:22493: undefined reference to 
> `_beginthreadex'
> collect2: error: ld returned 1 exit status

The problem is here:


For Cywin, SQLITE_MUTEX_PTHREADS should be set to 1, but in those
lines SQLITE_MUTEX_W32 is set in stead.

There was a commit which was

Any chance this will be fixed for SQLite 3.8.9?

There was a commit in SQLite which simply disables all
multi-threading for Cygwin:

that's indeed another possible 'solution' ;-)

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

Re: [sqlite] Compiling error on Cygwin on Windows 8.1: 3.8.7.4 and 3.8.8

2015-01-19 Thread Jan Nijtmans

2015-01-19 11:01 GMT+01:00 Frank Ho :
> Hi,
>
> I compiled the SQLite on the Cygwin 1.7.33 running on a Windows 8.1, here's 
> the error:
>
> .libs/sqlite3.o: In function `sqlite3ThreadProc':
> ../sqlite-autoconf-3080800/sqlite3.c:22471: undefined reference to 
> `_endthreadex'
> .libs/sqlite3.o: In function `sqlite3ThreadCreate':
> ../sqlite-autoconf-3080800/sqlite3.c:22493: undefined reference to 
> `_beginthreadex'
> collect2: error: ld returned 1 exit status

If you are interested, you can get a corrected amalgamation here:
   


An official cygwin build of SQLite 3.8.8 will be available soon.

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

[sqlite] Compiling error on Cygwin on Windows 8.1: 3.8.7.4 and 3.8.8

2015-01-19 Thread Frank Ho

Hi,

I compiled the SQLite on the Cygwin 1.7.33 running on a Windows 8.1, here's the 
error:

.libs/sqlite3.o: In function `sqlite3ThreadProc': 
../sqlite-autoconf-3080800/sqlite3.c:22471: undefined reference to 
`_endthreadex' 
.libs/sqlite3.o: In function `sqlite3ThreadCreate': 
../sqlite-autoconf-3080800/sqlite3.c:22493: undefined reference to 
`_beginthreadex' 
collect2: error: ld returned 1 exit status 

Best Regards



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

Re: [sqlite] compiling for WP81

2014-11-20 Thread E. Timothy Uy

I found the issue. I call vcvarsphoneall.bat and then vcvarsall.bat again
in order to reset everything. But WindowsPhoneKitDir does not get unset,
this triggers build-all-msvc.bat to cal vcvarsphoneall once again. Probably
that segment needs to be removed from build-all-msvc.bat since it seems
that you are no longer dependent on vcvarsphoneall.bat.

On Thu, Nov 20, 2014 at 12:03 PM, E. Timothy Uy  wrote:

> It seem the problem was that I was calling vcvarsphoneall first. Though I
> am surprised the winrt build worked fine.
>
> On Thu, Nov 20, 2014 at 11:15 AM, Joe Mistachkin 
> wrote:
>
>>
>> E. Timothy Uy wrote:
>> >
>> >> Seems that when making mkkeywordhash.exe, it should be using the x86
>> lib
>> >> paths.
>> >>
>> >> On Thu, Nov 20, 2014 at 12:45 AM, E. Timothy Uy  wrote:
>> >>
>> >>> Hi, I am attempting to compile for WP81 using build-all-msvc.bat.
>> >>> However, when I initialize with vcvarsphoneall, I end up with
>> >>>
>> >
>>
>> Please try the following commands from a Visual Studio 2013 Command
>> Prompt:
>>
>> SET PLATFORMS=x86 x86_arm
>> SET NMAKE_ARGS=FOR_WINRT=1 USE_WP81_OPTS=1
>>
>> CALL tool\build-all-msvc.bat C:\path\to\output\dir
>>
>> --
>> 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 for WP81

2014-11-20 Thread E. Timothy Uy

It seem the problem was that I was calling vcvarsphoneall first. Though I
am surprised the winrt build worked fine.

On Thu, Nov 20, 2014 at 11:15 AM, Joe Mistachkin 
wrote:

>
> E. Timothy Uy wrote:
> >
> >> Seems that when making mkkeywordhash.exe, it should be using the x86 lib
> >> paths.
> >>
> >> On Thu, Nov 20, 2014 at 12:45 AM, E. Timothy Uy  wrote:
> >>
> >>> Hi, I am attempting to compile for WP81 using build-all-msvc.bat.
> >>> However, when I initialize with vcvarsphoneall, I end up with
> >>>
> >
>
> Please try the following commands from a Visual Studio 2013 Command Prompt:
>
> SET PLATFORMS=x86 x86_arm
> SET NMAKE_ARGS=FOR_WINRT=1 USE_WP81_OPTS=1
>
> CALL tool\build-all-msvc.bat C:\path\to\output\dir
>
> --
> 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 for WP81

2014-11-20 Thread Joe Mistachkin


E. Timothy Uy wrote:
>
>> Seems that when making mkkeywordhash.exe, it should be using the x86 lib
>> paths.
>>
>> On Thu, Nov 20, 2014 at 12:45 AM, E. Timothy Uy  wrote:
>>
>>> Hi, I am attempting to compile for WP81 using build-all-msvc.bat.
>>> However, when I initialize with vcvarsphoneall, I end up with
>>>
>

Please try the following commands from a Visual Studio 2013 Command Prompt:

SET PLATFORMS=x86 x86_arm
SET NMAKE_ARGS=FOR_WINRT=1 USE_WP81_OPTS=1

CALL tool\build-all-msvc.bat C:\path\to\output\dir

--
Joe Mistachkin

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

Re: [sqlite] compiling for WP81

2014-11-20 Thread E. Timothy Uy

Seems that when making mkkeywordhash.exe, it should be using the x86 lib
paths.

On Thu, Nov 20, 2014 at 12:45 AM, E. Timothy Uy  wrote:

> Hi, I am attempting to compile for WP81 using build-all-msvc.bat. However,
> when I initialize with vcvarsphoneall, I end up with
>
> /debug
> /out:mkkeywordhash.exe
> "/LIBPATH:F:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\lib"
> "/LIBPATH:C:\Program Files (x86)\Windows Phone Silverlight
> Kits\8.1\lib\x86"
> mkkeywordhash.obj
> LINK : fatal error LNK1104: cannot open file 'kernel32.lib'
> NMAKE : fatal error U1077: '"F:\Program Files (x86)\Microsoft Visual
> Studio 12.0\VC\bin\cl.EXE"' : return code '0x2'
> Stop.
> Failed to build Debug "sqlite3.dll" for platform x86_arm.
>
> Any tips on how I should do this? Should I even be using
> build-all-msvc.bat?
>
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

[sqlite] compiling for WP81

2014-11-20 Thread E. Timothy Uy

Hi, I am attempting to compile for WP81 using build-all-msvc.bat. However,
when I initialize with vcvarsphoneall, I end up with

/debug
/out:mkkeywordhash.exe
"/LIBPATH:F:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\lib"
"/LIBPATH:C:\Program Files (x86)\Windows Phone Silverlight Kits\8.1\lib\x86"
mkkeywordhash.obj
LINK : fatal error LNK1104: cannot open file 'kernel32.lib'
NMAKE : fatal error U1077: '"F:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\bin\cl.EXE"' : return code '0x2'
Stop.
Failed to build Debug "sqlite3.dll" for platform x86_arm.

Any tips on how I should do this? Should I even be using build-all-msvc.bat?
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] Compiling System.Data.SQLite for .NET CF 3.5 (VS2008 & WinCE 6) on x86

2014-05-09 Thread Joe Mistachkin


Eric Johnston wrote:
>
> The question is: How do I compile System.Data.SQLite for .NET CF 3.5
(VS2008)
> with a target platform of x86 for the SQLite.Interop.092.dll? 
>

The Windows CE 6.x SDKs that I've seen do not include support for the x86
platform.  Are you aware of one that does?

--
Joe Mistachkin

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

[sqlite] Compiling System.Data.SQLite for .NET CF 3.5 (VS2008 & WinCE 6) on x86

2014-05-08 Thread Eric Johnston

The question is: How do I compile System.Data.SQLite for .NET CF 3.5 (VS2008) 
with a target platform of x86 for the SQLite.Interop.092.dll?

I feel as though this should be painfully obvious, but after going through the 
release build documentation I still can't find a way to do it. The archives for 
this list show a handful of others also asking about this, but none have any 
responses. The official binary packages come in ARM and x86 flavors for .NET CF 
3.9.

Building for ARM was completely painless and it works on the ARM devices with 
no problems. What I can't seem to do is produce the right 
SQLite.Interop.092.dll for x86. Every Interop library that it depends on that 
I've tried errors out with "Can't find PInvoke DLL 'SQLite.Interop.092.dll'" or 
a version mismatch.

Thank you for any assistance,
Eric
___
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)

2014-03-01 Thread 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)

2014-03-01 Thread 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.

2014-02-16 Thread 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

2013-11-17 Thread 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 the non-AMALGAMATION on visual studio

2013-10-30 Thread Joe Mistachkin


David Clark wrote:
>
> NMAKE : fatal error U1045: spawn failed : No error
> Stop.
>

>From my research, it looks like this error is caused by a 64-bit versus
32-bit issue.  What version Windows are you running?  Is it 32-bit or
64-bit?  Which ActiveTcl distribution file did you install?

--
Joe Mistachkin

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

Re: [sqlite] compiling the non-AMALGAMATION on visual studio

2013-10-30 Thread David Clark

Joe I tried you nmake line on a fresh extract of the .zip file from the 
download page and got this:
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\ro
wset.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\se
lect.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\st
atus.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\sh
ell.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\sq
lite.h.in tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\sq
lite3ext.h tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\sq
liteInt.h tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\sq
liteLimit.h tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\ta
ble.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\tc
lsqlite.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\to
kenize.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\tr
igger.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\ut
f.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\up
date.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\ut
il.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\va
cuum.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\vd
be.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\vd
be.h tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\vd
beapi.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\vd
beaux.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\vd
beblob.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\vd
bemem.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\vd
besort.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\vd
betrace.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\vd
beInt.h tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\vt
ab.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\wa
l.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\wa
l.h tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\wa
lker.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\src\wh
ere.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\ext\ft
s1\fts1.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\ext\ft
s1\fts1.h tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\ext\ft
s1\fts1_hash.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\ext\ft
s1\fts1_hash.h tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\ext\ft
s1\fts1_porter.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\ext\ft
s1\fts1_tokenizer.h tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\ext\ft
s1\fts1_tokenizer1.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\ext\ft
s2\fts2.c tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\ext\ft
s2\fts2.h tsrc
        1 file(s) copied.

C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>copy /Y .\ext\ft
s2\fts2_hash.c tsrc
        1

Re: [sqlite] compiling the non-AMALGAMATION on visual studio

2013-10-29 Thread Dominique Devienne

On Mon, Oct 28, 2013 at 10:38 PM, David Clark  wrote:

> I am trying to compile the source tree on visual studio with makefile.msc
> and I get the following:
>
[...]

> Why am I doing this:
> I have a database lock error coming from a update query and I am not sure
> why.  So I want to debug into it...but debugging into
> a file bigger than 65000 lines does not work at all on visual studio 2008.
>
>

See [1] for a similar question and its solution. --DD

[1]:
http://sqlite.1065341.n5.nabble.com/Windows-Specific-2-c-files-Amalgamation-tp67626p67627.html
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Re: [sqlite] compiling the non-AMALGAMATION on visual studio

2013-10-28 Thread Joe Mistachkin


David Clark wrote:
>
> So I want to debug into it...but debugging into a file bigger than 65000
> lines does not work at all on visual studio 2008.  
>

Using the latest trunk, you can work around this issue with Visual Studio by
using the following make command:

nmake /f Makefile.msc all SPLIT_AMALGAMATION=1

--
Joe Mistachkin

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

[sqlite] compiling the non-AMALGAMATION on visual studio

2013-10-28 Thread David Clark

I am trying to compile the source tree on visual studio with makefile.msc and I 
get the following:
C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>nmake -B -f make
file.msc | more

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

        copy .\src\lempar.c .
        1 file(s) copied.
        cl -W3 -MD -DNDEBUG -D_CRT_SECURE_NO_DEPRECATE -D_CRT_SECURE_NO_WARNINGS
 -D_CRT_NONSTDC_NO_DEPRECATE -D_CRT_NONSTDC_NO_WARNINGS -Od -Zi -Daccess=_access
 -Felemon.exe .\tool\lemon.c /link
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.30729.01 for 80x86
Copyright (C) Microsoft Corporation.  All rights reserved.

lemon.c
Microsoft (R) Incremental Linker Version 9.00.30729.01
Copyright (C) Microsoft Corporation.  All rights reserved.

/debug
/out:lemon.exe
lemon.obj
        del /Q parse.y parse.h parse.h.temp
        copy .\src\parse.y .
        1 file(s) copied.
        .\lemon.exe  -DSQLITE_ENABLE_FTS3=1 -DSQLITE_ENABLE_RTREE=1 -DSQLITE_ENA
BLE_COLUMN_METADATA=1 -DSQLITE_MAX_TRIGGER_DEPTH=100  parse.y
        move parse.h parse.h.temp
NMAKE : fatal error U1045: spawn failed : No error
Stop.


C:\TFS\Main\source\lib\ThirdParty\sqlite_dbg\sqlite-src-3080100>

Why am I doing this:
I have a database lock error coming from a update query and I am not sure why.  
So I want to debug into it...but debugging into
a file bigger than 65000 lines does not work at all on visual studio 2008.  

Thank you for any advice.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

1 2 3 4 5 >

1 - 100 of 419 matches

Mail list logo