From: Borsenkow Andrej <Andrej.Borsenkow@mow.siemens.ru>
To: "'Zsh hackers list'" <zsh-workers@sunsite.dk>
Subject: RE: Modules build framework/autoconf-2.13
Date: Wed, 8 May 2002 15:56:40 +0400 [thread overview]
Message-ID: <6134254DE87BD411908B00A0C99B044F02E89A78@mowd019a.mow.siemens.ru> (raw)
In-Reply-To: <13754.1020858119@csr.com>
>
> Sounds quite reasonable.
Oh well :-)
> It might make it more difficult to handle
> problems with include file location and dependencies on other modules,
> but that's currently not all that robust. Possibly the directory
> structure could reflect this, dependencies living in higher
directories.
> (Doesn't help multiple dependencies, though.)
>
What I plan is to first collect modules list then sort them before
generating Makefile.in's. This way you know all dependencies in advance
(or dependencies loop for that matter).
> It would be neatest if it were possible to add an new module and add
its
> tools without regenerating the whole set, i.e. looping over separate
> configure files rather than appending them to the main one.
>
Sure! That is what configure does. Of course, 2.5x does not cache by
default which means it will rerun the whole configure(s) (unless you
have told it to create cache).
> Subdirectories ought to be subdirectories of Modules, not directly of
> Src. I don't know what would happen with Zle.
>
The same. Move it as modules under Modules. It is not in any way
different.
Would it be O.K. to get rid of autoconf 2.13 compatibility?
-andrej
next prev parent reply other threads:[~2002-05-08 11:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-08 10:41 Borsenkow Andrej
2002-05-08 11:41 ` Peter Stephenson
2002-05-08 11:56 ` Borsenkow Andrej [this message]
2002-05-08 12:42 ` Peter Stephenson
2002-05-08 15:45 ` Bart Schaefer
2002-05-08 16:01 ` Borsenkow Andrej
2002-05-08 16:21 ` Bart Schaefer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6134254DE87BD411908B00A0C99B044F02E89A78@mowd019a.mow.siemens.ru \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=zsh-workers@sunsite.dk \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).