Support Automatic Integration of SDK with CMake

[GoogleCodeExporter]

Currently, there is no easy way to automatically generate a CMake project that 
uses the Native Client SDK.  Several users have requested that we provide an 
environment that CMake can use for automatically detecting and configuring the 
NaCl toolchain.

On Windows, this may require the SDK installer to set an environment variable 
that the CMake-GUI can reference when looking for tools such as x86_64-nacl-gcc.

See e-mail threads:
 - http://groups.google.com/group/native-client-discuss/browse_thread/thread/a76ba3eae5d6788d
 - http://groups.google.com/group/native-client-discuss/browse_thread/thread/eee98be9b5f06926

Original issue reported on code.google.com by mball@google.com on 8 Sep 2011 at 7:19

[GoogleCodeExporter]

It might make sense to think about this as not just a request to support CMake, 
but rather to make sure that it's possible for *any* build system to easily use 
NaCl.  The environment variable that points to the location of the SDK is 
generally useful to any similar tool.

Original comment by erik...@chromium.org on 8 Sep 2011 at 7:41

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Fully agreed, thanks for re-submitting this issue.

If we can rely on the NACL_SDK_ROOT environment variable to be set, *any* build 
system can easily use NaCL, including cmake, premake and autotools. In 
particular under Windows.

I kindly ask the NaCL devs not to close the new Issue 128 as WontFix, but leave 
it open if you are too busy with other tasks at the moment.

Original comment by erwin.coumans on 8 Sep 2011 at 8:19

[GoogleCodeExporter]

Original comment by dsprin...@chromium.org on 26 Sep 2011 at 9:10

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by dsprin...@chromium.org on 26 Sep 2011 at 9:20

• Changed state: Assigned

[GoogleCodeExporter]

Fixed in r1385

Original comment by mball@google.com on 5 Dec 2011 at 5:57

• Changed state: Fixed