'links' doesn't follow dependency on static libs projects

project "A"
  kind "StaticLib"
...
project "B"
  kind "StaticLib"
  links {"A"}
...
project "C"
  kind "StaticLib"
  links {"B"}

project "App"
  kind "ConsoleApp
  links {"C"} --> not going to be built, since B and A are not included

When there is links dependency on another project, which is a static lib, premake should include all the static lib dependencies of that as well. Otherwise user has to include all of them explicitly in the resulting app or DLL. ( links {"C", "A", "B"} for the App in the example above) Which is troublesome, since the list of libs might be conditional (platform dependent, for example) and user will have to copy/paste the conditions several times over.
Note, this isn't a problem for dlls, only for static libraries. Since dll has all it's dependencies built in already.

Start with the A→B→C→App static-library example in issue #627 and trace how project links are resolved. The payload names no files or tests; done means an App linking only C also includes the transitive static-library dependencies A and B, without requiring duplicate conditional link lists.