| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
For convenience for those of us who are running later Ubuntu versions
[endlessm/eos-sdk#444]
[endlessm/eos-sdk#444]
|
|
|
|
|
|
|
|
| |
Move all the tests for the SDK into tests/endless, move all
the demos into tests/demos, move all the smoke tests into
smoke-tests
[endlessm/eos-sdk#444]
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 configure.ac to get @PACKAGE_VERSION@
- Added version() and usage() utilities
[endlessm/eos-sdk#335]
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
| |
Pushing directly to dev, because it is holding up the build.
|
|
|
|
|
|
|
|
| |
This adds the infrastructure for autogenerating HTML documentation from a
Javascript module using NaturalDocs, and then adds documentation comments
to webhelper.js.
[endlessm/eos-sdk#302]
|
| |
|
|
|
|
| |
[endlessm/eos-sdk#1015]
|
|
|
|
|
|
|
|
| |
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]
|
|
|
|
|
|
|
|
|
| |
The dummy file necessary to get 'make check' to do the doc tests
correctly was generated at build time, but that way it doesn't support
the VPATH build that 'make distcheck' tests. The simplest way is to
distribute the dummy file.
[endlessm/eos-sdk#295]
|
|
|
|
|
|
|
|
|
|
| |
This gets rid of a long-standing workaround and makes it easier to
start using a proper test harness for Javascript unit tests.
Unfortunately, it requires a workaround to be able to run gtkdoc-check
on the documentation, but the workaround is not too bad.
[endlessm/eos-sdk#122]
|
|
|
|
|
|
|
|
| |
Now you should be able to import the app generator using
const EndlessWikipedia = imports.wikipedia.EndlessWikipedia;
[endlessm/eos-sdk#206]
[endlessm/eos-sdk#206]
|
|
|
|
|
|
|
|
| |
resource:///com/endlessm/sdk/ is now the official GResource path for SDK
resources. Right now the GResource contains reset.css (from GTK) and
endless-widgets.css (from eos-theme).
[endlessm/eos-sdk#125]
|
|
|
|
|
|
| |
The problem was with needing the serial-tests option in 1.13
More details here
http://gnu-automake.7480.n7.nabble.com/serial-tests-option-and-backwards-compatibility-td19571.html
|
|
|
|
|
|
|
| |
g-ir-doc-tool is buggy, and doesn't build very good documentation,
but it is better than nothing. Building the JS documentation is
turned off by default and turned on for 'make distcheck'.
[endlessm/eos-sdk#18]
|
|
|
|
|
|
|
| |
Use AM_PROG_AR, AM_PROG_CC_C_O, and -Wno-portability to avoid
warnings on Automake 1.12
[#26]
|
|
|
|
|
|
|
| |
After running 'make install', run test/smoke-tests/introspection.js
(and its Python counterpart) to test whether the GIR has been installed
correctly.
[#1]
|
|
|
|
|
|
|
|
| |
Run './configure --enable-gtk-doc' to turn on building documentation,
or use --disable-gtk-doc to disable it (for faster builds.) It builds
as part of the regular 'make' invocation, though you can use 'make
docs' to build only the documentation.
[#1]
|
|
|
|
|
|
|
| |
There are automated tests which run when you do 'make check', and also
smoke tests which demonstrate one piece of functionality, which can be
used as a sort of sanity check or demo.
[#1]
|
|
|
|
|
|
| |
Add infrastructure for translating the single string in the shared
library.
[#1]
|
|
|
|
|
|
| |
Builds a dummy shared library that exports one symbol for testing,
eos_hello_sample_function().
[#1]
|
|
|