From: Yuri Khan <yuri.v.khan@gmail.com>
To: rms@gnu.org
Cc: chad <yandros@gmail.com>, eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: [PROPOSAL] Builder, a build system integration for Emacs
Date: Sat, 27 May 2023 16:45:41 +0700 [thread overview]
Message-ID: <CAP_d_8XAy+FNbxLA9h_cFHiS3WsVffPRU7cm+Xiqpe0k6soj-Q@mail.gmail.com> (raw)
In-Reply-To: <E1q2f35-0002RB-S6@fencepost.gnu.org>
On Sat, 27 May 2023 at 04:33, Richard Stallman <rms@gnu.org> wrote:
> So when you say to link a certain program, the library-choosing
> systems figures out which of the libraries in that collection provide
> symbols that the program needs. And it links with them.
It does not work that way. No build system I have used recently, and
maybe ever, solves for you equations like “I want symbols x, y, and z,
find me a set of libraries to link with”.
The author of a program selects libraries to work with and specifies
them explicitly in the program build configuration. If those
libraries, in turn, depend on other libraries, a build system resolves
the full transitive closure of dependencies. If the program and each
library specify constraints on versions of their dependencies, the
build system is expected to validate that they are all satisfied,
and/or to find a set of versions that together satisfy all
constraints.
Checking library licenses for mutual compatibility and for
compatibility with the program’s intended license is solely the
programmer’s responsibility.
next prev parent reply other threads:[~2023-05-27 9:45 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 10:21 [PROPOSAL] Builder, a build system integration for Emacs BTuin
2023-05-21 12:11 ` Philip Kaludercic
2023-05-21 14:56 ` Augustin Chéneau (BTuin)
2023-05-21 17:24 ` Jim Porter
2023-05-21 19:33 ` Augustin Chéneau (BTuin)
2023-05-21 19:58 ` Jim Porter
2023-05-21 21:36 ` John Yates
2023-05-22 16:35 ` Augustin Chéneau (BTuin)
2023-05-23 0:44 ` Po Lu
2023-05-23 21:10 ` Augustin Chéneau (BTuin)
2023-05-23 21:17 ` Óscar Fuentes
2023-05-24 6:09 ` Dirk-Jan C. Binnema
2023-05-24 21:35 ` Richard Stallman
2023-05-24 23:32 ` Jim Porter
2023-05-25 0:11 ` Gregory Heytings
2023-05-25 4:00 ` tomas
2023-05-25 6:53 ` Gregory Heytings
2023-05-25 7:48 ` Eli Zaretskii
2023-05-25 9:33 ` Gregory Heytings
2023-05-25 11:28 ` Eli Zaretskii
2023-05-25 11:53 ` Gregory Heytings
2023-05-25 13:09 ` Eli Zaretskii
2023-05-25 14:36 ` Gregory Heytings
2023-05-25 16:20 ` Eli Zaretskii
2023-05-25 16:40 ` tomas
2023-05-25 19:23 ` Gregory Heytings
2023-05-26 0:57 ` Po Lu
2023-05-27 0:24 ` Gregory Heytings
2023-05-26 5:57 ` Eli Zaretskii
2023-05-26 21:16 ` Richard Stallman
2023-05-27 0:25 ` Gregory Heytings
2023-05-28 10:20 ` Madhu
2023-05-28 12:38 ` Po Lu
2023-05-29 22:03 ` Gregory Heytings
2023-05-29 22:42 ` Po Lu
2023-05-30 7:26 ` Gregory Heytings
2023-05-30 12:54 ` Po Lu
2023-05-30 15:08 ` Gregory Heytings
2023-05-30 16:50 ` chad
2023-05-31 1:14 ` Po Lu
2023-06-05 1:09 ` Gregory Heytings
2023-06-05 5:29 ` Po Lu
2023-06-05 8:17 ` Gregory Heytings
2023-06-05 9:06 ` Po Lu
2023-06-17 3:34 ` Yilkal Argaw
2023-05-27 14:55 ` Brian Cully via Emacs development discussions.
2023-05-26 0:54 ` Po Lu
2023-05-26 21:16 ` Richard Stallman
2023-05-27 0:26 ` Gregory Heytings
2023-05-27 2:37 ` Ruijie Yu via Emacs development discussions.
2023-05-28 21:48 ` Richard Stallman
2023-05-29 22:05 ` Gregory Heytings
2023-05-30 13:01 ` Po Lu
2023-05-30 15:08 ` Gregory Heytings
2023-05-31 1:16 ` Po Lu
2023-06-02 21:38 ` Richard Stallman
2023-06-05 1:10 ` Gregory Heytings
2023-06-05 5:19 ` Po Lu
2023-06-05 8:17 ` Gregory Heytings
2023-06-05 9:00 ` Po Lu
2023-05-31 22:28 ` Richard Stallman
2023-05-30 21:52 ` Richard Stallman
2023-05-28 21:48 ` Richard Stallman
2023-05-25 13:16 ` chad
2023-05-25 19:38 ` Augustin Chéneau (BTuin)
2023-05-26 21:32 ` Richard Stallman
2023-05-27 9:45 ` Yuri Khan [this message]
2023-05-28 21:48 ` Richard Stallman
2023-05-29 8:03 ` Yuri Khan
2023-05-30 21:47 ` Richard Stallman
2023-05-25 7:55 ` tomas
2023-05-25 8:44 ` Gregory Heytings
2023-05-25 10:38 ` Po Lu
2023-05-25 11:44 ` Gregory Heytings
2023-05-25 12:02 ` Po Lu
2023-05-25 12:08 ` Gregory Heytings
2023-05-26 0:52 ` Po Lu
2023-05-26 21:16 ` Richard Stallman
2023-05-27 0:26 ` Gregory Heytings
2023-05-28 21:47 ` Richard Stallman
2023-05-29 22:05 ` Gregory Heytings
2023-05-30 13:03 ` Po Lu
2023-05-31 22:29 ` Richard Stallman
2023-05-26 22:59 ` Lynn Winebarger
2023-05-28 21:22 ` Björn Bidar
2023-05-29 22:38 ` Richard Stallman
2023-05-29 22:38 ` Richard Stallman
2023-05-30 4:28 ` tomas
2023-05-25 10:42 ` Po Lu
2023-05-25 19:36 ` Augustin Chéneau (BTuin)
2023-05-22 22:00 ` Richard Stallman
2023-05-23 8:36 ` Philip Kaludercic
2023-05-23 11:18 ` Eli Zaretskii
2023-05-23 12:13 ` Po Lu
2023-05-23 18:46 ` Augustin Chéneau (BTuin)
2023-05-24 6:32 ` Juri Linkov
2023-05-24 20:09 ` Augustin Chéneau (BTuin)
2023-05-24 3:34 ` David Masterson
2023-05-24 10:26 ` Philip Kaludercic
2023-05-28 21:17 ` Björn Bidar
-- strict thread matches above, loose matches on Subject: below --
2023-05-27 7:12 [PROPOSAL] " Payas Relekar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP_d_8XAy+FNbxLA9h_cFHiS3WsVffPRU7cm+Xiqpe0k6soj-Q@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=yandros@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).