Home
last modified time | relevance | path

Searched refs:build (Results 1 – 25 of 91) sorted by relevance

1234

/sqlite-3.40.0/tool/
H A Dbuild-all-msvc.bat4 :: build-all-msvc.bat --
10 REM This batch script is used to build the SQLite DLL for multiple platforms
25 REM CALL tool\build-all-msvc.bat C:\Temp
31 REM Please note that the SQLite build process performed by the Makefile
38 REM platforms to build may be overriden by using the PLATFORMS environment
41 REM being used. The list of configurations to build may be overridden by
123 REM for the build.
624 REM specifically wanting to build for each platform.
640 ECHO Failed to build %%B "%DLL_FILE_NAME%" for platform %%P.
646 REM the build and platform beneath the binary directory.
[all …]
H A Dwarnings-clang.sh9 scan-build gcc -c -DHAVE_STDINT_H -DSQLITE_ENABLE_FTS4 -DSQLITE_ENABLE_RTREE \
12 scan-build gcc -c -I. -DSQLITE_ENABLE_STAT3 -DSQLITE_THREADSAFE=0 \
/sqlite-3.40.0/autoconf/tea/
H A DREADME11 and then run make. For more information about the build process, see
23 The recommended method to build extensions under windows is to use the
24 Msys + Mingw build process. This provides a Unix-style build while
25 generating native Windows binaries. Using the Msys + Mingw build tools
26 means that you can use the same configure script as per the Unix build
31 subdirectory and build the extension using just VC++. These files have
H A Dconfigure.ac158 AC_DEFINE(SQLITE_THREADSAFE, 1, [Trigger sqlite threadsafe build])
163 AC_DEFINE(SQLITE_THREADSAFE, 0, [Trigger sqlite non-threadsafe build])
/sqlite-3.40.0/
H A Dconfigure.ac2 # The build process allows for using a cross-compiler. But the default
5 # build and target systems:
30 # source files into executables that run on the build
35 # Switches that the build compiler needs in order to construct
40 # Libraries that the build compiler needs in order to construct
45 # The filename extension for executables on the build
127 echo "Warning: can't find tclsh - defaulting to non-amalgamation build."
162 # Locate a compiler for the build machine. This compiler should
163 # generate command-line programs that run on the build machine.
558 AC_MSG_CHECKING([build type])
[all …]
H A DREADME.md54 a stand-alone program. To install, simply download or build the single
74 the build products. It is recommended, but not required, that the
75 build directory be separate from the source directory. Cd into the
76 build directory and then from the build directory run the configure
83 cd bld ;# Change to the build directory
99 On Windows, all applicable build products can be compiled with MSVC.
102 with the provided "Makefile.msc" to build one of the supported targets.
114 There are several build options that can be set via the NMAKE command
127 **src/** folder also contains files used to build the "testfixture" test
159 fill it with all the source files needed to build SQLite, both
[all …]
H A Dspec.template36 %build
/sqlite-3.40.0/ext/wasm/
H A DGNUmakefile43 $(info WARNING: breaking _All The Things_. The workaround for that is to build)
47 $(info WARNING: If this build uses any optimization level higher than -O1 then)
187 $(info Development build. Use '$(MAKE) release' for a smaller release build.)
209 sqlite3-api-build-version.js := $(dir.tmp)/sqlite3-api-build-version.js
217 sqlite3-api.jses += $(sqlite3-api-build-version.js)
246 $(sqlite3-api-build-version.js): $(bin.version-info) $(MAKEFILE)
600 $(info This platform does not support the WASMFS build.)
H A DREADME.md2 parts of the sqlite3 build.
4 It requires [emscripten][] and that the build environment be set up for
47 from the top of the sqlite3 build tree:
91 * Remote: "`make`" to build WASM
H A Ddist.make38 dist.build ?= oz
70 $(dist.build) \
H A DREADME-dist.txt8 up the sqlite3 WASM/JS build.
/sqlite-3.40.0/ext/wasm/api/
H A DREADME.md4 `sqlite3-wasm.c`. This collection of files is used to build a
13 build environments. e.g. the files `post-js-*.js` are for use with
51 - `sqlite3-api-build-version.js`\
52 Gets created by the build process and populates the
98 The build process glues those files together, resulting in
110 The following files are part of the build process but are injected
111 into the build-generated `sqlite3.js` along with `sqlite3-api.js`.
/sqlite-3.40.0/autoconf/tea/win/
H A Drules.vc5 # macros. This file does not need editing to build Tcl.
102 # build the helper app we need to overcome nmake's limiting
303 # Make sure we don't build overly fat DLLs.
323 # x = special static build when it
493 # Locate the Tcl headers to build against
602 COFFBASE = \must\have\tcl\sources\to\build\this\target
603 TCLTOOLSDIR = \must\have\tcl\sources\to\build\this\target
623 # Locate the Tk headers to build against
/sqlite-3.40.0/autoconf/
H A DREADME.first1 This directory contains components use to build an autoconf-ready package
4 To build the autoconf amalgamation, run from the top-level:
H A DREADME.txt6 * the shell.c file used to build the sqlite3 command-line shell program
27 --enable-threadsafe build a thread-safe library [default=yes]
31 compiler) includes debugging symbols in the build, resulting in larger
H A DINSTALL16 configure, build, and install this package. The following
120 is known as a "VPATH" build.
138 may have to build one architecture at a time and combine the results
263 `--build=TYPE' option. TYPE can either be a short name for the system
282 platform different from the build platform, you should specify the
302 configure again during the build, and the customized values of these
H A Dconfigure.ac88 [--enable-threadsafe], [build a thread-safe library [default=yes]])],
210 [--enable-debug], [build with debugging features enabled [default=no]])],
/sqlite-3.40.0/autoconf/tea/tclconfig/
H A Dtcl.m4570 # tclConfig.sh is in Tcl build directory
628 # tkConfig.sh is in Tk build directory
691 AC_MSG_CHECKING([how to build libraries])
724 AC_DEFINE(STATIC_BUILD, 1, [This a static build])
778 [build with threads (default: on)]),
896 AC_MSG_CHECKING([for build with symbols])
899 [build with debugging symbols (default: off)]),
1472 # Use to build 6.2 compatible binaries on 6.3.
1641 # Check for combined 32-bit and 64-bit fat build
3204 # Some packages build their own stubs libraries
[all …]
/sqlite-3.40.0/mptest/
H A Dmultiwrite01.test5 --task 1 build-t1
37 --task 2 build-t2
68 --task 3 build-t3
99 --task 4 build-t4
130 --task 5 build-t5
/sqlite-3.40.0/test/
H A Dcapi3.test252 # Use the return value of sqlite3_column_count() to build
254 # is 3, build the list {0 1 2}.
351 # this build, this proc is a no-op.
353 # Use the return value of sqlite3_column_count() to build
355 # is 3, build the list {0 1 2}.
446 # Use the return value of sqlite3_column_count() to build
448 # is 3, build the list {0 1 2}.
H A Dcapi3c.test233 # Use the return value of sqlite3_column_count() to build
235 # is 3, build the list {0 1 2}.
332 # this build, this proc is a no-op.
335 # Use the return value of sqlite3_column_count() to build
337 # is 3, build the list {0 1 2}.
428 # Use the return value of sqlite3_column_count() to build
430 # is 3, build the list {0 1 2}.
H A Dpragma5.test14 # those pragmas that are not disabled at build time by setting:
H A Dwalrofault.test20 # And only if the build is WAL-capable.
H A Dautovacuum2.test18 # If this build of the library does not support auto-vacuum, omit this
/sqlite-3.40.0/ext/repair/test/
H A DREADME.md1 To run these tests, first build sqlite3_checker:

1234