forked from sqlite/sqlite
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Improved instructions on how to build SQLite on Windows 11 and similar.
FossilOrigin-Name: 0f6b2b33736ee07f17f3a4e5f077bb4d0e2481c8f81251b8ce6b78510f372237
- Loading branch information
drh
committed
Aug 16, 2023
1 parent
0d83c71
commit 7335f75
Showing
4 changed files
with
93 additions
and
32 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,59 @@ | ||
# Notes On Compiling SQLite On Windows 11 | ||
|
||
Here are step-by-step instructions on how to build SQLite from | ||
canonical source on a new Windows 11 PC, as of 2023-08-16: | ||
|
||
1. Install Microsoft Visual Studio. The free "community edition" | ||
will work fine. Do a standard install for C++ development. | ||
SQLite only needs the | ||
"cl" compiler and the "nmake" build tool. | ||
|
||
2. Under the "Start" menu, find "All Apps" then go to "Visual Studio 20XX" | ||
and find "x64 Native Tools Command Prompt for VS 20XX". Pin that | ||
application to your task bar, as you will use it a lot. Bring up | ||
an instance of this command prompt and do all of the subsequent steps | ||
in that "x64 Native Tools" command prompt. (Or use "x86" if you want | ||
a 32-bit build.) The subsequent steps will not work in a vanilla | ||
DOS prompt. Nor will they work in PowerShell. | ||
|
||
3. Install TCL development libraries. This note assumes that you wil | ||
install the TCL development libraries in the "`c:\Tcl`" directory. | ||
Make adjustments | ||
if you want TCL installed somewhere else. SQLite needs both the | ||
"tclsh.exe" command-line tool as part of the build process, and | ||
the "tcl86.lib" library in order to run tests. You will need | ||
TCL version 8.6 or later. | ||
<ol type="a"> | ||
<li>Get the TCL source archive, perhaps from | ||
<https://www.tcl.tk/software/tcltk/download.html>. | ||
<li>Untar or unzip the source archive. CD into the "win/" subfolder | ||
of the source tree. | ||
<li>Run: `nmake /f makefile.vc release` | ||
<li>Run: `nmake /f makefile.vc INSTALLDIR=c:\Tcl install` | ||
<li>CD to c:\\Tcl\\lib. In that subfolder make a copy of the | ||
"`tcl86t.lib`" file to the alternative name "`tcl86.lib`" | ||
(omitting the second 't'). Leave the copy in the same directory | ||
as the original. | ||
<li>CD to c:\\Tcl\\bin. Make a copy of the "`tclsh86t.exe`" | ||
file, renaming it to "`tclsh.exe`". Put the copy somewhere | ||
on your %PATH% so that the SQLite makefile will be able to | ||
run "tclsh" commands. | ||
</ol> | ||
|
||
4. Download the SQLite source tree and unpack it. CD into the | ||
toplevel directory of the source tree. | ||
|
||
5. Set the TCLDIR environment variable to point to your TCL installation. | ||
Like this: | ||
<ul> | ||
<li> `set TCLDIR=c:\Tcl` | ||
</ul> | ||
|
||
6. Run the "`Makefile.msc`" makefile with an appropriate target. | ||
Examples: | ||
<ul> | ||
<li> `nmake /f makefile.msc` | ||
<li> `nmake /f makefile.msc sqlite3.c` | ||
<li> `nmake /f makefile.msc devtest` | ||
<li> `nmake /f makefile.msc releasetest` | ||
</ul> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
a237a31ff4a7cd3dc744af1e1ebb9466e42eebafa31c1b5c0027cbaee9babc9b | ||
0f6b2b33736ee07f17f3a4e5f077bb4d0e2481c8f81251b8ce6b78510f372237 |