zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: "make clean" (distclean, realclean, etc.) and local modules
Date: Sat, 29 Aug 2015 08:11:09 -0700	[thread overview]
Message-ID: <150829081109.ZM24304@torch.brasslantern.com> (raw)

I have a git branch in which I'm working on a zsh module, including the
yodl doc for it.

It took quite a bit more wrangling than I expected to add the module to
the build (cf. my Etc/zsh-development-guide patches from a few weeks
ago, there's probably more to be done there) and get the documentation
tied in properly (which seems to be an entirely undocumented process).

Now I'd like to switch back to the master branch and build the lastest
"stock" shell, but I get a bunch of compile errors from references to
the (now-missing) module files. After repeatedly attempting to track
down and edit or remove files that refer to the module and still being
stuck with errors, I gave up and created a whole separate parallel build
tree (by running ../zsh/configure) which successfully builds the binary
but still complains about missing yodl sources.

I then tried "make clean" and "make realclean" before recompiling, also
without success. I didn't actually go for "distclean" because I didn't
want to delete all the configure results. I suppose I should have tried
"mostlyclean"? I forgot about that one until just now.

Does anybody actually still understand the system for generating the
makefiles and various intermediate semi-phony targets?  Is there a
correct incantation for removing references to a module, other than
to start from an entirely fresh source tree?


                 reply	other threads:[~2015-08-29 15:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=150829081109.ZM24304@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.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.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).