path: root/tools/
Commit message (Collapse)AuthorAge
* Do not link eos-profile with libendlessEmmanuele Bassi2018-03-21
| | | | | | | | We don't depend on any specific Endless SDK symbols, and if we link against the SDK library itself we end up enabling the profiling probes; this means we may end up overwriting the profiling data we're trying to open, if by any chance we have `EOS_PROFILE=capture:` in our environment pointing to the profile data we're opening.
* Add a diff tool for the eos-profile toolEmmanuele Bassi2018-03-21
| | | | | Compares N probe data files and prints a quick overview with the average timings of all the probes.
* Add eos-profile-convert commandEmmanuele Bassi2018-03-21
| | | | | | | | | | If we want to perform additional analysis on a profile capture file it's generally going to be easier to have it in a different format than a GVDB binary blob, especially if we want to use tools that are written in high level languages that may not have access to the GVDB API. The simplest format we can convert to is JSON, which is structured and easy to parse with other languages.
* Add show command to eos-profileEmmanuele Bassi2018-01-19
| | | | | The `show` command loads a list of profile capture files and prints the metadata and sample summary.
* Add CLI tool for loading profiling apturesEmmanuele Bassi2018-01-18
| | | | | | Captures of profiling data are saved in a binary format, and we need a tool that can load them and turn them into user readable (or machine readable) data.
* Add eos-html-extractor and m4 filePhilip Chimento2015-06-04
| | | | | | | | | | | | This is taken almost directly from the existing version in eos-english. Cleanups to follow in subsequent commits. Previously the m4 code was in two separate macros, but since they were much the same, I combined them into one macro. This also adds a very minimal test for eos-html-extractor; basically as a very quick regression test for the cleanups to follow. [endlessm/eos-sdk#3245]
* Remove ancient test runnerPhilip Chimento2015-04-17
| | | | | | | This test runner dates from even before eos-jasmine, and is not used anywhere. [endlessm/eos-sdk#3054]
* Integrated JSON extraction utilityFernando2013-12-10
| | | | | | | | | | | | The utility used in eos-english and eos-programming-app was integrated and installed as part of the SDK CR comments addressed include: - Integrated new facilities available on GTK - Removed duplicate prototype declaration - Reformatted CLEANFILES var declaration - Used to get @PACKAGE_VERSION@ - Added version() and usage() utilities [endlessm/eos-sdk#335]
* Subcommand 'eos-application-manifest init'Philip Chimento2013-12-09
| | | | | | | | | This implements the 'init' subcommand of the application manifest tool, which creates a new manifest in the current directory. [endlessm/eos-sdk#154] [endlessm/eos-sdk#154]
* eos-application-manifest: Install subcommands in $libexecdirPhilip Chimento2013-12-09
| | | | | | | $libexecdir/eos-application-manifest, instead of $datadir/eos-application-manifest [endlessm/eos-sdk#154]
* 'eos-application-manifest' tool with subcommandsPhilip Chimento2013-10-18
| | | | | | | | This is the framework for an 'eos-application-manifest' tool with subcommands as in git. Currently the 'help' and 'version' subcommands are implemented. [endlessm/eos-sdk#152]
* First attempt at an EOS test runnerPhilip Chimento2013-09-16
This adds a script eos-run-test which is adapted from gjs_run_tests, but does not try to discover the tests itself. Instead, in keeping with Automake's test suite facilities, it takes the filename of a test to run. [endlessm/eos-sdk#290]