close#1197
1) linuxcnc.in new option: -H dirname
to prepend 'dirname' to search path (HALLIB_PATH)
2) linuxcnc.in update usage() message
3) update docs: ini-config.txt
4) update docs: updating-linuxcnc.txt
Revised:
print HALLIB_PATH when '-H dirname' used
exit if specified dirname is invalid
Note: the dirname specified with '-H dirname' may be
absolute or relative to the working directory
where linuxcnc is invoked (not necessarily the ini
config dir). Example:
$ cd /tmp
$ mkdir try
$ echo "show pin axis.z" >|try/test.hal
$ linuxcnc -H try /somewhere/example.ini # uses test.hal
test.hal will be found as /tmp/try/test.hal
latency-histogram uses a mix of uS and uSec as units of time. But
large case S is the unit Siemens, and second should never be
shortened to "sec" or "Sec".
This patch changes to [greek letter mu]s in the GUI but uses "us" in
the terminal, since not all terminals support UTF-8.
fix for occaisonal buildbot failures for tests/motion-logger/mountaindew
that occur coincident with reports of excessive (> 1second) task latency
excursions like:
"task: 307 cycles, min=0.000155, max=1.804823, avg=0.014539, 7 latency excursions ..."
Scenario:
1) At termination of [DISPLAY]DISPLAY=test-ui.py, the linuxcnc script
initiates shutdown by sending a SIGTERM to linuxcncsvr and milltask.
2) On a heavily loaded buildbot system (showing task latencies like above),
the delivery of the SIGTERM to milltask may be delayed such that
the linuxcncsvr process exits well before milltask and the final
EMCMOT_DISABLE message is undeliverable to the motion-logger
process resulting in absence of the final expected motion-logger
"DISABLE" report.
3) This commit sends the SIGTERM to the motion-logger process also
so the race-dependent final "DISABLE" report is no longer
expected.
These tests refer to files outside the `tests` directory. To make the
tests function disembodied from the source tree and against a system
install, add rules to the build to copy the needed files in place, and
adjust the tests to work properly.
Also, the `personalities_mod` test did something funky: it overwrote
standard comps with modified versions, then replaced those when the
test finished. This patch undoes that, and instead renames the comps.
Some tests make assumptions about header and library locations; these
are correct for an RIP build but not for a system build.
This patch removes those assumptions and supplies the locations as
environment variables directly from the `runtests` script.
The `halcompile` script installs user comps in `/usr/bin` by default.
For testing temporary test user comps against a system install, teach
`halcompile` to put them in the test directory and run the test from
there.
Adds a possibility to owerwrite 'checklink' by using:
$ ac_cv_path_CHECKLINK=<path-to-executable> ./configure
Note: Specifying '/usr/bin/true' as follows:
$ ac_cv_path_CHECKLINK=/usr/bin/true ./configure
can be used to build the html documentation on machines
(usually builders) which by design disables network access
during a build process.
Signed-off-by: Damian Wrobel <dwrobel@ertelnet.rybnik.pl>
It is designed to be used for checking compatibility of python
scripts (currently only from the 'tests' subdirectory) with
both python2 and python3 interpreters.
Usage:
$ make pycheck
Successfull output:
$ make pycheck
Reading 200/200 dependency files
Done reading dependencies
Reading 212/212 realtime dependency files
Done reading realtime dependencies
Checking *.py files for python2 and python3 compatibility...
Checking "text/x-python" (by MIME type) files for python2 and python3 compatibility...
Signed-off-by: Damian Wrobel <dwrobel@ertelnet.rybnik.pl>
Fixes error:
grep: /etc/apt/sources.list.d/*: No such file or directory
which happens when you run:
$sudo scripts/travis-install-build-deps.sh
in an official ubuntu:16.04 docker image.
Signed-off-by: Damian Wrobel <dwrobel@ertelnet.rybnik.pl>
