From nobody Wed Nov 16 02:06:41 2022 X-Original-To: freebsd-database@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4NBmdl26TNz4hCLj for ; Wed, 16 Nov 2022 02:07:23 +0000 (UTC) (envelope-from archimedes.gaviola@gmail.com) Received: from mail-yw1-x1136.google.com (mail-yw1-x1136.google.com [IPv6:2607:f8b0:4864:20::1136]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NBmdl1S6qz3tX2 for ; Wed, 16 Nov 2022 02:07:23 +0000 (UTC) (envelope-from archimedes.gaviola@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-x1136.google.com with SMTP id 00721157ae682-36cbcda2157so154556767b3.11 for ; Tue, 15 Nov 2022 18:07:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=7DFg05bmHu2R705rMVnDP2SnCI/Bv6ksb7ZhkddTlvA=; b=Ux1tmDH0Q7xoXPzWMMVpu08ygIkOQoKbK22pVVzVUJGpOgjdh/kLVLENzTS3ta0TST gWgxdmYGpqObskYfbhckjMC6scm68TQG2xj7BDDMuewe1x7zjhdMwnxhfWbyOjCm42w2 Ztc03AR2o3XdWQmBEpfD8nAbfZV0PyZKDIm5DwtlhLQA/zDKt5Fds+Tz981xvo7+gAC8 L/nUXzVDlptn0ERjKSUrMLIbaxTpXxfkKkhqLJleXYB4zGsTNs9wWVHc2G7L42PzjpXR UG/zd6wSLDlGjOQi6GLa7PqmP15/OItD6DH/+D85kFH13o2j/MQLgivgtf7F7M/HMVN4 kEWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=7DFg05bmHu2R705rMVnDP2SnCI/Bv6ksb7ZhkddTlvA=; b=da5MZM1h2HO+az9PXb5sqG4fQGgjVGetTrmg0n9fK7wU6hrtXOYOMezGYyvT2NGoWy ZMflc3p0iXFOSprJN2GpOAvaFFU5Lrvqy1ccjXnWne3ALVgfDo+uZdaS9yfp0LSvgIS/ 5AXjKFbpvISetnwM6WaxMlCsQM+z1gfLQ6FeCxq9ZJASmQZo0JuBxds7+XgH9jxZMY3+ uHBnKWwZmTe2jr+8/nbrw+1dqoF2Oa41VfWXHTJNQteNEyYq50JksfLKCgw12IkHD61u QYG2+QkiAoL6b70HYuy3GEC9PHTIAAEBiQthfQRNyyfvigLQhHcqMq0IFa8t4J/GM3S3 K7wA== X-Gm-Message-State: ANoB5pnJrQ0yn78SQe/w8qoblC+Nrrysalbx8Idekj3/cvk1pFBBSica ZyXYyWUb+PBIFSIPX514GKxX8VqwuDWfg4pNblWZPX8o X-Google-Smtp-Source: AA0mqf5B8UjQQvyx7/qsJLLd4QQ2oSTk+LuUpIpf4wIrVAAChhMhhoyd7tCjvHOkj2fOiGshcRGVnKYyUDT8rOWqhTc= X-Received: by 2002:a81:9911:0:b0:369:b8a9:8fc6 with SMTP id q17-20020a819911000000b00369b8a98fc6mr21075501ywg.53.1668564442530; Tue, 15 Nov 2022 18:07:22 -0800 (PST) List-Id: Database use and development under FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-database List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-database@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Archimedes Gaviola Date: Wed, 16 Nov 2022 10:06:41 +0800 Message-ID: Subject: Re: Include SQLite3 source upon buildworld To: Xin LI Cc: freebsd-database@freebsd.org Content-Type: multipart/alternative; boundary="000000000000e1c76f05ed8cee9e" X-Rspamd-Queue-Id: 4NBmdl1S6qz3tX2 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000e1c76f05ed8cee9e Content-Type: text/plain; charset="UTF-8" On Wed, Nov 16, 2022 at 1:48 AM Xin LI wrote: > > > 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? >> > Hi Xin Li, > 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. > Okay, nice! I'm so glad that it can be done. My goal is to make SQLite3 be part of the base system in a customized FreeBSD build to make it embedded. I am checking the version and it's updated 3.93.3 as I'm using the 14.0-CURRENT. I need to figure-out this BSD make and glues you've mentioned to make this happen. 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. > Oh I see, now I know its purpose. Currently, I have my system installed with SQLite3 via package install 'pkg install sqlite3' and it works very well but because this time I want something embeddable. It so happened that I was checking the source and surprisingly found sqlite3. Anyway, let me explore and try. Thanks and best regards, Archimedes --000000000000e1c76f05ed8cee9e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, Nov 16, 2022 at 1:48 AM Xin L= I <delphij@gmail.com> wrote:=


On Tue, Nov 15, 2022 at 5:16 AM Archimedes Gaviola <archimedes.gaviola@gmail.com= > wrote:
=
Hi,

There's an SQLite3 s= ource located in the=20 /usr/src/contrib/sqlite3. Is there a way to include this upon buildworld so= that I can run the binary after compiling?
<= /div>

Hi Xin Li,
=C2= =A0
Yes and no.

Yes -- you can always com= pile shell.c source and link against the library; the code is there, just t= he BSD make build glues are missing.
Okay, nice! I'm so glad that it can be done. My goal is to = make SQLite3 be part of the base system in a customized FreeBSD build to ma= ke it embedded. I am checking the version and it's updated 3.93.3 as I&= #39;m using the 14.0-CURRENT. I need to figure-out this BSD make and glues = you've mentioned to make this happen.

No -- the omission= is intentional: the library is meant to be used by the base system as a &q= uot;private library", which gives us the flexibility to not give a sta= ble API/ABI promise and to only build with options that the base system nee= ded (to reduce attack surface), so that when we make an update, it will be = a "wholesale" update and user applications are not broken, even i= f sqlite3 update have introduced one.=C2=A0 Users who want sqlite3 should r= eally install it from ports (databases/sqlite3) or package.

Oh I see, now I know its purpose. Curren= tly, I have my system installed with SQLite3 via package install 'pkg i= nstall sqlite3' and it works very well but because this time I want som= ething embeddable. It so happened that I was checking the source and surpri= singly found sqlite3. Anyway, let me explore and try.

<= div>Thanks and best regards,
Archimedes=C2=A0
--000000000000e1c76f05ed8cee9e--