Wednesday, November 18, 2015

work in progress 2

Nitro V8 Adapter Cart

Google can be pretty funny with their names. The tool to configure V8 builds is called gyp which is such a lovely term, in just 3 letters the company philosophy is thereby enshrined.

gyp1
dʒɪp/
informal
verb
  1. 1.
    cheat or swindle (someone).
    "a young inventor gypped by greedy financiers"
noun
  1. 1.
    an act of cheating someone; a swindle.

I would consider it even more amusing if gyp was the underlying python management build system for their advertising engine. If sentient systems even need build system management layers....

Anyways, after expanding the main partition to use entire SD card gifting the filesystem with 24GB of free space, today may feature an error free build of the nitro V8 adapter on Pi2.

The build itself started an hour ago with the simple

make -j4 native

The nice thing about V8 is it has a big brother Chromium the browser technology of champions that will, down the track, provide an even more substantial challenge to our mash up plans for 2016.

man page

Linux is a man's world. From the command line type man man for proof.

Here is the boilerplate for the nitro man page.


For those that don't know me, the concept of a bitwise interface is intended to make you giggle.

Nitro V8 Pi2 Progress

OK, after 2 or so hours yesterday's build died during construction of the google tests.

I and the internet both have no idea of the cause so more time required before hitting build on that one.

Argument Encoding

There are two places so far I plan to use a json encoded string as function interface.

Both physics bodies and entities and I suspect materials are going to use constructors based on many arguments encoded in a json object.

The number of methods provided by the platform continues to grow but this will definitely be the last week before a self enforced API freeze occurs.

Files of Interest


The NitroSDK API in C header form can be reviewed here:


It is intended that every function that remains after next cull will be available via local binary, remote network and virtual proxy interfaces.


The only release scheduled in 2015 will be for Raspberry PI after which commitment will switch to manufacture of value added content.