Home | History | Annotate | Download | only in autosetup

Lines Matching defs:soname

351         # soname: https://sqlite.org/src/forumpost/5a3b44f510df8ded
352 soname:=legacy
353 => {SONAME for libsqlite3.so. "none", or not using this flag, sets no
354 soname. "legacy" sets it to its historical value of
358 e.g. --soname=9.10 equates to "libsqlite3.so.9.10".}
438 #lappend allFlags just-testing {{*} {soname:=duplicateEntry => {x}}}
515 sqlite-handle-soname
889 # "soname" for libsqlite3.so. See discussion at:
891 proc sqlite-handle-soname {} {
893 if {[proj-opt-was-provided soname]} {
894 set soname [join [opt-val soname] ""]
896 # Enabling soname breaks linking for the --dynlink-tools feature,
897 # and this project has no direct use for soname, so default to
899 # soname.
900 set soname none
902 switch -exact -- $soname {
904 legacy { set soname libsqlite3.so.0 }
906 if {[string match libsqlite3.* $soname]} {
910 set soname "libsqlite3.so.${soname}"
914 proc-debug "soname=$soname"
915 if {[proj-check-soname $soname]} {
916 define LDFLAGS_LIBSQLITE3_SONAME [get-define LDFLAGS_SONAME_PREFIX]$soname
917 msg-result "Setting SONAME using: [get-define LDFLAGS_LIBSQLITE3_SONAME]"
918 } elseif {[proj-opt-was-provided soname]} {
919 # --soname was explicitly requested but not available, so fail fatally
920 proj-fatal "This environment does not support SONAME."
922 # --soname was not explicitly requested but not available, so just warn
923 msg-result "This environment does not support SONAME."