Date: Tue, 15 Nov 2022 09:47:52 -0800 From: Xin LI <delphij@gmail.com> To: Archimedes Gaviola <archimedes.gaviola@gmail.com> Cc: freebsd-database@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Include SQLite3 source upon buildworld Message-ID: <CAGMYy3u3ocKJ713m=m2qHXBTQxynMt=LWQiN99yYDo6KQuDTGg@mail.gmail.com> In-Reply-To: <CAJFbk7H4cgZn6Cy4m6uMZhZKe93mMtHb6afbVb8YDrQwJ2FBtA@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Tue, Nov 15, 2022 at 5:16 AM Archimedes Gaviola < archimedes.gaviola@gmail.com> wrote: > Hi, > > There's an SQLite3 source located in the /usr/src/contrib/sqlite3. Is > there a way to include this upon buildworld so that I can run the binary > after compiling? > Yes and no. Yes -- you can always compile shell.c source and link against the library; the code is there, just the BSD make build glues are missing. No -- the omission is intentional: the library is meant to be used by the base system as a "private library", which gives us the flexibility to not give a stable API/ABI promise and to only build with options that the base system needed (to reduce attack surface), so that when we make an update, it will be a "wholesale" update and user applications are not broken, even if sqlite3 update have introduced one. Users who want sqlite3 should really install it from ports (databases/sqlite3) or package. [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Nov 15, 2022 at 5:16 AM Archimedes Gaviola <<a href="mailto:archimedes.gaviola@gmail.com">archimedes.gaviola@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi,</div><div><br></div><div>There's an SQLite3 source located in the /usr/src/contrib/sqlite3. Is there a way to include this upon buildworld so that I can run the binary after compiling?</div></div></blockquote><div><br></div><div class="gmail_default" style="font-family:monospace,monospace">Yes and no.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">Yes -- you can always compile shell.c source and link against the library; the code is there, just the BSD make build glues are missing.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">No -- the omission is intentional: the library is meant to be used by the base system as a "private library", which gives us the flexibility to not give a stable API/ABI promise and to only build with options that the base system needed (to reduce attack surface), so that when we make an update, it will be a "wholesale" update and user applications are not broken, even if sqlite3 update have introduced one. Users who want sqlite3 should really install it from ports (databases/sqlite3) or package.</div></div></div>help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGMYy3u3ocKJ713m=m2qHXBTQxynMt=LWQiN99yYDo6KQuDTGg>