Hello Joe,
thank you for your attention, but your change does not fully address my issue.
This code still assumes that SQLITE_WIN32_CACHE_SIZE is measured in pages:
#ifndef SQLITE_WIN32_HEAP_INIT_SIZE
# define SQLITE_WIN32_HEAP_INIT_SIZE ((SQLITE_WIN32_CACHE_SIZE) * \
I have attempted to compile 3.17.0 in MSVS using the 32 bit native command
line
No editing of sources was done
I have tried the amalgamation download with
cl sqlite3.c -link -dll -out:sqlite3.dll
and sqlite-autoconf-317.tar.gz with
nmake /f makefile.msc
In both cases the dll was produced
Ok, found it by hacking the tcl scripts. The amalgamation code now has the
appropriate macros but when compiled -m64 it works fine but does nothing, when
compiled -m32 it spits a cascade of errors. Same thing using either the
__attribute__ or __stdcall ...
> -Original Message-
>
On Monday, 20 February, 2017 14:25, Cezary H. Noweta
wrote:
> On 2017-02-20 20:07, Keith Medcalf wrote:
> > Yes, and I see the defines for those in the sqlite3.c file, but they are
> not used anywhere ...
> > That is, I would have expected to see:
> > SQLITE_API void
Hello,
On 2017-02-20 20:07, Keith Medcalf wrote:
Yes, and I see the defines for those in the sqlite3.c file, but they are not
used anywhere ...
That is, I would have expected to see:
SQLITE_API void SQLITE_APICALL sqlite3_.()
in all the function definitions. But I don't. Is
Detlef Golze wrote:
>
> Changes carried forward from version 3.12.0 (2016-03-29):
>
Ah, right. I was reading the comments in the source code.
I've checked-in some changes that should prevent integer
overflows when very large values are used for the
SQLITE_DEFAULT_CACHE_SIZE and/or
On Monday, 20 February, 2017 03:58, Cezary H. Noweta said:
> On 2017-02-19 22:25, Keith Medcalf wrote:
> > Can you tell us how you do it with the amalgamation using MSVS?
> ``autoconf'' (containing the same amalgamated ``sqlite3.c'') has the
> following options for that
I would use system.data.sqlite in that situation.
But I would also say it depends on what you already have written, and what your
strengths are. I am under the impression from your first email that you already
have something written using system.data.sqlite. i.e. Using the class
Thanks for the clarification. In my case:
1) Speed is not an issue. Size is not an issue.
2) This is a personal use database (genealogy).
3) Typically I create .dll's that serve as a library (WPF Custom
Control Library) ... easy to use for different programs.
4) For example, I have an Excel
Hello,
On 2017-02-19 18:31, Bart Smissaert wrote:
gcc -o SQLite3_StdCall.dll -shared sqlite3.c -s -Wl,--subsystem,windows,--
kill-at
objdump of SQLite3_StdCall.dll sqlite3_close:
6574f392: 55 push %ebp
6574f393: 89 e5 mov%esp,%ebp
On 2/20/17, Andy Gibbs wrote:
>
> What this means is that using the gcc version number alone will actually
> disable the optimisations given by __builtin_{add|sub|mul}_overflow when
> compiled with clang.
>
Yes. And what this means is that I need to go back and
Hi,
I spotted the compiler version checking changes in commits [810d2932] and
[8d3f485d] and thought I'd drop in with some thoughts.
I am not aware of everything that passes on this mailing list (I am only a
sporadic reader) but I did try to go through and see where this change might
have
Hello,
On 2017-02-19 22:25, Keith Medcalf wrote:
Can you tell us how you do it with the amalgamation using MSVS?
``autoconf'' (containing the same amalgamated ``sqlite3.c'') has the
following options for that task:
-Gz -DSQLITE_CDECL=__cdecl -DSQLITE_APICALL=__stdcall
> The SQLITE_DEFAULT_CACHE_SIZE value is always measured in pages.
http://sqlite.org/compile.html#default_cache_size
http://sqlite.org/pragma.html#pragma_cache_size
My interpretation is that the option to provide a negative value has been
introduced to allow specification of cache size limits
Detlef Golze wrote:
>
> SQLITE_DEFAULT_CACHE_SIZE is defined as page size if positive or
> Kbyte if negative.
>
The SQLITE_DEFAULT_CACHE_SIZE value is always measured in pages.
>
> I came here because I got an integer overflow in the definition
> of SQLITE_WIN32_HEAP_INIT_SIZE.
>
What values
Hi,
the following looks like an incorrect use of SQLITE_DEFAULT_CACHE_SIZE
(amalgamation 3.17 starting at line 37963):
/*
* This is cache size used in the calculation of the initial size of the
* Win32-specific heap. It cannot be negative.
*/
#ifndef SQLITE_WIN32_CACHE_SIZE
# if
16 matches
Mail list logo