* generation of tramp-loaddefs
@ 2010-09-13 15:38 Juanma Barranquero
2010-09-13 15:49 ` Michael Albinus
0 siblings, 1 reply; 3+ messages in thread
From: Juanma Barranquero @ 2010-09-13 15:38 UTC (permalink / raw)
To: Emacs developers; +Cc: Michael Albinus
I'm porting this change to Windows:
2010-09-08 Michael Albinus <michael.albinus@gmx.de>
Migrate to Tramp 2.2. Rearrange load dependencies.
(Bug#1529, Bug#5448, Bug#5705)
* Makefile.in (TRAMP_DIR, TRAMP_SRC): New variables.
($(TRAMP_DIR)/tramp-loaddefs.el): New target.
(LOADDEFS): Add $(lisp)/net/tramp-loaddefs.el.
[...]
* net/tramp-compat.el (top): Require 'tramp-loaddefs. [...]
but AFAICS, this
TRAMP_DIR = $(lisp)/net
TRAMP_SRC = $(TRAMP_DIR)/tramp.el $(TRAMP_DIR)/tramp-cache.el \
[... etc...]
$(TRAMP_DIR)/tramp-loaddefs.el: $(TRAMP_SRC)
$(emacs) -l autoload \
--eval "(setq generate-autoload-cookie \";;;###tramp-autoload\")" \
--eval "(setq generated-autoload-file \"$@\")" \
--eval "(setq make-backup-files nil)" \
-f batch-update-autoloads $(TRAMP_DIR)
will update autoloads for *all* files in lisp/net/*, using
$(TRAMP_DIR)/tramp-loaddefs.el as autoload file. Or am I missing
something?
Juanma
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: generation of tramp-loaddefs
2010-09-13 15:38 generation of tramp-loaddefs Juanma Barranquero
@ 2010-09-13 15:49 ` Michael Albinus
2010-09-13 15:55 ` Juanma Barranquero
0 siblings, 1 reply; 3+ messages in thread
From: Michael Albinus @ 2010-09-13 15:49 UTC (permalink / raw)
To: Juanma Barranquero; +Cc: Emacs developers
Juanma Barranquero <lekktu@gmail.com> writes:
> I'm porting this change to Windows:
>
> 2010-09-08 Michael Albinus <michael.albinus@gmx.de>
>
> Migrate to Tramp 2.2. Rearrange load dependencies.
> (Bug#1529, Bug#5448, Bug#5705)
Thanks a lot!
> but AFAICS, this
>
> TRAMP_DIR = $(lisp)/net
> TRAMP_SRC = $(TRAMP_DIR)/tramp.el $(TRAMP_DIR)/tramp-cache.el \
> [... etc...]
>
> $(TRAMP_DIR)/tramp-loaddefs.el: $(TRAMP_SRC)
> $(emacs) -l autoload \
> --eval "(setq generate-autoload-cookie \";;;###tramp-autoload\")" \
> --eval "(setq generated-autoload-file \"$@\")" \
> --eval "(setq make-backup-files nil)" \
> -f batch-update-autoloads $(TRAMP_DIR)
>
> will update autoloads for *all* files in lisp/net/*, using
> $(TRAMP_DIR)/tramp-loaddefs.el as autoload file. Or am I missing
> something?
That's correct. But it doesn't hurt, because it uses the autoload cookie
";;;###tramp-autoload", which exists only in tramp-*.el files.
An alternative would be to introduce an own lisp/tramp subdirectory, but
Tramp does not reach the "20 files or up" count. Shall I continue to
split the files? :-)
> Juanma
Best regards, Michael.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: generation of tramp-loaddefs
2010-09-13 15:49 ` Michael Albinus
@ 2010-09-13 15:55 ` Juanma Barranquero
0 siblings, 0 replies; 3+ messages in thread
From: Juanma Barranquero @ 2010-09-13 15:55 UTC (permalink / raw)
To: Michael Albinus; +Cc: Emacs developers
On Mon, Sep 13, 2010 at 17:49, Michael Albinus <michael.albinus@gmx.de> wrote:
> Thanks a lot!
Not at all. It's just copying a few lines of lisp/Makefile.in and
massaging them a little, after all :-)
> That's correct. But it doesn't hurt, because it uses the autoload cookie
> ";;;###tramp-autoload", which exists only in tramp-*.el files.
Ah, I missed that. OK.
> An alternative would be to introduce an own lisp/tramp subdirectory,
Not necessary yet, no.
Thanks,
Juanma
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-09-13 15:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-09-13 15:38 generation of tramp-loaddefs Juanma Barranquero
2010-09-13 15:49 ` Michael Albinus
2010-09-13 15:55 ` Juanma Barranquero
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).