I am executing a JScript to generate code. I have a Custom Build Step to do that. It is not being done and I don't understand why not.
The command line for the custom build (excluding the path of the script) is:
CScript.EXE Preprocessor.js "$(ProjectDir)" "$(InputFileName)"
I have outputs such as:
"$(ProjectDir)\Output1" "$(ProjectDir)\Output2"
However I can't get the custom build to execute. If the outputs don't exist then it does not execute. If the outputs do exist and I update the input then the custom build still does not execute. Am I wrong that the custom build should execute in both situations
Update: I found the thread "Custom build step" of a project: execution rule , which suggests that there is a bug or are some bugs. If that is the problem then at least I didn't misunderstand. I will try to ensure that the case of the filenames match, as indicated in that thread.
Custom Build Step isn't done
Jym
Maybe the outputs must be separated with semicolon:
"$(ProjectDir)\Output1";"$(ProjectDir)\Output2"
I hope it helps.
GroovenDrew
Yes, semicolons are necessary. I am surprised that there was no message of any kind about the outputs. VC just did nothing.
I got quite frustrated setting up that Custom Build. I don't do them very often so I had forgot some things. Another problem is that some changes from the way that VC works was a problem, yet VC did not always complain about that either. More specifically, VC 6 used ProjDir whereas VC 2005 (VC 8 ) uses ProjectDir. Yet VC 2005 did not complain about ProjDir initially.
Also the project settings (now called Project Properties, which seems innapropriate to me) are inconsistent; when library files are specified, they are separated by spaces. I think there are other places where either spaces or semicolons work.
I did not get notification that that the answer was designated as being an answer. I thought we are notified.