You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
you store vars in a style VARNAME_$(d),don't you think there will be something wrong when in a situation uppercase and lowercase for same word are mixed together?
The text was updated successfully, but these errors were encountered:
I'm not sure what you mean - could you give an example?
Variables in make are case sensitive. More over there is nearly no chance that anybody will define variable with name of the sort SRCS_/home/user/some/directory (that is a full name of variable). If anybody makes a mistake and instead of SRCS in his Rules.mk defines Srcs or srcs then he should correct it - there is no provision to guess that, and there will not be since that can break some make files where e.g. some user uses srcs for his internal purposes.
What I mean is not someone stupidly using a wrong case variable name (SRCS to be sRcs),but is generating a wrong case variable TARGETS_/home/user/Some/Directory,this generated name can be correctly used at one place,but other one use TARGETS_/home/user/some/directory to point to it but get nothing.It's just similar to the trap that TARGETS_/home/user/some/AWAY/../directory is not equal to TARGETS_/home/user/some/directory
you store vars in a style VARNAME_$(d),don't you think there will be something wrong when in a situation uppercase and lowercase for same word are mixed together?
The text was updated successfully, but these errors were encountered: