Opened 13 years ago
Last modified 4 years ago
#8558 new enhancement
[Build system] should abort on updating nonexistent target
Reported by: | diver | Owned by: | bonefish |
---|---|---|---|
Priority: | normal | Milestone: | R1.1 |
Component: | Build System | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
This is hrev44133, gcc2hybrid.
I was trying to update something and accidentally misspelled target name. I couldn't figure out why the binary doesn't change. Later I noticed that update feature doesn't show any errors if you try to update something which doesn't even exist.
jam -j2 @disk update 123
Change History (3)
comment:1 by , 13 years ago
comment:2 by , 12 years ago
Type: | bug → enhancement |
---|
comment:3 by , 4 years ago
Milestone: | R1 → R1.1 |
---|
Note:
See TracTickets
for help on using tickets.
That may be fixed by inserting
in the "update" case block in DefineBuildProfile in build/jam/MiscRules. I don't have the time to test this ATM. Not sure when/how the missing target is reported with this solution. It may be nicer to explicitly check whether all update targets have been found after having processed the complete jamfile tree.