Re: [PATCH 3/3] allow a second parameter to be the output file name

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On Tue, 30 Jun 2015 15:11:19 +1000
David Gibson <david@xxxxxxxxxxxxxxxxxxxxx> wrote:

Hi David,

> On Tue, May 26, 2015 at 12:11:23AM +0100, Andre Przywara wrote:
> > If there is more than one file name specified on the command line,
> > assume it is the output file name.
> > This allows to use a more intuitive cp-style command line syntax,
> > which (together with the input type guessing) allows something like:
> > $ dtc input.dts output.dtb
> > (or the other way round) to cover the most common usage scenarios.
> > 
> > Signed-off-by: Andre Przywara <osp@xxxxxxxxx>
> 
> Nack to this, sorry.
> 
> I'd prefer to model our command line on other compilers, and -o is a
> more common convention there.

Fair enough, I will drop this patch then.
Seems like: "dtc input.dts > output.dtb"  will do the trick, too and
it's just two characters more to type ;-)

> 
> I would however, accept a patch to guess an output name based on input
> name if -o is not specified, allowing the output name to be omitted
> entirely in common cases.

I'd rather keep the stdout behaviour in this case, I find writing to
unspecified filenames quite scary.

Cheers,
Andre.
--
To unsubscribe from this list: send the line "unsubscribe devicetree-compiler" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Device Tree]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux