View Single Post
Posts: 2,076 | Thanked: 3,268 times | Joined on Feb 2011
#60
Yup, bash here.

Been reading jam manfile and this part maybe is causing different build:
Code:
The scanning for header file inclusions is not exact, but it is at least dynamic, so there is no need to run something like makedepend(GNU) to create a static dependency file. The scanning mechanism errs on the side of inclusion (i.e., it is more likely to return filenames that are not actually used by the compiler than to miss include files) because it can't tell if #include lines are inside #ifdefs or other conditional logic. In Jambase, HdrRule applies the NOCARE rule to each header file found during scanning so that if the file isn't present yet doesn't cause the compilation to fail, jam won't care.
As in: doesn't find something on my device, still builds, finds something in autobuilder and result differs?
 

The Following 2 Users Say Thank You to szopin For This Useful Post: