It is normal and expected for agent entry points to not have an icon.

Signed-off-by: Simon McVittie <smcv@collabora.com>
Reviewed-by: Emanuele Aina <emanuele.aina@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D6858

`ade configure` and `ade build` have `--native` option, but `install`
and `uninstall` commands doesn't. To install/uninstall a bundle which
is built with `--native`, user should use `ade install --simulator`
because two options actually do same thing.
For the consistency, the option, `--native`, is added.

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

When unparsed arguments were picked out, they were appended
to args. This is problematic if the wrapped command takes
command-line options with values of the form "--foo bar" (as
opposed to --foo=bar), because they would be re-ordered to "bar --foo",
likely causing a syntax error. It is obviously also a problem if
order is significant for the wrapped command. Prepend the unparsed
arguments to args instead of appending.

Signed-off-by: Simon McVittie <smcv@collabora.com>
Reviewed-by: André Magalhães <andre.magalhaes@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D6798

Picking out the known arguments and leaving unknown arguments is
dangerous, because typos and prefix-matching can have unintended
results. To discourage this, warn if any unknown arguments were
found. These are all considered correct, and are equivalent
(except for order):

    ade configure --native -- VARIABLE=1 --with-option
    ade configure --native VARIABLE=1 --with-option
    ade configure --native -- --with-option VARIABLE=1

but this will now provoke a warning for --with-option:

    ade configure --native --with-option VARIABLE=1

Signed-off-by: Simon McVittie <smcv@collabora.com>
Reviewed-by: André Magalhães <andre.magalhaes@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D6797

The common convention of passing "--" as a separator between
arguments for this command and arguments for the wrapped command
did not work, because it would also pass the "--" through. For
instance, "ade configure --native -- --device=foo" should pass
"--device=foo" to the configure script instead of interpreting it
as ade's own --device option.

Signed-off-by: Simon McVittie <smcv@collabora.com>
Reviewed-by: André Magalhães <andre.magalhaes@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D6796

Subcommands with no REMAINING arguments, such as "ade uninstall",
would previously accept and ignore unknown arguments. This could be
very bad if the command is something like "ade uninstall --dry-run".

Signed-off-by: Simon McVittie <smcv@collabora.com>
Reviewed-by: André Magalhães <andre.magalhaes@collabora.co.uk>
Differential Revision: https://phabricator.apertis.org/D6795

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

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

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

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

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

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

`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

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

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

 * Directory for apps is Applications not Application
 * Don't set --sysconfdir so the AppArmor profile is in the
   right directory

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/D5280

ribchester-bundle is a python3-gi based application which is capable of
doing some low-level operations in ribchester, ribchesterctl is a
simpler C application installed as part of the ribchester package which
can at the moment only do install and remove (which is exectly what ade
is doing).

Move ade to use ribchestectl so it doesn't need anything not normally
installed on a target device. Also for operation on a target device use
sudo (an ssh user is not allowed to install applications).

While there, also copy bundles to /tmp rather then hardcode the users
home directory (which could change in the future).

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

Differential Revision: https://phabricator.apertis.org/D5261

ade install failed for me as my target device doesn't have
ribchester-bundle, however it did so without giving any indication
something was wrong at all.

Sort this out by raising an exception if the remote command returns a
non-zero exit status.

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

Differential Revision: https://phabricator.apertis.org/D5260

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

Signed-off-by: Louis-Francis Ratté-Boulianne <lfrb@collabora.com>

Differential Revision: https://phabricator.apertis.org/D5233

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

Signed-off-by: Louis-Francis Ratté-Boulianne <lfrb@collabora.com>

Differential Revision: https://phabricator.apertis.org/D5232

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

Signed-off-by: Louis-Francis Ratté-Boulianne <lfrb@collabora.com>

Differential Revision: https://phabricator.apertis.org/D5231

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

Signed-off-by: Louis-Francis Ratté-Boulianne <lfrb@collabora.com>

Differential Revision: https://phabricator.apertis.org/D5230

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

Signed-off-by: Louis-Francis Ratté-Boulianne <lfrb@collabora.com>

Differential Revision: https://phabricator.apertis.org/D5245

Unless a compiler which produces code for the target is setup, the
result of the compilation (if successful) will just be native code which
isn't helpful. Setup target specific gcc && linker instead

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/D5257

The intention here is to point to the /usr/include in the sysroot,
however when joining an absolute paths the result will just be the last
absolute paths

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/D5256

We're using four different ways to define the achitecture. There is the
machine name as given by e.g. uname -m, the dpkg architectures (armhf,
amd64, etc) and finally the gnu arch triplet (e.g. aarch64-linux-gnu).
Have TargetTriplet recognize all three and properties for all three
variants.

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/D5253