/
niceSOFT
/
sqlite
Обзор
Документация
Войти
/
niceSOFT
/
sqlite
Код
Задачи
Вики
Пакеты
0
Релизы
0
Аналитика
Безопасность
version-3.49.2
Makefile.in
349 строк
11 KB
stephan
Account for the Mac-specific -install_name linker flag. See [forum:5651662b8875ec0a|forum post 5651662b8875ec0a].
04 апр 2025, 23:58
04 апр 2025, 23:58
31eb27e
Код
Авторство
О чём код?
#!/usr/bin/make # ^^^^ help out editors which guess this file's type. # # Makefile for SQLITE # # This makefile is intended to be configured automatically using the # configure script. # # The docs for many of its variables are in the primary static # makefile, main.mk (which this one includes at runtime). # all: ######################################################################## # # Known TODOs/FIXMEs/TOIMPROVEs for the autosetup port, in no # particular order... # # - TEA pieces. # # - Replace the autotools-specific distribution deliverable(s). # # - Confirm whether cross-compilation works and patch it # appropriately. # # Maintenance reminders: # # - This makefile should remain as POSIX-make-compatible as possible: # https://pubs.opengroup.org/onlinepubs/9799919799/utilities/make.html # # - The naming convention of some vars, using periods instead of # underscores, though unconventional, was selected for a couple of # reasons: 1) Personal taste (for which there is no accounting). 2) # It is thought to help defend against inadvertent injection of # those vars via environment variables (because X.Y is not a legal # environment variable name). "Feature or bug?" is debatable and # this naming convention may be reverted if it causes any grief. # # # The top-most directory of the source tree. This is the directory # that contains this "Makefile.in" and the "configure" script. # TOP = @abs_top_srcdir@ # # Autotools-conventional vars which are used by package installation # rules in main.mk. To get sane handling when a user overrides only # a subset of these, we perform some acrobatics with these vars # in the configure script: see [proj-remap-autoconf-dir-vars] for # full details. # # For completeness's sake, the aforementioned conventional vars which # are relevant to our installation rules are: # # datadir = $(prefix)/share # mandir = $(datadir)/man # includedir = $(prefix)/include # exec_prefix = $(prefix) # bindir = $(exec_prefix)/bin # libdir = $(exec_prefix)/lib # # Our builds do not require any of their relatives: # # sbindir = $(exec_prefix)/sbin # sysconfdir = /etc # sharedstatedir = $(prefix)/com # localstatedir = /var # runstatedir = /run # infodir = $(datadir)/info # libexecdir = $(exec_prefix)/libexec # prefix = @prefix@ datadir = @datadir@ mandir = @mandir@ includedir = @includedir@ exec_prefix = @exec_prefix@ bindir = @bindir@ libdir = @libdir@ INSTALL = @BIN_INSTALL@ AR = @AR@ AR.flags = cr CC = @CC@ B.cc = @CC_FOR_BUILD@ @BUILD_CFLAGS@ T.cc = $(CC) # # $(CFLAGS) is problematic because it is frequently overridden when # invoking make, which loses things like -fPIC. So... we avoid using # it directly and instead add a level of indirection. We combine # $(CFLAGS) and $(CPPFLAGS) here because that's the way the legacy # build did it and many builds rely on that. See main.mk for more # details. # # Historical note: the pre-3.48 build only honored CPPFLAGS at # configure-time, and expanded them into the generated Makefile. There # are, in that build, no uses of CPPFLAGS in the configure-expanded # Makefile. Ergo: if a client configures with CPPFLAGS=... and then # explicitly passes CFLAGS=... to make, the CPPFLAGS will be # lost. That behavior is retained in 3.48+. # CFLAGS = @CFLAGS@ @CPPFLAGS@ # # $(LDFLAGS.configure) represents any LDFLAGS=... the client passes to # configure. See main.mk. # LDFLAGS.configure = @LDFLAGS@ # # CFLAGS.core is documented in main.mk. # CFLAGS.core = @SH_CFLAGS@ LDFLAGS.shlib = @SH_LDFLAGS@ LDFLAGS.zlib = @LDFLAGS_ZLIB@ LDFLAGS.math = @LDFLAGS_MATH@ LDFLAGS.rpath = @LDFLAGS_RPATH@ LDFLAGS.pthread = @LDFLAGS_PTHREAD@ LDFLAGS.dlopen = @LDFLAGS_DLOPEN@ LDFLAGS.readline = @LDFLAGS_READLINE@ CFLAGS.readline = @CFLAGS_READLINE@ LDFLAGS.icu = @LDFLAGS_ICU@ LDFLAGS.rt = @LDFLAGS_RT@ CFLAGS.icu = @CFLAGS_ICU@ LDFLAGS.libsqlite3.soname = @LDFLAGS_LIBSQLITE3_SONAME@ # soname: see https://sqlite.org/src/forumpost/5a3b44f510df8ded LDFLAGS.libsqlite3.os-specific = \ @LDFLAGS_MAC_CVERSION@ @LDFLAGS_MAC_INSTALL_NAME@ @LDFLAGS_OUT_IMPLIB@ # os-specific: see # - https://sqlite.org/forum/forumpost/9dfd5b8fd525a5d7 # - https://sqlite.org/forum/forumpost/0c7fc097b2 # - https://sqlite.org/forum/forumpost/5651662b8875ec0a libsqlite3.DLL.basename = @SQLITE_DLL_BASENAME@ # DLL.basename: see https://sqlite.org/forum/forumpost/828fdfe904 libsqlite3.out.implib = @SQLITE_OUT_IMPLIB@ # libsqlite3.out.implib => the output filename part of LDFLAGS_OUT_IMPLIB. ENABLE_LIB_SHARED = @ENABLE_LIB_SHARED@ ENABLE_LIB_STATIC = @ENABLE_LIB_STATIC@ HAVE_WASI_SDK = @HAVE_WASI_SDK@ libsqlite3.DLL.install-rules = @SQLITE_DLL_INSTALL_RULES@ T.cc.sqlite = $(T.cc) @TARGET_DEBUG@ # # Define -D_HAVE_SQLITE_CONFIG_H so that the code knows it # can include the generated sqlite_cfg.h. # # main.mk will fill out T.cc.sqlite with additional flags common to # all builds. # T.cc.sqlite += -D_HAVE_SQLITE_CONFIG_H -DBUILD_sqlite # # $(JIMSH) and $(CFLAGS.jimsh) are documented in main.mk. $(JIMSH) # must start with a path component so that it can be invoked as a # shell command. # CFLAGS.jimsh = @CFLAGS_JIMSH@ JIMSH = ./jimsh$(T.exe) # # $(B.tclsh) is documented in main.mk. # B.tclsh = @BTCLSH@ $(B.tclsh): # # $(OPT_FEATURE_FLAGS) is documented in main.mk. # # The appending of $(OPTIONS) to $(OPT_FEATURE_FLAGS) is historical # and somewhat confusing because there's another var, $(OPTS), which # has a similar (but not identical) role. # OPT_FEATURE_FLAGS = @OPT_FEATURE_FLAGS@ $(OPTIONS) # # Version (X.Y.Z) number for the SQLite being compiled. # PACKAGE_VERSION = @PACKAGE_VERSION@ # # Filename extensions for binaries and libraries # B.exe = @BUILD_EXEEXT@ T.exe = @TARGET_EXEEXT@ B.dll = @BUILD_DLLEXT@ T.dll = @TARGET_DLLEXT@ B.lib = @BUILD_LIBEXT@ T.lib = @TARGET_LIBEXT@ # # $(HAVE_TCL) is 1 if the configure script was able to locate the # tclConfig.sh file, else it is 0. When this variable is 1, the TCL # extension library (libtclsqlite3.so) and related testing apps are # built. # HAVE_TCL = @HAVE_TCL@ # # $(TCLSH_CMD) is the command to use for tclsh - normally just # "tclsh", but we may know the specific version we want to use. This # must point to a canonical TCL interpreter, not JimTCL. # TCLSH_CMD = @TCLSH_CMD@ TCL_CONFIG_SH = @TCL_CONFIG_SH@ # # TCL config info from tclConfig.sh # # We have to inject this differently in main.mk to accommodate static # makefiles, so we don't currently bother to export it here. This # block is retained in case we decide that we do indeed need to export # it at configure-time instead of calculate it at make-time. # #TCL_INCLUDE_SPEC = @TCL_INCLUDE_SPEC@ #TCL_LIB_SPEC = @TCL_LIB_SPEC@ #TCL_STUB_LIB_SPEC = @TCL_STUB_LIB_SPEC@ #TCL_EXEC_PREFIX = @TCL_EXEC_PREFIX@ #TCL_VERSION = @TCL_VERSION@ # # $(TCLLIBDIR) = where to install the tcl plugin. If this is empty, it # is calculated at make-time by the targets which need it but we # export it here so that it can be set at configure-time, so that # clients are not required to pass it at make-time, or may set it in # their environment to override it. # TCLLIBDIR = @TCLLIBDIR@ # # Additional options when running tests using testrunner.tcl # This is usually either blank or --status. # TSTRNNR_OPTS = @TSTRNNR_OPTS@ # # If gcov support was enabled by the configure script, add the appropriate # flags here. It's not always as easy as just having the user add the right # CFLAGS / LDFLAGS, because libtool wants to use CFLAGS when linking, which # causes build errors with -fprofile-arcs -ftest-coverage with some GCCs. # Supposedly GCC does the right thing if you use --coverage, but in # practice it still fails. See: # # http://www.mail-archive.com/debian-gcc@lists.debian.org/msg26197.html # # for more info. # CFLAGS.gcov1 = -DSQLITE_COVERAGE_TEST=1 -fprofile-arcs -ftest-coverage LDFLAGS.gcov1 = -lgcov USE_GCOV = @USE_GCOV@ T.compile.extras = $(CFLAGS.gcov$(USE_GCOV)) T.link.extras = $(LDFLAGS.gcov$(USE_GCOV)) # # Vars with the AS_ prefix are specifically related to AutoSetup. # # AS_AUTO_DEF is the main configure script. # AS_AUTO_DEF = $(TOP)/auto.def # # Shell commands to re-run $(TOP)/configure with the same args it was # invoked with to produce this makefile. # AS_AUTORECONFIG = @SQLITE_AUTORECONFIG@ USE_AMALGAMATION ?= @USE_AMALGAMATION@ LINK_TOOLS_DYNAMICALLY ?= @LINK_TOOLS_DYNAMICALLY@ AMALGAMATION_GEN_FLAGS ?= --linemacros=@AMALGAMATION_LINE_MACROS@ # # CFLAGS for sqlite3$(T.exe) # SHELL_OPT ?= @OPT_SHELL@ Makefile: $(TOP)/Makefile.in $(AS_AUTO_DEF) $(AS_AUTORECONFIG) @touch $@ sqlite3.pc: $(TOP)/sqlite3.pc.in $(AS_AUTO_DEF) $(AS_AUTORECONFIG) @touch $@ install: install-pc # defined in main.mk sqlite_cfg.h: $(AS_AUTO_DEF) $(AS_AUTORECONFIG) @touch $@ # # Fiddle app # # EMCC_WRAPPER must refer to the genuine emcc binary, or a # call-compatible wrapper, e.g. $(TOP)/tool/emcc.sh. If it's empty, # build components requiring Emscripten will not build. # # Achtung: though _this_ makefile is POSIX-make compatible, the fiddle # build requires GNU make. # EMCC_WRAPPER = @EMCC_WRAPPER@ fiddle: sqlite3.c shell.c @if [ x = "x$(EMCC_WRAPPER)" ]; then \ echo "Emscripten SDK not found by configure. Cannot build fiddle." 1&>2; \ exit 1; \ fi $(MAKE) -C ext/wasm fiddle emcc_opt=-Os # # Spell-checking for source comments # The sources checked are either C sources or C source templates. # Their comments are extracted and processed through aspell using # a custom dictionary that contains scads of odd identifiers that # find their way into the comments. # # Currently, this target is setup to be "made" in-tree only. # The output is ephemeral. Redirect it to guide spelling fixups, # either to correct spelling or add words to tool/custom.txt. # ./custom.rws: ./tool/custom.txt @echo 'Updating custom dictionary from tool/custom.txt' aspell --lang=en create master ./custom.rws < ./tool/custom.txt # Note that jimsh does not work here: # https://github.com/msteveb/jimtcl/issues/319 misspell: ./custom.rws has_tclsh84 $(TCLSH_CMD) ./tool/spellsift.tcl ./src/*.c ./src/*.h ./src/*.in # # clean/distclean are mostly defined in main.mk. In this makefile we # perform cleanup known to be relevant to (only) the autosetup-driven # build. # #clean-autosetup: # -if [ -f ext/wasm/GNUmakefile ]; then \ # gmake --no-print-directory --ignore-errors -C ext/wasm clean; \ # fi >/dev/null 2>&1; true #clean: clean-autosetup distclean-autosetup: clean rm -f sqlite_cfg.h config.log config.status config.defines.* Makefile sqlite3.pc rm -f $(TOP)/tool/emcc.sh rm -f libsqlite3*$(T.dll) rm -f jimsh0* distclean: distclean-autosetup # # tool/version-info: a utility for emitting sqlite3 version info # in various forms. # version-info$(T.exe): $(TOP)/tool/version-info.c Makefile sqlite3.h $(T.link) $(ST_OPT) -o $@ $(TOP)/tool/version-info.c IS_CROSS_COMPILING = @IS_CROSS_COMPILING@ include $(TOP)/main.mk