Stopping a failed build from linking in DevEnv?

Cd577ee1cb56aa2ad5645b7daa0a2830
0
eddie 101 Jul 14, 2006 at 22:46

This is less programming and more IDE-MSVCBuild-Specific.

Does anyone know if it’s possible to stop visual studio from linking an executable if any of the OBJ’s failed building?

I like that VS will keep building even if there’s errors, but it sucks that it then tries to link (which then fails, and leaves you with no executable).

Just curious if anyone knows of a way around that.

Cheers.

5 Replies

Please log in or register to post a reply.

A8433b04cb41dd57113740b779f61acb
0
Reedbeta 167 Jul 14, 2006 at 23:02

Hmm. I’m not sure why you’re experiencing for that, but for me, VS (7.1) doesn’t try to link if there was a compile error, and the executable is not overwritten in that case.

6d318bb67270aa12b325e2cd7b64ff7a
0
pater 101 Jul 15, 2006 at 06:03

I’m quite sure that neither of VS6.0, VS7.0 or VS7.1 would normaly cause this behaviour. What they DO, is they continue building with the next project in the solution if one fails. If these projects depend on each other, the final linkage may fail, resulting in the executable being deleted.

Cd577ee1cb56aa2ad5645b7daa0a2830
0
eddie 101 Jul 15, 2006 at 16:25

Sorry, that’s what I meant. The final linkage fails.

6d318bb67270aa12b325e2cd7b64ff7a
0
pater 101 Jul 15, 2006 at 18:59

I’m sorry I don’t know then. But I would be glad to know how to abort the build completelly as soon as an error occurs, too.

340bf64ac6abda6e40f7e860279823cb
0
_oisyn 101 Jul 16, 2006 at 01:04

It would probably be possible using macros, as for every build error a task gets added to the task list (which can be monitored by macros)