c++ - How do you force a makefile to rebuild a target -
I have a mess file that creates and then makes a messphil call because it makes more messphile calls to MessFile which works Actually it does not change. Thus, it keeps thinking that the project is up to date and date.
dnetdev11 ~ # create: 'Release' is up to date. How can I force Macfill to rebuild the target?
Clear = $ (make) -f ~ / xxx / xxx_compile.workspace.mak Clear Build = svn up ~ / xxx \ $ (clean) \ ~ / cbp2mak / cbp2mak -C ~ / Xxx ~ / xxx / xxx_compile.workspace \ $ (make) -f ~ / xxx / xxx_compile.workspace.mak $ (1) \ release: $ (build) debug: $ (build DEBUG = 1) Clean: $ (clean) Install: cp ~ / xxx / source / xxx_utility / release / xxx_util / usr / local / bin cp ~ / xxx / source / xxx_utility /release/xxxcore.so / usr / local / lib < P> Note: Names have been removed to protect innocent. Editing: Last Fix Version:
Clear <$> clean = $ (make) -f xxx_compile.workspace.mak ; Build = svn up; \ $ (Clean) \ ./cbp2mak/cbp2mak-Cxxx_compile.workspace; \ $ (Make) -f xxx_compile.workspace.mak $ (1); \ .PHONY: Reboot debug clean install release: $ (call build, debug): $ (call build, DEBUG = 1) clean: install $ (clean): cp./source/xxx_utillity/release/xxx_util/ usr / bin
A fake target is that which is not actually the name of a file; Rather, it is only a name for a recipe when you make a clear request. There are two reasons to use a simulated target: to avoid conflict with the file of the same name and to improve the performance.
...
A mock target should not be a condition of a real target file; If this happens, then its recipe will go to update that file every time. Unless a fraudulent goal has any condition for any real goal, a fake target recipe is executed when the simulated target is a fixed target
Comments
Post a Comment