From: Eric Lilja <mindcooler@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Moving homebrewn binaries and question about building documentation
Date: Sat, 21 Jul 2007 18:25:30 +0200 [thread overview]
Message-ID: <f7tc1p$r3u$1@sea.gmane.org> (raw)
In-Reply-To: <ufy3hojsa.fsf@gnu.org>
Eli Zaretskii wrote:
>> From: Eric Lilja <mindcooler@gmail.com>
>> Date: Sat, 21 Jul 2007 16:56:00 +0200
>>
>> As you can see I had a trailing / in my INSTALL_DIR so
>> install tries to copy like this (just pasting one example):
>> cp -f oo-spd/i386/etags.exe c:/emacs//bin
>> Notice the double forward slash. It didn't seem to affect copying,
>> though, and I will simply remove the trailing slash from INSTALL_DIR in
>> my script (I thought it would check for a trailing slash and add one if
>> there wasn't one but it seems it adds one regardless).
>
> This is not a problem, as you've found out, but it's better to not
> have a trailing slash in INSTALL_DIR.
I hear you. I have fixed my script in this regard and added a comment
about it should I forget it.
>
>> Also, I still have many CVS directories in the subdirectories.
>
> Only in etc/ and leim/. The Unix "make install" removes them after
> copying (see the `install:' target in the top-level Makefile.in), but
> the Windows build does not want to rely on the utilities required for
> that. If you have them, you can remove those after "make install"
> finishes.
And info as well, anyway, what I wanted to do was not to nitpick but ask
you if you know of a clever way I can remove these directories from
inside my script? It's a bash script run under cygwin bash. I'm not
really a unix person, so I don't know what I'm talking about here, but
maybe something involving find and rm? If I can get rid of my standalone
application for removing these directories and incorporate its
functionality in my cvs build script, that would be nice.
>
>> I also
>> noticed two empty top-level directories named lock and data,
>> respectively. These are not present in the official emacs 22.1 windows
>> binary package. Comments?
>
> These are created by two explicit lines in nt/makefile, but I don't
> know why. Anybody?
I will leave them untouched for now, but if they are not needed it would
be nice if they were not created, of course.
You're a great asset, Eli! Thanks!
- Eric
next prev parent reply other threads:[~2007-07-21 16:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 12:23 Moving homebrewn binaries and question about building documentation Eric Lilja
2007-07-21 13:56 ` Eli Zaretskii
2007-07-21 14:32 ` Eric Lilja
2007-07-21 14:52 ` Eli Zaretskii
2007-07-21 14:56 ` Eric Lilja
2007-07-21 15:31 ` Eli Zaretskii
2007-07-21 16:25 ` Eric Lilja [this message]
2007-07-21 16:58 ` Eli Zaretskii
2007-07-21 17:37 ` Eric Lilja
2007-07-21 19:05 ` Eli Zaretskii
2007-07-22 3:58 ` dhruva
2007-07-22 13:18 ` Eric Lilja
2007-07-21 22:17 ` Jason Rumney
2007-07-22 3:14 ` Eli Zaretskii
2007-07-22 13:18 ` Eric Lilja
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='f7tc1p$r3u$1@sea.gmane.org' \
--to=mindcooler@gmail.com \
--cc=emacs-devel@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).