From: "Eli Zaretskii" <eliz@elta.co.il>
Subject: Re: Emacs for sites with different operating systems and CVS.
Date: Wed, 28 May 2003 07:48:03 +0300 [thread overview]
Message-ID: <2950-Wed28May2003074802+0300-eliz@elta.co.il> (raw)
In-Reply-To: <u4r3fedyt.fsf@hotpop.com> (message from Galen Boyer on 27 May 2003 23:05:18 -0500)
> From: Galen Boyer <galenboyer@hotpop.com>
> Newsgroups: gnu.emacs.help
> Date: 27 May 2003 23:05:18 -0500
>
> 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?
Because Windows users are used to get pre-compiled binaries. The main
reason for this is that Windows systems normally don't have a compiler
installed on them, so most Windows users cannot themselves build
Emacs.
OTOH, with the proliferation of Unix systems where the compiler is an
optional product not installed by default, perhaps the Unix version
should be a binary as well.
> 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 ...
The main issue to figure out is how to install Emacs so that it will
find all its files. Emacs (as well as other GNU packages) has the
names of the directories where to find files hard-coded into it. The
configure script takes care of creating a header file where those
directories are spelled out, as determined by the configuration
procedure. So the pre-compiled binary expects its Lisp, Info,
subprograms (such as etags), and other auxiliary files to be in
certain places; you must make sure that these directories exist on the
target system and the files Emacs looks for are in those directories.
(Of course, the usual Unix tricks with symlinks can help you out.)
Either that, or make sure that environment variables which override
the default locations of these files are all set appropriately on the
target system.
> 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?
I don't know of any docs about this, but the above kinda summarizes it
all. Feel free to ask more, though.
next prev parent reply other threads:[~2003-05-28 4:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 4:05 Emacs for sites with different operating systems and CVS Galen Boyer
2003-05-28 4:48 ` Eli Zaretskii [this message]
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=2950-Wed28May2003074802+0300-eliz@elta.co.il \
--to=eliz@elta.co.il \
/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).