Re: [native-client-discuss] Pepper17 nacl sdk download

[Christian Stefansen]

Hi Rang,

Can I ask why you want Pepper 17? We have made significant improvements to the SDK since Pepper 17. E.g., recently, Pepper 25 introduced MessageLoop and the ability to make Pepper calls from any thread.

Christian

On Mon, Apr 1, 2013 at 8:33 PM, Rang <gian...@rubycell.com> wrote:

Hi everyone.

I want to download "pepper17 nacl sdk" but it was deprecated. 

If someone else had downloaded it before, please share it with me. Thanks !

--
You received this message because you are subscribed to the Google Groups "Native-Client-Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to native-client-di...@googlegroups.com.
To post to this group, send email to native-cli...@googlegroups.com.
Visit this group at http://groups.google.com/group/native-client-discuss?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Christian Stefansen

[Victor Khimenko]

On Mon, Apr 29, 2013 at 10:32 PM, Tamas Madl <thoma...@gmail.com> wrote:

Hi everyone,

I would also need a legacy version, pepper_16. I am using a library (BOINC BeeGrid, https://github.com/BME-IK/gridbee-nacl-framework) that needs scons, which was included in that version. Adding and custom building scons doesn't seem to help, since the build scripts make lots of calls to routines only included in pepper_16 (such as calls to the NaClEnvironment function and the other scripts of "build_tools" that got removed from the newer pepper versions)

Does anyone know how to access old/legacy pepper versions? Can I somehow still download them?

If you know where they live on http://gsdview.appspot.com/nativeclient-mirror/nacl/nacl_sdk/ - or you can just poke around there.

We even backport compiler hotfixes for them (e.g. latest fixes for pepper_16 compiler live in http://gsdview.appspot.com/nativeclient-archive2/toolchain/11250~ppapi16/ for newlib toolchain and in http://gsdview.appspot.com/nativeclient-archive2/x86_toolchain/r11250~ppapi16/ for glibc toolchain), but I'm afraid for SDKs that old we only verify that few basic tests pass, nothing more.

 

Or is my only chance to check out some versions from SVN and to build them?

I would not recommend that. You can find instructions for how to checkout old version of Chromium sources on Google easily enough (hint: M16 branch is 912 which means that you can start from here - http://src.chromium.org/viewvc/chrome/branches/912/src/ ) but as you can guess these are not built for over a year and are bitrotted quite a bit. Toolchain is hard enough to compile on some platforms (Mac or versions of Linux newer then Ubuntu 10.04 Lucid), I would imagine Chromium is harder.

 

If so, how do I find out which SVN revision corresponds to which pepper_? version, and how do I actually build it (it seems gclient is required, but only operates on the most recent trunk...)?

It operates on what you give it, really. You can specify branch (e.g. you can give it https://src.chromium.org/chrome/branches/912/src instead of https://src.chromium.org/chrome/trunk/src ), it can checkout specified revisions (we use http://src.chromium.org/native_client/trunk/src/native_client@6941 to pull sources for old version of toolchain), etc.

It's pretty versatile tool, but my recommendation is to just grab old binary version of SDK and use it to upgrade build to the new version of SDK: it's hard enough to find pepper_16 SDK today but sometime in the future it may just disappear!