summaryrefslogtreecommitdiff
path: root/Makefile.am
Commit message (Collapse)AuthorAge
* Added Creative Commons LicensesFernando Farfan2015-05-05
| | | | | | | | | | | | | | | | | | | | | | Added HTML files for Creative Commons lincenses to be presented offline. Licenses added include: * BY-3.0 * BY-4.0 * BY-ND-2.0 * BY-ND-3.0 * BY-SA-3.0 * BY-SA-4.0 For all these, the following languages were added: * No language suffix: Copy of the English file as fallback * Arabic * English * Spanish * French * Portuguese (Brazil) [endlessm/eos-sdk#3025]
* Address warning about rule being overwrittenPhilip Chimento2015-04-17
| | | | | | | There are two dist-hook rules, so a double-colon rule is appropriate. That means both will get executed when required, instead of only one. [endlessm/eos-sdk#3054]
* Don't define dist_noinst_DATA in included MakefilePhilip Chimento2015-04-17
| | | | | | | This is vulnerable to being overwritten. Instead, define it in the top level Makefile and append to it in the included Makefile. [endlessm/eos-sdk#3054]
* Enable Gjs and C coverage reports.Sam Spilsbury2015-01-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We now provide a new m4 module eos-coverage.m4, which is installed into the system aclocal directory. This macro provides three new commands for SDK consumers to use: EOS_COVERAGE_REPORT([languages]) - Enables a "coverage report". The first argument is a space separated list of unquoted languages to collect coverage information for. Valid values at the moment are "c" and "js". For each language specified, the macro will check for support for collecting coverage and enable reporting accordingly. Raw coverage output goes in $(abs_top_builddir)/_coverage/output/$language accordingly. The macro then checks to see if a coverage reporter, either genhtml, or cobertura, is available and enables them. A reporter must be installed and available for coverage reports to be generated. The coverage-genhtml is enabled if lcov is installed and available. This is generally used by developers themselves as it creates a self-contained report. The coverage-covertura is enabled if a program called lcov-result-merger is installed and a python module called lcov_cobertura are installed. lcov-result-merger can be installed from Node Package Manager. lcov_cobertura can be installed from PyPI. lcov-result-merger is necessary because each test suite is run in a separate subprocess and so there will be multiple entries per source file in the coverage.lcov file generated by gjs. lcov_cobertura doesn't handle that properly and so the results need to be merged together properly. JavaScript Coverage Details =========================== A variable called EOS_JS_COVERAGE_FILES should be defined containing a list of all javascript files to be considered a "part of" the coverage report, before EOS_COVERAGE_RULES are substituted. For example: EOS_JS_COVERAGE_FILES = $(SRCS) @EOS_COVERAGE_RULES@ AM_JS_LOG_FLAGS += @EOS_COVERAGE_JS_LOG_FLAGS@ C/C++ Coverage Details ====================== Certain additions also need to be made for Makefiles where coverage reporting is enabled on a C project: @EOS_COVERAGE_RULES@ AM_CFLAGS += @EOS_C_COVERAGE_CFLAGS@ AM_LDFLAGS += @EOS_C_COVERAGE_LDFLAGS@ If a target's CFLAGS is overridden and AM_CFLAGS is not used, then @EOS_C_COVERAGE_CFLAGS@ must be added to its CFLAGS. Blacklisting patterns ===================== If a path should not appear in the coverage report, then it can be blacklisted by adding a glob expression to EOS_COVERAGE_BLACKLIST_PATTERNS. Clean rules =========== A clean-coverage target is added to the dependencies for the clean-local target automatically by EOS_COVERAGE_RULES. [endlessm/eos-shell#2264]
* Remove eos-gir.m4, not used anymorePhilip Chimento2014-05-28
| | | | | | This was originally designed to be installed into the system aclocal directory, but we copy it into each project's m4 directory instead. This is to try to fix the build for [endlessm/eos-sdk#693].
* Remove Endless Wikipedia library from SDKRory MacQueen2014-05-27
| | | | [endlessm/eos-sdk#693]
* Clean up the structure of the tests directorySam Spilsbury2014-01-15
| | | | | | | | 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]
* Add README.md to distPhilip Chimento2013-10-04
|
* Documentation for WebHelperPhilip Chimento2013-09-19
| | | | | | | | 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]
* Added asset button to the endless overrideMatt Watson2013-09-18
| | | | | | | | The syntax can will hopefully stay the same for apps when this widget gets rewritten in C. Added support for labels like the standard button. Moved the overrides rules to a separate .inc makefile so we can add more standard js libs if we want [endlessm/eos-sdk#290]
* Move test autotooling to test/Makefile.am include filePhilip Chimento2013-09-18
| | | | | | | | The autotools code for running the tests should go in the included Makefile.am in the test/ subdirectory, so that all those test files are run and distributed in the same place. [endlessm/eos-sdk#290]
* Unit tests for webhelperPhilip Chimento2013-09-16
| | | | | | | | | These are tests for the basic functionality and a few fail cases of webhelper, by no means exhaustive. There are a few tests that cannot execute because I do not currently know of any way to catch exceptions that occur inside GObject callbacks. [endlessm/eos-sdk#290]
* 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]
* Merge pull request #292 from endlessm/issues/289mattdangerw2013-09-12
|\ | | | | Install WebHelper into GJS modules directory
| * Install WebHelper into GJS modules directoryPhilip Chimento2013-09-12
| | | | | | | | | | | | | | | | WebHelper is now importable using const WebHelper = imports.webhelper; [endlessm/eos-sdk#289]
* | Use Automake's parallel test harnessPhilip Chimento2013-09-04
|/ | | | | | | | | | 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]
* Merge pull request #219 from endlessm/wikipediaP. F. Chimento2013-08-02
|\ | | | | Merge Wikipedia into dev
| * Integrate Wikipedia into SDK build systemPhilip Chimento2013-08-02
| | | | | | | | | | | | | | | | Now you should be able to import the app generator using const EndlessWikipedia = imports.wikipedia.EndlessWikipedia; [endlessm/eos-sdk#206] [endlessm/eos-sdk#206]
* | Autoconf macros for checking GIR filesPhilip Chimento2013-07-22
|/ | | | | | | | | EOS_PROG_GJS checks for the existence of GJS in the path; EOS_CHECK_GJS_GIR checks that a GIR can be loaded in GJS, optionally with a certain version number; and EOS_CHECK_GJS_GIR_API checks for particular API being available in a GIR in GJS. [endlessm/eos-sdk#168]
* Merge pull request #89 from endlessm/issues/86Felipe Erias Morandeira2013-05-22
|\ | | | | Ensure that Gtk-Doc and GIR doc are enabled for distributions
| * Ensure that Gtk-Doc and GIR doc are enabled for distributionsP. F. Chimento2013-05-16
| | | | | | | | | | | | 'make dist' and 'make distcheck' do not work without calling ./configure --enable-gtk-doc --enable-gir-doc. [endlessm/eos-sdk#86]
* | Added --warn-all flag to g-ir-scanner call.Matt Watson2013-05-16
|/ | | | Warns about any non introspectable functions in the public API.
* Added javascript override to the page manager add functionmatt2013-05-16
| | | | | | Added the autotooling to get our overrides installing as well. [endlessm/eos-sdk#70]
* Build Javascript API documentationP. F. Chimento2013-05-06
| | | | | | | 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]
* Run tests verboselyP. F. Chimento2013-04-22
| | | | | | | Without the verbose flag, gtester just says "1 test passed" or "1 test failed", which is not very informative. [#26]
* Build library before docsP. F. Chimento2013-04-22
| | | | | | | Build system improvement. Otherwise building docs fails on a clean checkout. [#26]
* Enable GObject introspectionPhilip Chimento2013-04-17
| | | | | | | After running 'make install', run test/smoke-tests/introspection.js (and its Python counterpart) to test whether the GIR has been installed correctly. [#1]
* Autogenerate documentation with Gtk-docPhilip Chimento2013-04-17
| | | | | | | | 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]
* Add test frameworkPhilip Chimento2013-04-17
| | | | | | | 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]
* Internationalize the shared libraryP. F. Chimento2013-04-17
| | | | | | Add infrastructure for translating the single string in the shared library. [#1]
* Skeleton build system to build a shared libraryPhilip Chimento2013-04-17
Builds a dummy shared library that exports one symbol for testing, eos_hello_sample_function(). [#1]
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-07 12:02:22 +0000