-
Type: Bug
-
Resolution: Won't Do
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Server Development Platform
-
ALL
When LibdepLinter fails, it does not tell me which file and line number the error is located. This requires a developer to search the code base when it would save time if the error could simply include information about where the fault likes like compilers do.
Example:
scons: *** LibdepLinter: Program 'XYZ' has 'src/x/y/z' listed in LIBDEPS out of alphabetical order.