Annotation of pkgsrc/databases/sqlite3/Makefile, revision 1.162

1.162   ! adam        1: # $NetBSD: Makefile,v 1.161 2024/12/26 22:04:28 riastradh Exp $
1.109     kamil       2: 
                      3: .include "Makefile.common"
1.22      tnn         4: 
1.122     adam        5: DISTNAME=      sqlite-autoconf-${SQLITE3_DISTVERSION}
1.95      khorben     6: PKGNAME=       sqlite3-${SQLITE3_VERSION}
1.22      tnn         7: CATEGORIES=    databases
                      8: 
                      9: MAINTAINER=    pkgsrc-users@NetBSD.org
                     10: COMMENT=       SQL Database Engine in a C Library
1.9       heinz      11: 
1.37      agc        12: .include "options.mk"
                     13: 
1.32      adam       14: USE_LIBTOOL=           yes
                     15: USE_TOOLS+=            gmake
1.22      tnn        16: GNU_CONFIGURE=         yes
1.105     adam       17: CONFIGURE_ARGS+=       --disable-static-shell
1.22      tnn        18: 
1.110     kamil      19: PKGCONFIG_OVERRIDE+=   sqlite3.pc.in
                     20: 
1.9       heinz      21: INSTALLATION_DIRS+=    ${PKGMANDIR}/man1
1.1       tv         22: 
1.28      obache     23: .include "../../mk/bsd.prefs.mk"
                     24: 
1.161     riastrad   25: # sqlite3 compile options are documented at:
                     26: #
                     27: # https://www.sqlite.org/compile.html
                     28: #
                     29: # We always enable those options that:
                     30: #
                     31: # (a) are not dynamically loadable, but
                     32: # (b) enable functionality applications are likely to require, and
                     33: # (c) do not change default settings, and
                     34: # (d) do not bring unwieldy dependencies, and
                     35: # (e) do not incur unreasonable burden on users not needing them if
                     36: #     applicable only to niche use cases.
                     37: #
                     38: # We also always enable options that are necessary to build, or are
                     39: # performance optimizations that do not affect functionality.
                     40: #
                     41: # Other options -- those that can be dynamically loaded, those that
                     42: # change defaults which applications could override anyway, or those
                     43: # that bring in unwieldy dependencies -- are relegated to options.mk,
                     44: # e.g. the `icu' option which brings in the unwieldy dependency of
                     45: # textproc/icu.
                     46: #
                     47: # Where both a configure argument option and a C preprocessor macro
                     48: # option are available, we prefer the configure argument so that it is
                     49: # checked by the configure script to detect potential bitrot in the
                     50: # future.
                     51: 
                     52: ### Build fixes
1.35      joerg      53: 
1.28      obache     54: # Darwin < 9 (Mac OS X < 10.5 "Leopard") doesn't have gethostuuid(2)
1.81      wiz        55: # and lacks the zone memory allocator
1.28      obache     56: .if !empty(MACHINE_PLATFORM:MDarwin-[0-8].*-*)
1.161     riastrad   57: CFLAGS+=               -DSQLITE_ENABLE_LOCKING_STYLE=0
                     58: CFLAGS+=               -DSQLITE_WITHOUT_ZONEMALLOC
1.28      obache     59: .endif
                     60: 
1.161     riastrad   61: ### Performance optimizations
                     62: 
                     63: # In the past, Linux had database corruption issues with pread, so only
                     64: # enable it on safe platforms.  This (undocumented) option enables the
                     65: # use of pread(2), instead of the sequence of syscalls
                     66: # lseek(2)-then-read(2), to read from a specific position in a file.
                     67: CFLAGS.NetBSD+=                -DUSE_PREAD
                     68: 
                     69: ### Enabled functionality
1.139     adam       70: 
1.161     riastrad   71: # SQLITE_THREADSAFE.  Some applications of sqlite3 in pkgsrc require
                     72: # thread-safety, so we enable this for everyone.  Applications that
                     73: # really benefit from omitting mutexes and similar can statically link
                     74: # a custom build of sqlite3.  We pass the arguments to make sure they
                     75: # stay enabled in case upstream ever changes the default until we
                     76: # review the change.
                     77: CONFIGURE_ARGS+=       --enable-threadsafe
                     78: 
                     79: # The column metadata API provides some additional information about
                     80: # the provenance of columns in query results, and is not dynamically
                     81: # loadable:
                     82: #
                     83: # https://www.sqlite.org/c3ref/column_database_name.html
                     84: # https://www.sqlite.org/compile.html#enable_column_metadata
1.57      drochner   85: CFLAGS+=               -DSQLITE_ENABLE_COLUMN_METADATA
1.161     riastrad   86: 
                     87: # The DBSTAT virtual table provides information about disk space
                     88: # utilization, is required by lang/tcl's bin/sqlite3_analyzer, and is
                     89: # not (as far as I can tell) dynamically loadable:
                     90: #
                     91: # https://www.sqlite.org/dbstat.html
                     92: # https://www.sqlite.org/compile.html#enable_dbstat_vtab
                     93: CFLAGS+=               -DSQLITE_ENABLE_DBSTAT_VTAB
                     94: 
                     95: # Full-text search engines.  There are two full-text search engines,
                     96: # fts3/4 and fts5.  The options SQLITE_ENABLE_FTS3 and
                     97: # SQLITE_ENABLE_FTS4 are equivalent; we enable both to make it clear
                     98: # that that is intended.  fts3 has been available since 3.5.0 in 2007,
                     99: # the fts4 extension (which is unconditionally bundled with the fts3
                    100: # build option now) since 3.7.4 in 2010, fts5 since 3.9.0 in 2015, and
                    101: # all are enabled by default.  We pass the arguments to make sure they
                    102: # stay enabled in case upstream ever changes the default until we
                    103: # review the change.
                    104: #
                    105: # In principle, fts5 is dynamically loadable, but since upstream
                    106: # enables it by default anyway we treat that as a moot point.
                    107: #
                    108: # https://www.sqlite.org/fts3.html
                    109: # https://www.sqlite.org/fts5.html
                    110: # https://www.sqlite.org/compile.html#enable_fts3
                    111: # https://www.sqlite.org/compile.html#enable_fts4
                    112: # https://www.sqlite.org/compile.html#enable_fts5
                    113: CONFIGURE_ARGS+=       --enable-fts3 # -DSQLITE_ENABLE_FTS3
                    114: CONFIGURE_ARGS+=       --enable-fts4 # -DSQLITE_ENABLE_FTS4
                    115: CONFIGURE_ARGS+=       --enable-fts5 # -DSQLITE_ENABLE_FTS5
                    116: 
                    117: # Nested queries and AND/OR operators for fts3/4.
                    118: #
                    119: # https://www.sqlite.org/fts3.html#_set_operations_using_the_enhanced_query_syntax
                    120: # https://www.sqlite.org/compile.html#enable_fts3_parenthesis
                    121: CFLAGS+=               -DSQLITE_ENABLE_FTS3_PARENTHESIS
                    122: 
                    123: # SQLITE_ENABLE_GEOPOLY, SQLITE_ENABLE_RTREE -- R*Tree and Geopoly
                    124: # interface for geospatial queries.  Enabled by default since 2018.  We
                    125: # pass the arguments to make sure they stay enabled in case upstream
                    126: # ever changes the default until we review the change.
                    127: #
                    128: # https://www.sqlite.org/geopoly.html
                    129: # https://www.sqlite.org/rtree.html
                    130: # https://www.sqlite.org/compile.html#enable_geopoly
                    131: # https://www.sqlite.org/compile.html#enable_rtree
                    132: CONFIGURE_ARGS+=       --enable-rtree
                    133: 
                    134: # SQLITE_ENABLE_ICU -- unwieldy dependency, relegated to options.mk.
                    135: # https://www.sqlite.org/compile.html#enable_icu
                    136: 
                    137: # SQLITE_ENABLE_IOTRACE -- experimental and may be discontinued in a
                    138: # future release.
                    139: # https://www.sqlite.org/compile.html#enable_iotrace
                    140: 
                    141: # Hidden columns.  Allows virtual tables to declare certain columns
                    142: # HIDDEN, which hides them from PRAGMA table_info, SELECT *, and
                    143: # implicit INSERT.
                    144: #
                    145: # https://www.sqlite.org/vtab.html#hiddencol
                    146: # https://www.sqlite.org/compile.html#enable_hidden_columns
                    147: CFLAGS+=               -DSQLITE_ENABLE_HIDDEN_COLUMNS
                    148: 
                    149: # SQLITE_ENABLE_JSON1 -- JSON1 support, built-in functions for
                    150: # manipulating JSON.  Enabled by default since 2022, configure option
                    151: # removed, compile-time option switched from opt-in to opt-out in
                    152: # sqlite3>=3.38.0.
                    153: #
                    154: # https://www.sqlite.org/json1.html
                    155: # https://www.sqlite.org/compile.html#enable_json1
                    156: 
                    157: # SQLITE_ENABLE_LOCKING_STYLE -- relevant mainly (only?) on Apple
                    158: # systems, where it is enabled by default anyway.
                    159: #
                    160: #      This option enables additional logic in the OS interface layer
                    161: #      for Mac OS X.  The additional logic attempts to determine the
                    162: #      type of the underlying filesystem and choose and alternative
                    163: #      locking strategy that works correctly for that filesystem type.
                    164: #
                    165: # Note issue with Darwin < 9 (Mac OS X < 10.5 "Leopard") above.
                    166: #
                    167: # https://www.sqlite.org/compile.html#enable_locking_style
                    168: 
                    169: # SQLITE_ENABLE_MATH_FUNCTIONS -- SQL math functions: sin/cos/tan,
                    170: # log/exp, floor/ceil/trunc, &c.  We pass the arguments to make sure
                    171: # they stay enabled in case upstream ever changes the default until we
                    172: # review the change.
                    173: #
                    174: # https://www.sqlite.org/lang_mathfunc.html
                    175: # https://www.sqlite.org/compile.html#enable_math_functions
                    176: CONFIGURE_ARGS+=       --enable-math
                    177: 
                    178: # XXX Consider SQLITE_ENABLE_MEMORY_MANAGEMENT.
                    179: #
                    180: #      This option adds extra logic to SQLite that allows it to
                    181: #      release unused memory upon request.  This option must be
                    182: #      enabled in order for the sqlite3_release_memory() interface to
                    183: #      work.  If this compile-time option is not used, the
                    184: #      sqlite3_release_memory() interface is a no-op.
                    185: #
                    186: # https://www.sqlite.org/compile.html#enable_memory_management
                    187: 
                    188: # SQLITE_ENABLE_MEMSYS3, SQLITE_ENABLE_MEMSYS5 -- alternative memory
                    189: # allocators, mutually exclusive.  These seem likely to be relevant
                    190: # only for specialized applications having unusual dynamic memory
                    191: # allocation requirements, so although this does enable extra
                    192: # functionality (SQLITE_CONFIG_HEAP,
                    193: # https://www.sqlite.org/c3ref/c_config_covering_index_scan.html#sqliteconfigheap),
                    194: # it's not clear which allocator is appropriate to ship by default so
                    195: # we will not enable either one.
                    196: #
                    197: # https://www.sqlite.org/compile.html#enable_memsys3
                    198: # https://www.sqlite.org/compile.html#enable_memsys5
                    199: 
                    200: # XXX Consider -DSQLITE_ENABLE_NORMALIZE.
                    201: #
                    202: #      This option includes the sqlite3_normalized_sql() API.
                    203: #
                    204: # Unclear what runtime consequences this has.  Unclear what
                    205: # applications outside https://github.com/bloomberg/comdb2 use this.
                    206: #
                    207: # https://www.sqlite.org/compile.html#enable_normalize
                    208: #
                    209: # Gentoo enables: https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-db/sqlite/sqlite-3.47.2.ebuild?id=be159693998b95bddf9c118b2425d9f8a2365a67#n211
                    210: #
                    211: # Arch Linux does not: https://gitlab.archlinux.org/archlinux/packaging/packages/sqlite/-/blob/bf41f088e6ca945d9374838780d5bacb47653277/PKGBUILD#L42-53
                    212: # Debian does not: https://sources.debian.org/src/sqlite3/3.46.1-1/debian/rules/#line43
                    213: # Fedora does not: https://src.fedoraproject.org/rpms/sqlite/blob/182717934c83e9d3ec80f9f818961fd21640c964/f/sqlite.spec#_189
                    214: # FreeBSD does not: https://cgit.freebsd.org/ports/tree/databases/sqlite3/Makefile?id=8d38e8fbf53dfc94507a466b7269b38a55b167ac#n70
                    215: # Homebrew does not: https://github.com/Homebrew/homebrew-core/blob/f6ac42c098379841c21ed3a30e150f26187f34b1/Formula/s/sqlite.rb#L35-L58
                    216: # OpenBSD does not: https://cvsweb.openbsd.org/ports/databases/sqlite3/Makefile?rev=1.132&content-type=text/x-cvsweb-markup
                    217: #
                    218: # https://www.sqlite.org/compile.html#enable_normalize
                    219: 
                    220: # SQLITE_ENABLE_NULL_TRIM -- minor on-disk space optimization with some
                    221: # compatibility issues and potentially blob API bugs.  We will let
                    222: # sleeping dogs lie here.
                    223: #
                    224: # https://www.sqlite.org/compile.html#enable_null_trim
                    225: 
                    226: # XXX Consider -DSQLITE_ENABLE_OFFSET_SQL_FUNC.
                    227: #
                    228: # Unclear what applications need this.  Gentoo and Fedora enable this;
                    229: # others I checked do not.
                    230: #
                    231: #      This option enables support for the sqlite_offset(X) SQL
                    232: #      function.
                    233: #
                    234: #      The sqlite_offset(X) SQL function requires a new interface on
                    235: #      the B-tree storage engine, a new opcode in the virtual machine
                    236: #      that runs SQL statements, and a new conditional in a critical
                    237: #      path of the code generator.  To avoid that overhead in
                    238: #      applications that do not need the utility of sqlite_offset(X),
                    239: #      the function is disabled by default.
                    240: #
                    241: # https://www.sqlite.org/compile.html#enable_offset_sql_func
                    242: #
                    243: #      The sqlite_offset(X) function returns the byte offset in the
                    244: #      database file for the beginning of the record from which value
                    245: #      would be read.  If X is not a column in an ordinary table, then
                    246: #      sqlite_offset(X) returns NULL.  The value returned by
                    247: #      sqlite_offset(X) might reference either the original table or
                    248: #      an index, depending on the query.  If the value X would
                    249: #      normally be extracted from an index, the sqlite_offset(X)
                    250: #      returns the offset to the corresponding index record.  If the
                    251: #      value X would be extracted from the original table, then
                    252: #      sqlite_offset(X) returns the offset to the table record.
                    253: #
                    254: # https://www.sqlite.org/lang_corefunc.html#sqlite_offset
                    255: 
                    256: # XXX Consider SQLITE_ENABLE_ORDERED_SET_AGGREGATES.
                    257: #
                    258: #      This option enables support for the "WITHIN GROUP ORDER BY"
                    259: #      ordered-set aggregate syntax.  For example:
                    260: #
                    261: #          SELECT percentile_cont(0.75) WITHIN GROUP (ORDER BY x) FROM tab;
                    262: #
                    263: #      The above is the SQL-standard way to compute the 75-percentile
                    264: #      value of a distribution.  The usual way to do this in SQLite is
                    265: #      as follows:
                    266: #
                    267: #          SELECT percentile_cont(x,0.75) FROM tab;
                    268: #
                    269: #      Though simpler, easier to read, and easier to type, this syntax
                    270: #      is not compliant with standard SQL.  The simpler, non-standard
                    271: #      syntax is always available in SQLite.  But the SQL-standard
                    272: #      compliant syntax is only available if compiled using
                    273: #      -DSQLITE_ENABLE_ORDERED_SET_AGGREGATES.  The SQL-standard
                    274: #      compliant syntax is disabled by default because (A) it requires
                    275: #      about 1,200 bytes of extra code in the compiled SQLite binary
                    276: #      and (B) because it makes your SQL code more difficult to read,
                    277: #      write, and understand without adding any value.  Use this
                    278: #      option only if you need to write cross-platform SQL that uses
                    279: #      ordered-set aggregate functions such as percentile_cont().
                    280: #
                    281: # This might be useful for generic database wrappers that use this
                    282: # package for a sqlite3 backend.  But nobody else seems to enable this.
                    283: # So let's hold off until the need arises.
                    284: #
                    285: # https://www.sqlite.org/compile.html#enable_ordered_set_aggregates
                    286: 
                    287: # SQLITE_ENABLE_PREUPDATE_HOOK, SQLITE_ENABLE_SESSION -- enables the
                    288: # sqlite3_preupdate_* for pre-update hooks, and the sqlite3session_*
                    289: # APIs for reifying changesets.
                    290: #
                    291: # https://www.sqlite.org/c3ref/preupdate_blobwrite.html
                    292: # https://www.sqlite.org/sessionintro.html
                    293: # https://www.sqlite.org/compile.html#enable_preupdate_hook
                    294: # https://www.sqlite.org/compile.html#enable_session
                    295: CONFIGURE_ARGS+=       --enable-session
                    296: 
                    297: # SQLITE_ENABLE_QPSG -- query planner stability guarantee.  Off by
                    298: # default.  This option turns it on by default.  Applications can
                    299: # always use sqlite3_db_config(SQLITE_DBCONFIG_ENABLE_QPSG) to enable
                    300: # it at run-time, so no need for us to build sqlite3 with it.
                    301: #
                    302: # https://www.sqlite.org/queryplanner-ng.html#qpstab
                    303: # https://www.sqlite.org/compile.html#enable_qpsg
                    304: 
                    305: # XXX Consider SQLITE_ENABLE_RBU, Resumable Bulk Updates.
                    306: #
                    307: # Gentoo enables this; nobody else I found does.
                    308: #
                    309: # https://www.sqlite.org/rbu.html
                    310: # https://www.sqlite.org/compile.html#enable_rbu
                    311: 
                    312: # XXX Consider SQLITE_ENABLE_SNAPSHOT, write-ahead log snapshots.
                    313: #
                    314: # Unclear what applications might use this.  Nobody else seems to
                    315: # enable this.
                    316: #
                    317: # https://www.sqlite.org/c3ref/snapshot.html
                    318: # https://www.sqlite.org/compile.html#enable_snapshot
                    319: 
                    320: # SQLITE_ENABLE_SORTER_REFERENCES -- potential optimization whose value
                    321: # is not clear, off by default.
                    322: #
                    323: # https://www.sqlite.org/compile.html#enable_sorter_references
                    324: 
                    325: # SQLITE_ENABLE_STMT_SCANSTATUS -- enables sqlite3_stmt_scanstatus and
                    326: # sqlite3_stmt_scanstatus_v2.
                    327: #
                    328: #       Those interfaces are normally omitted from the build because
                    329: #       they imposes a performance penalty, even on statements that do
                    330: #       not use the feature.
                    331: #
                    332: # https://www.sqlite.org/c3ref/stmt_scanstatus.html
                    333: # https://www.sqlite.org/compile.html#enable_stmt_scanstatus
                    334: 
                    335: # The SQLITE_STMT virtual table provides information about all prepared
                    336: # statements associated with the database connection.  This is likely
                    337: # to be useful for performance analysis of applications and does not
                    338: # appear to have any performance penalty for applications that don't
                    339: # use it.
                    340: #
                    341: # https://www.sqlite.org/stmt.html
                    342: # https://www.sqlite.org/compile.html#enable_stmtvtab
                    343: CFLAGS+=               -DSQLITE_ENABLE_STMTVTAB
                    344: 
                    345: # SQLITE_RTREE_INT_ONLY
                    346: #
                    347: #      This compile-time option is deprecated and untested.
                    348: #
                    349: # https://www.sqlite.org/compile.html#rtree_int_only
                    350: 
                    351: # SQLITE_ENABLE_SQLLOG
                    352: #
                    353: #      This option enables extra code (especially the
                    354: #      SQLITE_CONFIG_SQLLOG option to sqlite3_config()) that can be
                    355: #      used to create logs of all SQLite processing performed by an
                    356: #      application.
                    357: #
                    358: # Unclear what applications use this or what it does beyond
                    359: # sqlite3_trace_v2 (https://www.sqlite.org/c3ref/trace_v2.html).  Can't
                    360: # find anyone else who enables this.
                    361: #
                    362: # https://www.sqlite.org/c3ref/c_config_covering_index_scan.html#sqliteconfigsqllog
                    363: # https://www.sqlite.org/compile.html#enable_sqllog
                    364: 
                    365: # SQLITE_ENABLE_STAT2, SQLITE_ENABLE_STAT3, SQLITE_ENABLE_STAT4 --
                    366: # statistics tables created by the ANALYZE command.
                    367: # SQLITE_ENABLE_STAT2 and SQLITE_ENABLE_STAT3 are now ignored.
                    368: # SQLITE_ENABLE_STAT4 is not enabled by default and it's unclear what
                    369: # the performance implications are, but it appears likely to expand
                    370: # disk usage and potentially break the query planner stability
                    371: # guarantee, so we'll leave it off for now.
                    372: #
                    373: # https://www.sqlite.org/fileformat2.html#stat4tab
                    374: # https://www.sqlite.org/compile.html#enable_stat2
                    375: # https://www.sqlite.org/compile.html#enable_stat3
                    376: # https://www.sqlite.org/compile.html#enable_stat4
                    377: 
                    378: # SQLITE_ENABLE_TREE_EXPLAIN
                    379: #
                    380: #      This compile-time option is no longer used.
                    381: #
                    382: # https://www.sqlite.org/compile.html#enable_tree_explain
                    383: 
                    384: # XXX Consider SQLITE_ENABLE_UPDATE_DELETE_LIMIT:
                    385: #
                    386: #      This option enables an optional ORDER BY and LIMIT clause on
                    387: #      UPDATE and DELETE statements.
                    388: #
                    389: # Unclear what applications might rely on this.  Debian and Gentoo
                    390: # enable this by default; others do not.
                    391: #
                    392: # https://www.sqlite.org/compile.html#enable_update_delete_limit
                    393: 
                    394: # XXX Consider SQLITE_ENABLE_UNKNOWN_SQL_FUNCTION -- enables the
                    395: # `unknown()' function for (and only for) EXPLAIN or EXPLAIN QUERY
                    396: # PLAN, as a substitute for any functions sqlite3 does not recognize.
                    397: #
                    398: #      When used in the command-line shell, the
                    399: #      SQLITE_ENABLE_UNKNOWN_SQL_FUNCTION feature allows SQL text that
                    400: #      contains application-defined functions to be pasted into the
                    401: #      shell for analysis and debugging without having to create and
                    402: #      load an extension that implements the application-defined
                    403: #      functions.
                    404: #
                    405: # However, this might be useful _only_ for the command-line shell;
                    406: # unclear what applications might rely on failure vs unknown().
                    407: #
                    408: # https://www.sqlite.org/compile.html#enable_unknown_sql_function
                    409: 
                    410: # SQLITE_ENABLE_UNLOCK_NOTIFY -- enables sqlite3_unlock_notify(),
                    411: # needed for various sqlite3 API calls to sleep rather than fail with
                    412: # SQLITE_LOCKED when another thread is using another connection to the
                    413: # same database, so they can be woken by the other thread when it is
                    414: # done.  Needed by, e.g., Firefox.
                    415: #
                    416: # https://www.sqlite.org/unlock_notify.html
                    417: # https://www.sqlite.org/compile.html#enable_unlock_notify
                    418: CFLAGS+=               -DSQLITE_ENABLE_UNLOCK_NOTIFY
                    419: 
                    420: # SQLITE_INTROSPECTION_PRAGMAS
                    421: #
                    422: #      This option is obsolete.
                    423: #
                    424: # https://www.sqlite.org/compile.html#introspection_pragmas
                    425: 
                    426: # XXX Consider SQLITE_SOUNDEX:
                    427: #
                    428: #      This option enables the soundex() SQL function.
                    429: #
                    430: # Debian and Gentoo enable this by default; others do not.
                    431: #
                    432: # https://www.sqlite.org/lang_corefunc.html#soundex
                    433: # https://www.sqlite.org/compile.html#soundex
                    434: 
                    435: # XXX Consider SQLITE_STRICT_SUBTYPE=1:
                    436: #
                    437: #      This option causes application-defined SQL functions to raise
                    438: #      an SQL error if they invoke the sqlite3_result_subtype()
                    439: #      interface but where not registered with the
                    440: #      SQLITE_RESULT_SUBTYPE property.  This recommended option helps
                    441: #      to identify problems in the implementation of
                    442: #      application-defined SQL functions early in the development
                    443: #      cycle.
                    444: #
                    445: # Debian and FreeBSD enable this; others do not.
                    446: #
                    447: # https://www.sqlite.org/compile.html#strict_subtype
                    448: 
                    449: # XXX Consider SQLITE_USE_ALLOCA:
                    450: #
                    451: #      If this option is enabled, then the alloca() memory allocator
                    452: #      will be used in a few situations where it is appropriate.  This
                    453: #      results in a slightly smaller and faster binary.  The
                    454: #      SQLITE_USE_ALLOCA compile-time only works, of course, on
                    455: #      systems that support alloca().
                    456: #
                    457: # Nobody else seems to enable this.
                    458: #
                    459: # https://www.sqlite.org/compile.html#use_alloca
                    460: 
                    461: # XXX Consider SQLITE_USE_FCNTL_TRACE:
                    462: #
                    463: #      This option causes SQLite to issue extra SQLITE_FCNTL_TRACE
                    464: #      file controls to provide supplementary information to the VFS.
                    465: #      The "vfslog.c" extension makes use of this to provide enhanced
                    466: #      logs of VFS activity.
                    467: #
                    468: # Nobody else seems to enable this.  Unclear what applications this
                    469: # benefits.
                    470: #
                    471: # https://www.sqlite.org/compile.html#use_fcntl_trace
                    472: 
                    473: # SQLITE_USE_SEH
                    474: #
                    475: #      Client code should not use this define, as it is used
                    476: #      internally by the library.
                    477: #
                    478: # https://www.sqlite.org/compile.html#use_seh
                    479: 
                    480: # XXX Consider SQLITE_HAVE_ZLIB:
                    481: #
                    482: #      This option has no effect on the SQLite core.  It is only used
                    483: #      by extensions.  This is option is necessary for the compression
                    484: #      and decompression functions that are part of SQL Archive
                    485: #      support in the command-line shell.
                    486: #
                    487: # https://www.sqlite.org/compile.html#have_zlib
                    488: 
                    489: # XXX Consider YYTRACKMAXSTACKDEPTH:
                    490: #
                    491: #      This option causes the LALR(1) parser stack depth to be tracked
                    492: #      and reported using the
                    493: #      sqlite3_status(SQLITE_STATUS_PARSER_STACK,...)  interface.
                    494: #      SQLite's LALR(1) parser has a fixed stack depth (determined at
                    495: #      compile-time using the YYSTACKDEPTH options).  This option can
                    496: #      be used to help determine if an application is getting close to
                    497: #      exceeding the maximum LALR(1) stack depth.
                    498: 
                    499: # SQLITE_OMIT_LOAD_EXTENSION (old: !SQLITE_ENABLE_LOAD_EXTENSION)
                    500: #
                    501: # Make sure this is consistently enabled on all platforms -- this way
                    502: # the build fails early if something goes wrong with getting at dlopen.
                    503: # (XXX If we have platforms without dlopen, we may want to disable this
                    504: # on those platforms.)
                    505: #
                    506: # https://www.sqlite.org/compile.html#omit_load_extension
                    507: CONFIGURE_ARGS+=       --enable-load-extension
1.29      tnn       508: 
1.16      epg       509: # Uses dlopen and friends but doesn't use -ldl on Linux.
                    510: # See http://www.sqlite.org/cvstrac/tktview?tn=3555
                    511: LIBS+=                 ${BUILDLINK_LDADD.dl}
                    512: 
1.161     riastrad  513: # Solaris needs -lrt for nanosleep, PR pkg/58714
1.156     nia       514: LIBS.SunOS+=           -lrt
                    515: 
1.80      ryoon     516: .if ${OS_VARIANT} == "SCOOSR5"
                    517: LDFLAGS.SCO_SV+=       -lpthread
                    518: .endif
                    519: 
1.127     sevan     520: .include "../../mk/pthread.buildlink3.mk"
1.67      ryoon     521: .include "../../mk/readline.buildlink3.mk"
1.16      epg       522: .include "../../mk/dlopen.buildlink3.mk"
1.1       tv        523: .include "../../mk/bsd.pkg.mk"

CVSweb <webmaster@jp.NetBSD.org>