From: Galen Boyer <galenboyer@hotpop.com>
Subject: Emacs for sites with different operating systems and CVS.
Date: 27 May 2003 23:05:18 -0500 [thread overview]
Message-ID: <u4r3fedyt.fsf@hotpop.com> (raw)
When maintaining Emacs for a site where users are on different
platforms, should you
Check in compiled code for each platform?
Check in source and give them the scripts to build for each platform?
Check in the tar file and let them untar to their directories while
just maintaining external packages?
I think the second option, but then why is there, seemingly, a specific
source tree for the windows Emacs? Are there different steps because
there are special files and such which therefore make it difficult to
build windows from the same source as Linux as ...
Is there anyplace I can go to know what I should do to build Emacs from
one source for multiple platforms, or do I dig through all of the notes
and such in the etc directory.
Are there any manuals and howtos as well as FAQs for site-admins?
--
Galen deForest Boyer
Sweet dreams and flying machines in pieces on the ground.
next reply other threads:[~2003-05-28 4:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 4:05 Galen Boyer [this message]
2003-05-28 4:48 ` Emacs for sites with different operating systems and CVS Eli Zaretskii
2003-05-28 7:03 ` Jason Rumney
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=u4r3fedyt.fsf@hotpop.com \
--to=galenboyer@hotpop.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.
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).