Hacksaw n00b
Joined: 24 Jan 2014 Posts: 3
|
Posted: Fri Jan 24, 2014 2:33 pm Post subject: Chromium (32.0.1700.77): why no nacl/pnacl? |
|
|
Hi all, first of all I'm new to the forum, so I hope to be posting in the right section and not asking something already answered many times.
Since Chrome 31, PNacl (Portable Native Client) was deemed stable by Google. I would like to test it, but current stable Chromium ebuild, AFAIK, disables both NaCl and PNaCl unconditionally:
Code: |
# Disable nacl, we can't build without pnacl (http://crbug.com/269560).
myconf+=" -Ddisable_nacl=1"
# Disable glibc Native Client toolchain, we don't need it (bug #417019).
# myconf+=" -Ddisable_glibc=1"
# TODO: also build with pnacl
# myconf+=" -Ddisable_pnacl=1"
|
Is there some security concern or technical reason behind this choice? Maybe NaCl/PNaCl engine could be made dependant by a USE flag?
Thank you in advance for you answer. |
|