From: "Daniel P. Berrange" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Alberto Garcia <berto@igalia.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] rules: don't try to create missing include dirs
Date: Mon, 6 Feb 2017 12:23:12 +0000 [thread overview]
Message-ID: <20170206122312.GL3029@redhat.com> (raw)
In-Reply-To: <221a40d6-9688-d384-0d59-5b0fefe8206e@redhat.com>
On Mon, Feb 06, 2017 at 01:22:08PM +0100, Paolo Bonzini wrote:
>
>
> On 06/02/2017 13:05, Daniel P. Berrange wrote:
> >>> $(shell mkdir -p ./ $(sort $(dir $($v))))
> >>> - $(shell cd $(BUILD_DIR) && mkdir -p ./ $(sort $(dir $($v))))
> >> I know this is the same syntax as the existing line above
> >> and we're deleting it anyway, but what does it actually do?
> >> When does telling mkdir to create "./" make sense?
> > No idea why the ./ was there originally - it appears to serve no
> > purpose. The useful bit is the stuff afterwards - the $($v) bit.
> > It gets populated based on the variable being unnested. For example
> >
> > block-obj-y = block.o blockjob.o block/ nbd/
> >
> > will make $v contain "block nbd", hence cause creation of those
> > dirs in the the build dir.
>
> "mkdir -p" with no arguments gives an error, the "./" shuts it up.
Ah yes, clever. So that deals with case of unnesting a variable which
does not contain any nested dirs.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
next prev parent reply other threads:[~2017-02-06 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 11:29 [Qemu-devel] [PATCH] rules: don't try to create missing include dirs Daniel P. Berrange
2017-02-06 11:42 ` Alberto Garcia
2017-02-06 11:50 ` Peter Maydell
2017-02-06 12:05 ` Daniel P. Berrange
2017-02-06 12:22 ` Paolo Bonzini
2017-02-06 12:23 ` Daniel P. Berrange [this message]
2017-02-07 12:04 ` Peter Maydell
2017-02-07 15:13 ` Stefan Hajnoczi
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=20170206122312.GL3029@redhat.com \
--to=berrange@redhat.com \
--cc=berto@igalia.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.