Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 291
  • Last Modified:

Wait While Custom Build Tool Runs

I run a custom build tool to date/version stamp my resources.  On most machines  (Win95 MSVC4.2) the build process waits for the tool to close before proceeding. On one, it does not wait.  On my machine, it waits in 4.2, but in recently installed DevStudio 5.0 it does not. The behavior is not specific to my tool.  Notepad behaves the same way.
0
NullTerminator
Asked:
NullTerminator
  • 3
  • 3
1 Solution
 
shaigCommented:
Are you sure you didn't mix the custum build with the pre-link page?
Anyway, why not use the pre-link option?
Or, don't you want to version your files only if the build was succesful?  if yes, use the post biuld option!
0
 
NullTerminatorAuthor Commented:
Your answer was three questions. No I am not mixing the Custom Tab with the pre link page.  MSVC 4 didn't have a prelink page.  I am not stamping the executable, I am writing the VS_VERSION_INFO block of the resources.  I have access to all of the versioning info, and I don't have to worry about space allocation in the executable.  Fail or succeed, the stamp is the same.
0
 
shaigCommented:
Let me be more specific:
Since you mentioned that you HAVE passed to VC5.0 wich has the tab i mentioned ( and maybe because you aren't familur with VC5.0 because you've just recently switched from 4.2 ), i only suggested you check.

Any way, if it is important that you do your stuff after the bulid, the i suggest you use the post-build option of the VC5.0.

Mybe my English isn't clear enough, since i'm not an American.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
NullTerminatorAuthor Commented:
I don't think my question was clear. In 4.x the build process stopped while my tool collected version information from the user.  This is the desired behavior. It worked on all but one machine.

We are testing development on 5.0.  5.0 does not wait on any of the tested machines.  This is not desired.  I AM NOT stamping the executable.  I am stamping the resource VS_VERION_INFO block.

An alternate solution for 5.x would be to run my tool as a pre link operation on the resources, and then add something to force the resource compiler to recompile prior to linking. If you can tell me how to trigger the resource compile so the linker sees the change I'll accept an answer.
0
 
shaigCommented:
Is it possible that you have not saved changes to the resource file and that is why changes are ignored? (the date is not new enough to trigger recompilation)

0
 
NullTerminatorAuthor Commented:
No it is not possible.  The problem is the build process does not wait for my tool to finish before proceeding.  The dependency check process does not see the updated date on the file after my tool closes.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now