Always build a file

[awneil]

@chrisbrown

The MS-DOS touch command can be used too

But MS-DOS doesn’t have a touch command, does it

Yes, there are plenty of 3rd-party add-on ones that you can download (at your own risk) - but MS-DOS itself doesn’t have one (nor even the Win32 command shell).

[chrisbrown]

@awneil

@chrisbrown

The MS-DOS touch command can be used too

But MS-DOS doesn’t have a touch command, does it

Yes, there are plenty of 3rd-party add-on ones that you can download (at your own risk) - but MS-DOS itself doesn’t have one (nor even the Win32 command shell).

I assumed that there was one, because it has always worked whenever I have used it on various computers. However, upon further inspection, it appears that multiple programs that I have installed, have added path entries that point to (among other things) a touch command. Apparently I have never tried this on a computer where I hadn’t already installed something that inculded it.

[awneil]

@daav

For arguments, put the location of the file you want to touch, relative to the ${project_loc} variable (e.g. ${project_loc}/src/timestamp.c)

Shouldn’t that be:

${project_loc:/src/timestamp.c}

[daav]

@awneil

@daav

For arguments, put the location of the file you want to touch, relative to the ${project_loc} variable (e.g. ${project_loc}/src/timestamp.c)

Shouldn’t that be:
${project_loc:/src/timestamp.c}

Both syntaxs should work.
The only difference I see is that maybe the ${project_loc:/src/timestamp.c} syntax produces a path with the path separators in the right way under Windows (only '' instead of a mix of '' and ‘/’ for the other syntax), which may be more suitable for your COPY command tip.