ot about anticipated traffic volume.
>-Original Message-
>From: sqlite-users [mailto:sqlite-users-
>boun...@mailinglists.sqlite.org] On Behalf Of John Smith
>Sent: Monday, 21 January, 2019 03:16
>To: SQLite mailing list
>Subject: [sqlite] Building SQLite DLL with Visual Stud
Just curious as to why you wouldn't choose option #2 - as that's what I use
with my VB .NET applications, which work quite well. Just distribute the
.exe, then the two SQLite DLLs (well, three technically, as there are two
versions of the interop.dll)
Thanks,
Chris
On Mon, Jan 21, 2019 at 4:19 P
On 21 Jan 2019, at 11:16am, J Decker wrote:
> 4. Statically linked to and compiled with your datalayer code.
What he said. Also, you should be using the 'Amalgamation' download to do
this, unless you need some compiler switches which are not supported by that
source-set.
Simon.
___
On Mon, Jan 21, 2019 at 2:16 AM John Smith wrote:
> Hi,
>
>
> I need to build a data-layer DLL for a large project.
>
> My project is 64-bit built with Visual-Studio 2015.
>
> I want to ask about what would be the preferred way to build SQLite:
>
> 1. Build SQLite code as a separate DLL and use
Hi,
I need to build a data-layer DLL for a large project.
My project is 64-bit built with Visual-Studio 2015.
I want to ask about what would be the preferred way to build SQLite:
1. Build SQLite code as a separate DLL and use it from my data-layer DLL,
2. Use the ready-built binary of 64-bit
5 matches
Mail list logo
