Re: Precompiled Emacs

[Phillip Lord]

But you don't say why!

If you want to build a prebuilt binary which will install in a sane way,
then building something for the appropriate package management system
seems the sensible way. Your only stated aim (fast installations,
multiple versions) is fulfilled with this solution.

But, emacs packages already exist for most distributions. So using one
of these makes most sense. Unless you want to extend and modify emacs in
some way; but if you want to do this, then, probably package.el will be
enough.

Phil




Johan Andersson <johan.rejeep@gmail.com> writes:

>> You don't say what distribution you are working with.
>
> Any, that's the idea.
>
>
> On Mon, Nov 4, 2013 at 9:25 AM, Jambunathan K <kjambunathan@gmail.com>wrote:
>
>>
>> You don't say what distribution you are working with.  Why not mess
>> around with the distributed deb-srcs and make a custom .deb out of it.
>>
>> As you see below, you can choose one among the many different
>> alternatives for emacs.
>>
>> kjambunathan@debian-6:/usr/bin$ ls -al | grep emacs
>>    5792 Dec 11  2010 b2m.emacs23
>>   82760 Dec 11  2010 ctags.emacs23
>>    3309 Aug  7  2010 dh_installemacsen
>>   34780 Dec 11  2010 ebrowse.emacs23
>>      23 Aug 18 15:54 emacs -> /etc/alternatives/emacs
>>       9 Aug 18 15:54 emacs23 -> emacs23-x
>> 6583560 Dec 11  2010 emacs23-x
>>      29 Aug 18 15:54 emacsclient -> /etc/alternatives/emacsclient
>>   16816 Dec 11  2010 emacsclient.emacs23
>>   81064 Dec 11  2010 etags.emacs23
>>    7294 Dec 11  2010 grep-changelog.emacs23
>>    3983 Dec 11  2010 rcs-checkin.emacs23
>>
>>
>> Johan Andersson <johan.rejeep@gmail.com> writes:
>>
>> > Well, the thing is that I don't want to install it there. I guess it's
>> not
>> > possible to compile Emacs, archive it, move to another machine and there
>> > "make install" to the desired prefix?
>> >
>> > The purpose of this is to allow for fast installations and at the same
>> time
>> > allow for multiple Emacs version. So that will not work with
>> > "/usr/local/emacs".
>> >
>> > I guess I could do:
>> >
>> > $ ./configure --prefix /usr/local/emacs-x.y.z --without-all --without-x
>> > $ make bootstrap
>> > $ tar ...
>> >
>> > ... move to another system
>> >
>> > $ make install
>> >
>> > That would mean a larger tar-file. But I guess I could "make install" on
>> > the compile system and then tar "/usr/local/emacs-x.y.z".
>> >
>> > Still... seems a bit weird that this limitation exists. Maybe there's a
>> > good reason for it?
>> >
>> >
>> > On Sun, Nov 3, 2013 at 10:43 PM, Kai Großjohann <kai.grossjohann@gmx.net
>> >wrote:
>> >
>> >> Johan Andersson wrote:
>> >> > I've read the instructions in INSTALL, which are very good. I tried
>> and
>> >> did
>> >> > a build with:
>> >> >
>> >> > $ ./configure --prefix emacs-install --without-all --without-x
>> >>
>> >> The assumption is that the argument of --prefix is the fully qualified
>> >> directory name where Emacs is installed.  If you omit --prefix, it will
>> >> use /usr/local.
>> >>
>> >> Conventionally, people are expected to use values such as
>> >> /usr/local/emacs or /opt/emacs or something.
>> >>
>> >> Kai
>> >>
>> >>
>>
>
>

-- 
Phillip Lord,                           Phone: +44 (0) 191 222 7827
Lecturer in Bioinformatics,             Email: phillip.lord@newcastle.ac.uk
School of Computing Science,            
http://homepages.cs.ncl.ac.uk/phillip.lord
Room 914 Claremont Tower,               skype: russet_apples
Newcastle University,                   twitter: phillord
NE1 7RU