From: Alex Corcoles <alex@corcoles.net>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Interest in a Cosmopolitan build?
Date: Fri, 10 Nov 2023 11:10:27 +0100 [thread overview]
Message-ID: <b05f94252e2306c0a5de9c8d22259b098e1449cb.camel@corcoles.net> (raw)
In-Reply-To: <E1r1Hcy-000471-1i@fencepost.gnu.org>
Hi,
> > If I understand correctly, they found a way to make something
> that fits
> > all executable formats that major OSs support, plus they embed a
> zip
> > with binaries and dependencies (e.g. parts of /usr/ for Emacs),
> plus
> > they even convinced the POSIX stewards to loosen up the
> definition of
> > what's an executable. Plus a new libc...
>
> Could you possibly explain concretely what "a new libc" means in
> this context? In what sense is it "new"? In what ways is it
> different from the existing libc that any POSIX system would have?
I am afraid I am a novice about systems programming, C, and
portability. I can quote parts from their README:
> Please note that the Cosmopolitan build configuration doesn't link
> any C/C++ library dependencies by default, so you still have the
> flexibility to choose the one provided by your system. If you'd
> prefer Cosmopolitan, just add $(LIBC) and $(CRT) to your linker
>arguments.
> The Cosmopolitan Library exports only the most stable canonical
> system calls for all supported operating systems, regardless of which
> platform is used for compilation. We polyfill many of the APIs, e.g.
> read(), write() so they work consistently everywhere while other
> apis, e.g. CreateWindowEx(), might only work on one platform, in
> which case they become no-op functions on others.
> Please note that, unlike Cygwin or MinGW, Cosmopolitan does not
> achieve broad support by bolting on a POSIX emulation layer. We do
> nothing more than (in most cases) stateless API translations that get
> you 90% of the way there in a fast lightweight manner. We therefore
> can't address some of the subtle differences, such as the nuances of
> absolute paths on Windows.
I can provide you further links, although they host their code on
GitHub. I'm happy to push it to some other Git forge, or host a tarball
of the source on a system of my own. I'm also happy to answer any other
question, although really I don't feel qualified for this discussion.
Not sure, though, if this remains on-topic for this list. Happy to
continue this discussion in some other place if needed.
Cheers,
Álex
next prev parent reply other threads:[~2023-11-10 10:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.37.1699462824.25818.emacs-devel@gnu.org>
2023-11-08 20:16 ` Interest in a Cosmopolitan build? Alex Corcoles
2023-11-10 2:52 ` Richard Stallman
2023-11-10 10:10 ` Alex Corcoles [this message]
2023-11-07 21:23 Alex Corcoles
2023-11-08 9:38 ` Emanuel Berg
2023-11-08 12:13 ` Eli Zaretskii
2023-11-08 14:54 ` Björn Bidar
2023-11-08 20:11 ` Alex Corcoles
2023-11-09 0:00 ` Po Lu
2023-11-09 5:44 ` Eli Zaretskii
2023-11-09 8:32 ` Po Lu
2023-11-09 8:47 ` Eli Zaretskii
2023-11-09 11:02 ` Alex Corcoles
2023-11-09 2:34 ` Richard Stallman
2023-11-09 10:56 ` Alex Corcoles
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=b05f94252e2306c0a5de9c8d22259b098e1449cb.camel@corcoles.net \
--to=alex@corcoles.net \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/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).