Because we set args to a new value, any arguments passed to
"ade configure" were ignored.

Apertis: https://phabricator.apertis.org/T3978



Signed-off-by: Simon McVittie <smcv@collabora.com>
Reviewed-by: Justin Kim <justin.kim@collabora.com>
Differential Revision: https://phabricator.apertis.org/D6774

Python arguments are passed by reference, so if we append to these
arrays, the caller's copy of the list is modified. This seems unlikely
to be intended.

Signed-off-by: Simon McVittie <smcv@collabora.com>
Reviewed-by: Justin Kim <justin.kim@collabora.com>
Differential Revision: https://phabricator.apertis.org/D6773

Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Reviewed-by: Simon McVittie <smcv@collabora.com>
Differential Revision: https://phabricator.apertis.org/D6742

Currently the sysroot file is named 'sysroot'. This prevents to have
different latests sysroot for different architectures. For example, ade
sysroot latest --arch arm64 returns the url of the armhf sysroot if it
was the last sysroot uploaded.
A symbolic link called sysroot can be used so that older version of
ade are still able to download a sysroot file.

Apertis: https://phabricator.apertis.org/T3849



Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Reviewed-by: Simon McVittie <smcv@collabora.com>
Differential Revision: https://phabricator.apertis.org/D6678

Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Reviewed-by: Emanuele Aina <emanuele.aina@collabora.com>
Differential Revision: https://phabricator.apertis.org/D6426

The current test infrastruture only exercises "ade sysroot".
This test add support to exercise "ade configure" using a mock project
implementation that lures "ade configure" as if a real project was
being configured.
This is done because the test sysroots do not have real autotools.

Apertis: https://phabricator.apertis.org/T3777



Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Reviewed-by: Emanuele Aina <emanuele.aina@collabora.com>
Differential Revision: https://phabricator.apertis.org/D6413

The handler is already present since the info and sysroot subcommand
are already having a --path parameter.

Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Reviewed-by: Emanuele Aina <emanuele.aina@collabora.com>
Differential Revision: https://phabricator.apertis.org/D6412

Create this dummy project to exercise ade configure and build.
autogen.sh and configure are mocking the real scripts behavior.
It is also possible to build from a build directory.

Apertis: https://phabricator.apertis.org/T3777



Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Reviewed-by: Emanuele Aina <emanuele.aina@collabora.com>
Differential Revision: https://phabricator.apertis.org/D6411

The sysroot tag parser was not tested and a regression occured
To catch future regressions make use for ade info and check
that the expected sysroot info can be read during tests.
Add support for --path to the ade info subcommand parser work
in temporary test directory.

Apertis: https://phabricator.apertis.org/T3777



Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Reviewed-by: Emanuele Aina <emanuele.aina@collabora.com>
Differential Revision: https://phabricator.apertis.org/D6390

Currently test_util.py can only test 'ade sysroot'. Additionnaly
it uses about 3 different python syntaxes for parameters. *args
is used for the majority of parameters, path and config are passed as
**kwargs. Finally command, is a positionnal argument.

In order for ade functions other than sysroot can thus be tested,
simplify run_cmd api so that in only take (*args) wth direct arguments.
This means changing all the should_succeed and should_fail calls so
that they no longer assume 'sysroot' is the command to be tested.

Apertis: https://phabricator.apertis.org/T3777



Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Reviewed-by: Emanuele Aina <emanuele.aina@collabora.com>
Differential Revision: https://phabricator.apertis.org/D6410

That error was not defined and triggered an Exception in the Exception.
It was not raised either. Use SysrootManagerError instead

Apertis: https://phabricator.apertis.org/T3777



Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Reviewed-by: Emanuele Aina <emanuele.aina@collabora.com>
Differential Revision: https://phabricator.apertis.org/D6402

Recent parsing changes introduced this regression.

Apertis: https://phabricator.apertis.org/T3777



Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Reviewed-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D6383

Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Reviewed-by: Andrew Shadura <andrew.shadura@collabora.co.uk>
Reviewed-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D6320

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Reviewed-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Differential Revision: https://phabricator.apertis.org/D6265

The current parsing expressions assume release is in the form of
YY.QQ e.g. 16.09. While this is true for Apertis, it's not mandatory for
derivatives so drop that assumption.

While fixing that, move to using match names to make the regexps a bit
more foolproof.

Also split up the function parsing the string from a version file
(/etc/image_version) and from the sysroot version tag as they are
fundamentally different, the current regexp handled both in extremely
subtle and error-prone ways.

Apertis: https://phabricator.apertis.org/T3555



Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Reviewed-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Differential Revision: https://phabricator.apertis.org/D6264

The SysrootVersion class was trying to define a date and build index
from the build identifier. While this is true by convention for the
Apertis builds, this may break in the future.

Instead treat the build identifier as an opaque string consisting of just
digits and dots.

While there, also make all SysrootVersion arguments optional to improve
readability and rename author to variant (which is its intended
meaning).

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Reviewed-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Differential Revision: https://phabricator.apertis.org/D6263

Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Reviewed-by: Emanuele Aina <emanuele.aina@collabora.com>
Differential Revision: https://phabricator.apertis.org/D6205

sudo is used to run ribchesterctl to install a bundle on the target,
but it is not used to run ribchesterctl to install a bundle on the
simulator. Let's change that.

Change a call to ribchesterctl instead of ribchester on the fly.

Apertis: https://phabricator.apertis.org/T3556



Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Reviewed-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D6200

We suppose the intent from the user when configuring an existing
directory is to rebuild all the binaries for the new configuration. For
example, the user could have changed the sysroot.

Apertis: https://phabricator.apertis.org/T3557



Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Reviewed-by: Emanuele Aina <emanuele.aina@collabora.com>
Differential Revision: https://phabricator.apertis.org/D6141

In order to configure different target and build in a different
directory, the build-dir parameter will run configure from a
subdirectory of the root. This allows separating build artifacts
from source code. It allows to build for different targets
at the same time.
Also add support for this in export, run, debug, install, and
uninstall commands.
Do not add it in info command yet.

Apertis: https://phabricator.apertis.org/T3557



Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>
Reviewed-by: Emanuele Aina <emanuele.aina@collabora.com>
Differential Revision: https://phabricator.apertis.org/D6129

ribchesterctl command line tool is being used for bundle handling
like install/uninstall/update and it is shipped along with the
ribchester package.

Signed-off-by: Thushara Malali Somesha <ThusharaM.MalaliSomesha@in.bosch.com>
Reviewed-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D5384

Signed-off-by: Justin Kim <justin.kim@collabora.com>

Prepared man pages are packed into `.deb`.

Signed-off-by: Justin Kim <justin.kim@collabora.com>
Reviewed-by: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D5365

`subprocess.PIPE` returns a bytes object which has no attribute
`read`.

Signed-off-by: Justin Kim <justin.kim@collabora.com>
Reviewed-by: Emanuele Aina <emanuele.aina@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D5358

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

Louis-Francis Ratté-Boulianne authored 8 years ago and Sjoerd Simons committed 8 years ago

When we only want the GDB server running

Signed-off-by: Louis-Francis Ratté-Boulianne <lfrb@collabora.com>
Reviewed-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D5328

Louis-Francis Ratté-Boulianne authored 8 years ago and Sjoerd Simons committed 8 years ago

We were trying to connect the GDB client even before we got the
listening event. The debugger server thread is now looping forever.

Signed-off-by: Louis-Francis Ratté-Boulianne <lfrb@collabora.com>
Reviewed-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D5327

Louis-Francis Ratté-Boulianne authored 8 years ago and Sjoerd Simons committed 8 years ago

If the --app is not given, we check the installed desktop files
and use the main one if that makes sense.

Signed-off-by: Louis-Francis Ratté-Boulianne <lfrb@collabora.com>
Reviewed-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D5326

There is no reason to not allow e.g. an ssh agent or to prevent ade
looking for keys, so drop the restrictions. Also fixes launching the
install job from eclipse as that doesn't seems to pass a user and relies
on ssh key authentication.

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Reviewed-by: Emanuele Aina <emanuele.aina@collabora.com>
Differential Revision: https://phabricator.apertis.org/D5344

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Reviewed-by: Emanuele Aina <emanuele.aina@collabora.com>
Differential Revision: https://phabricator.apertis.org/D5343

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

If ade execv's gdb then its process will be replaced, potentially
causing the ssh connection to the target device to fail which will kill
the remote gdb server. So instead run gdb in a subprocess, keeping ade
(and thus the ssh connection) alive during the debugging session.

Also instead of using gdb, use gdb-multiarch which is a variant capable
of interacting with gdbservers of multiple architectures (and
understand/parsing the debug symbols of multiple architectures). This
means it can be used to debug both ARM and Intel targets, rather then
just native targets.

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Reviewed-by: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D5305

debug-file-directory is the directory where gdb goes to look for
detached debug symbols (the non buildid kind). It's interaction with the
sysroot bits are bit.. odd.. For each debug-file-directory path it will
look in ${path}/${sysroot}/<debuglink> and ${path}/debuglink, both of
which are mostly useless  for sysroots.

Explicitely set the path to ${sysroot}/usr/lib/debug to set gdb
straight.

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Reviewed-by: Guillaume Desmottes <guillaume.desmottes@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D5304

Louis-Francis Ratté-Boulianne authored 8 years ago and Sjoerd Simons committed 8 years ago

Start the gdbserver on device and start gdb client locally in interactive
mode. Default port is not configurable as of now (1234) and other targets
(e.g. simulator, SDK) are not supported.

Signed-off-by: Louis-Francis Ratté-Boulianne <lfrb@collabora.com>
Reviewed-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D5299

Louis-Francis Ratté-Boulianne authored 8 years ago and Sjoerd Simons committed 8 years ago

If the target is a device, we want to know whether to use a
sysroot or the SDK for configuration/debugging/etc.

Signed-off-by: Louis-Francis Ratté-Boulianne <lfrb@collabora.com>
Reviewed-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D5298

Louis-Francis Ratté-Boulianne authored 8 years ago and Sjoerd Simons committed 8 years ago

ARGS options are for the application getting started

Signed-off-by: Louis-Francis Ratté-Boulianne <lfrb@collabora.com>
Reviewed-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D5297

Louis-Francis Ratté-Boulianne authored 8 years ago and Sjoerd Simons committed 8 years ago

The target.run() function expects to receive the arguments
unpacked.

Signed-off-by: Louis-Francis Ratté-Boulianne <lfrb@collabora.com>
Reviewed-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D5287

Louis-Francis Ratté-Boulianne authored 8 years ago and Sjoerd Simons committed 8 years ago

If sysroot is None, it means we want to compile natively (e.g.
for the simulator or for a target device with the same arch)

Signed-off-by: Louis-Francis Ratté-Boulianne <lfrb@collabora.com>
Reviewed-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D5286