Paolo Bonzini writes:
> On 11/05/2017 17:30, Alex Bennée wrote:
%.o: %.S
+ mkdir -p $(dir $@)
>>> Should this use @ for cleanliness?
>> > I'm not sure I follow. Did you mean use $(@D) directly?
>
> That too, but I was thinking of using "@mkdir" to avoid
On 11/05/2017 17:30, Alex Bennée wrote:
>>>
>>> %.o: %.S
>>> + mkdir -p $(dir $@)
>> Should this use @ for cleanliness?
> > I'm not sure I follow. Did you mean use $(@D) directly?
That too, but I was thinking of using "@mkdir" to avoid spamming the
output with mkdir commands.
Paolo
Paolo Bonzini writes:
> On 06/04/2017 21:07, Alex Bennée wrote:
>> This is fairly direct way of ensuring the target build directories are
>> created before we build a binary blob. mkdir -p fails gracefully if
>> the directory is already there.
>>
>> Signed-off-by: Alex
On 06/04/2017 21:07, Alex Bennée wrote:
> This is fairly direct way of ensuring the target build directories are
> created before we build a binary blob. mkdir -p fails gracefully if
> the directory is already there.
>
> Signed-off-by: Alex Bennée
> ---
> Makefile | 5
On Thu, Apr 06, 2017 at 08:07:24PM +0100, Alex Bennée wrote:
> This is fairly direct way of ensuring the target build directories are
> created before we build a binary blob. mkdir -p fails gracefully if
> the directory is already there.
>
> Signed-off-by: Alex Bennée
>
This is fairly direct way of ensuring the target build directories are
created before we build a binary blob. mkdir -p fails gracefully if
the directory is already there.
Signed-off-by: Alex Bennée
---
Makefile | 5 +
1 file changed, 5 insertions(+)
diff --git