Instead of creating template files in the repo, maybe a script in tools
that creates the files with all the proper contents?
Why not create an entire project framework is the spirit of VisualStudio:
I want to create:
[ ] Device driver
[ ] An MTD driver
[ ] A new board
[ ] etc.
Then creat
Instead of creating template files in the repo, maybe a script in tools
that creates the files with all the proper contents?
Why not create an entire project framework is the spirit of VisualStudio:
I want to create:
[ ] Device driver
[ ] An MTD driver
[ ] A new board
[ ] etc.
Then create
On Sun, Feb 2, 2020 at 9:11 AM Gregory Nutt wrote:
>
> > My argument for this is the coding standard document can reference the
> > directory and `cp` or `copy` can be used to get a properly formatted
> staring
> > point file. This is opposed to cutting and pasting from a web browser and
> > poss
My argument for this is the coding standard document can reference the
directory and `cp` or `copy` can be used to get a properly formatted staring
point file. This is opposed to cutting and pasting from a web browser and
possibly really getting garbage in the file.
Less tools, less margin for
error and a test case for nxstyle, with the
possibility to automate a replacement tool.
I would be in favor of that sort of thing.
-Original Message-
From: Gregory Nutt [mailto:spudan...@gmail.com]
Sent: Sunday, February 02, 2020 5:55 AM
To: dev@nuttx.apache.org
Subject: Re: [DISCUSS] adding
When we do get this figured out. Can we put templates in a folder in the
nuttx repo named something like:
template_c_file.txt
template_h_file.txt
template_Make_file.txt
template_ld_file.txt
template_script_file.txt
There are already templates at the end of the coding standard document
for .
