Hi,
I do it all the time - why not?
There are basically two approaches
1) download precompiled binary from SQLite website
2) compile it yourself.
As for the second one we use CMake for everything. The following little CMake
script does the job:
cmake_minimum_required(VERSION 2.8)
project(sqlite C)
set(CMAKE_SKIP_BUILD_RPATH ON)
set(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${CMAKE_BINARY_DIR}/bin)
set(CMAKE_LIBRARY_OUTPUT_DIRECTORY ${CMAKE_RUNTIME_OUTPUT_DIRECTORY})
set(CMAKE_INCLUDE_CURRENT_DIRECTORY ON)
if(CMAKE_SYSTEM MATCHES Windows)
# warning C4251: class x needs to have dll-interface to be used by
clients of class y
add_definitions(-DWIN32_LEAN_AND_MEAN -Zc:wchar_t -wd4251 -Zi)
endif(CMAKE_SYSTEM MATCHES Windows)
set(Sources
sqlite3.c
)
add_library(sqlite3 SHARED ${Sources})
set_target_properties(sqlite3 PROPERTIES DEFINE_SYMBOL
"SQLITE_API=__declspec(dllexport)")
Note that you can manipulate the "add_definitions" thing. We just happen to use
the same set everywhere.
--
Gruesse,
Jakub
-----Original Message-----
From: sqlite-users-bounces at mailinglists.sqlite.org
[mailto:sqlite-users-bounces at mailinglists.sqlite.org] On Behalf Of
p...@arbolone.ca
Sent: Mittwoch, 26. August 2015 19:03
To: MailingList SQLite3
Subject: [sqlite] SQLite3 to 64-bit DLL
On my Win10, I'd like to compile SQLite3 to create a 64-bit DLL. The intention
is to use this DLL instead of the amalgamation, this way more than one C++
application can access the same DLL. Please note that I am an aficionado, not
an expert when it comes to C++ and for SQL, well, this would be my second
attempt to get an application to use a database, as opposed to flat files.
How would you suggest I should proceed? is this even a good idea?
_______________________________________________
sqlite-users mailing list
sqlite-users at mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
