Is there any method/technique/feature to add automatically incremented build number to the code (managed by software or tool)? the build number can be used for viewing (hence traceability of the code).
Was Reading the chapter5 of help, i executed a command line in the command prompt of windows. SubWCRev D:\MyLPC1788\Codes\Development Board\Local D:\MyLPC1788\Codes\Development Board\version.h D:\MyLPC1788\Codes\Development Board -nmdfe
But the nothing change in the version.h file. So i went to the (right click) Properties->new->keywords and checked the boxes "Author, Date, ID, Revision" Again executed the line in the command prompt but no updates.
I created a text file (template.txt) and updated
// Test file for SubWCRev char *Revision = "$WCREV$"; char *Revision16 = "$WCREV&0xFF$"; char *Revisionp100 = "$WCREV+100$"; char *Revisionm100 = "$WCREV-100$"; char *Modified = "$WCMODS?Modified:Not modified$"; char *Unversioned = "$WCUNVER?Unversioned items found:no unversioned items$"; char *Date = "$WCDATE$"; ... // as given on the site #if $WCMODS?1:0$ #error Source is modified #endif
then saved it as .tmpl file.
SubWCRev D:\MyLPC1788\Codes\Development Board\Local D:\MyLPC1788\Codes\Development Board\template.tmpl D:\MyLPC1788\Codes\Development Board\version.h -nmdfe
But the nothing change in the version.h file. So i changed the name to version.txt but no updates. What is the mistake that i am committing?
What is the mistake that i am committing?
Did you try to figure it out yourself? First of all, do you actually need all those command line switches: "-nmdfe"? I don't think they mean what you think they mean. And I don't think you actually need them. Second, you really should enclose file paths in quotes. Those spaces in directory names can easily create problems.
Did you try to figure it out yourself? First of all, do you actually need all those command line switches: "-nmdfe"? Do you understand what they mean? Because I don't think you need them. Secondly, you really should enclose file paths in quotes. Those spaces in directory names can easily create problems.
Thank you. Double inverted commas got me the required output.
Secondly, you really should enclose file paths in quotes. Those spaces in directory names can easily create problems.
Or better yet, one should really just not use spaces in file and directory names. They simply aren't worth the grief they routinely cause. Blanks in filenames just don't mix well with command-line oriented tools like compilers.
Absolutely!
(and, of course, "filenames" includes folder names)