Support static/dynamic for bionic

Unlike the other toolchains, bionic supports both static and dynamic.  This CL adds an environment variable which will allow SDK targets to be built with dynamic linking.  It also enables additional bionic targets such as nacl_io demo and test.

Since the current dynamic loader only supports searching DT_NEEDED namespaces for symbols, bionic forces us to declare dependencies explicitly which causes build order issues.

BUG=none
R=binji@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=266900

[noelallen1, 2014-04-28 20:14:21]

ptal

[binji, 2014-04-28 21:01:22]

lgtm in general, curious about a few things.

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/bu...
File native_client_sdk/src/build_tools/build_projects.py (right):

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/bu...
native_client_sdk/src/build_tools/build_projects.py:107:
out.append('%s_DEPS:=%s' % (proj['NAME'], ' '.join(localdeps)))
I'd prefer appending a dict or tuple here and doing the string generation in the
template file. It makes it clearer in the template file what is being generated.

e.g.

  out.append({'name': proj['NAME'], 'value': ' '.join(localdeps)})

then in the template:

  [[for dep in deps:]]
    {{dep['name']}}_DEPS := {{dep['value']}}
  [[]]

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/bu...
File native_client_sdk/src/build_tools/build_sdk.py (left):

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/bu...
native_client_sdk/src/build_tools/build_sdk.py:356: 'libnacl.a',
Why? Mention this in the CL description.

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/bu...
File native_client_sdk/src/build_tools/parse_dsc.py (right):

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/bu...
native_client_sdk/src/build_tools/parse_dsc.py:187: def OrderTree(project_tree):
?

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/re...
File native_client_sdk/src/resources/Makefile.index.template (right):

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/re...
native_client_sdk/src/resources/Makefile.index.template:16: {{dep}}
Can you give an example of what this will generate?

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/to...
File native_client_sdk/src/tools/nacl_gcc.mk (right):

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/to...
native_client_sdk/src/tools/nacl_gcc.mk:369: $(call LOG,LINK,$$@,$(ARM_LINK)
$(BIONIC_LINK) -o $$@ $$(filter %.o,$$^) $(NACL_LDFLAGS) $(ARM_LDFLAGS)
$(foreach path,$(6),-L$(path)/$(TOOLCHAIN)_arm/$(CONFIG)) $(foreach
lib,$(3),-l$(lib)) $(5))
won't this affect arm newlib as well?

[noelallen1, 2014-04-28 23:00:32]

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/bu...
File native_client_sdk/src/build_tools/build_projects.py (right):

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/bu...
native_client_sdk/src/build_tools/build_projects.py:107:
out.append('%s_DEPS:=%s' % (proj['NAME'], ' '.join(localdeps)))
On 2014/04/28 21:01:22, binji wrote:
> I'd prefer appending a dict or tuple here and doing the string generation in
the
> template file. It makes it clearer in the template file what is being
generated.
> 
> e.g.
> 
>   out.append({'name': proj['NAME'], 'value': ' '.join(localdeps)})
> 
> then in the template:
> 
>   [[for dep in deps:]]
>     {{dep['name']}}_DEPS := {{dep['value']}}
>   [[]]

Done.

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/bu...
File native_client_sdk/src/build_tools/build_sdk.py (left):

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/bu...
native_client_sdk/src/build_tools/build_sdk.py:356: 'libnacl.a',
On 2014/04/28 21:01:22, binji wrote:
> Why? Mention this in the CL description.

Done.

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/bu...
File native_client_sdk/src/build_tools/parse_dsc.py (right):

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/bu...
native_client_sdk/src/build_tools/parse_dsc.py:187: def OrderTree(project_tree):
On 2014/04/28 21:01:22, binji wrote:
> ?

Done.

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/re...
File native_client_sdk/src/resources/Makefile.index.template (right):

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/re...
native_client_sdk/src/resources/Makefile.index.template:16: {{dep}}
On 2014/04/28 21:01:22, binji wrote:
> Can you give an example of what this will generate?

Done.

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/to...
File native_client_sdk/src/tools/nacl_gcc.mk (right):

https://codereview.chromium.org/240493003/diff/20001/native_client_sdk/src/to...
native_client_sdk/src/tools/nacl_gcc.mk:369: $(call LOG,LINK,$$@,$(ARM_LINK)
$(BIONIC_LINK) -o $$@ $$(filter %.o,$$^) $(NACL_LDFLAGS) $(ARM_LDFLAGS)
$(foreach path,$(6),-L$(path)/$(TOOLCHAIN)_arm/$(CONFIG)) $(foreach
lib,$(3),-l$(lib)) $(5))
On 2014/04/28 21:01:22, binji wrote:
> won't this affect arm newlib as well?

Done.

[noelallen1, 2014-04-29 16:54:46]

Committed patchset #3 manually as r266900 (presubmit successful).