Orvid King

Assuming the unused properties warning you're referring to is the same one described [here](http://forums.nexusmods.com/index.php?/topic/2211779-removing-unused-properties-warnings-from-scripts/), there's nothing I can do about that. That warning is triggered when there are properties set...

Even if I remove that property, you'll still get a Warning because the actual binding data in the `.esm` is still present. With some significant re-structuring it would be possible...

I can certainly do that, but I'd be putting it behind a `--lint` flag, that would be disabled by default because I'd like to keep the warnings limited to things...

The OCDecorator script in v1.0.5 is a fun one. It was not compiled from a Papyrus script, but was instead done by modifying and re-compiling the Pex assembly file. Champollion's...

For whoever decides to implement this, PHP appears to implement it based on a bit extracted from PostgreSQL [here](https://github.com/php/php-src/blob/0437aa2abf1eb494e4555d7d4dfbdbf566a59bdc/sapi/cli/ps_title.c#L110).

PPC64le isn't currently supported by F14, so prehashing isn't available in the fallback implementation. It looks like the tests for it need to be also be disabled in that mode.

Does https://github.com/facebook/folly/pull/1849 fix this for you? We appear to currently be defaulting to x86_64 if `CMAKE_LIBRARY_ARCHITECTURE` isn't set. (explicitly setting it to any non-empty string should be enough to work...

Folly is fully untested on big endian platforms, including PPC64, though there was some community maintained support for PPC64 little endian a few years back. The title of this issue...

Which version of gtest are you using? It looks like ThrowsMessage was introduced in 1.11.0

This has been there since February, so I'd be inclined to just say we need to ensure getdeps pulls in a new enough version of gtest. Does that sound reasonable?