jasmine-gjs:master

Last commit made on 2024-02-12
Get this branch:
git clone -b master https://git.launchpad.net/jasmine-gjs

Branch merges

Branch information

Name:
master
Repository:
lp:jasmine-gjs

Recent commits

c6aa28b... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

build: Substitute uninstalled variables when in subproject

If a project includes jasmine-gjs as subproject for its test
suite, it currently needs to pass a couple of environment
variables for jasmine to work uninstalled.

Now that we no longer install anything when used as subproject,
we can instead use the right substitutions, so projects can use
jasmine in their test suite without special-casing the subproject
case.

6817661... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

build: Do not install from subproject

Projects that include jasmine-gjs as subproject will typically
use it to run their own test suite with `meson test`, which means
that jasmine-gjs only runs from the build directory.

There is therefore little use for installing jasmine alongside
the project. In fact, it can cause problems for packagers when
multiple projects end up installing their own copy.

Avoid this and simply don't install anything when used as
subproject.

7b1c735... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

build: Skip tests when in subproject

Projects that include jasmine-gjs as subproject want to test
their own code, not jasmine-gjs.

0b0cb39... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

Minimize differences when running uninstalled

Instead of using a completely different code path for setting
up imports, override only the substituted variables from the
environment.

261183b... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

build: Adjust substituted config variables

We variables we currently substitute allow setting up imports
when running installed, but need a separate code path for the
uninstalled case.

Using slightly different variables will allow us to change that.

a8d8bb8... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

tests: Don't get fixtures path from env

Now that tests are loaded as modules, we can use `imports.meta.url`
to resolve the path to fixtures instead of passing the directory
in the environment.

451a1b4... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

build: Use correct jasmine script in tests

Referencing the script as string makes assumptions about the
working directory. Instead, use the result of configure_file().

7f66a51... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

build: Replace deprecated get_pkgconfig_variable()

The type-specific get_*_variable() functions were deprecated in
meson 0.56.0. Avoid a warning with newer meson versions and
switch to the replacement.

d8254f8... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

build: Specify install_dir with install_data()

Omitting the install_dir from install_data() has only worked correctly
from inside a subproject since meson 1.3.0.

6fbd6d8... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

build: Allow using as meson subproject

Mark the `jasmine` target as a possible provider of a
`find_program('jasmine')` dependency. This allows
projects to pull in jasmine-gjs as wrap/subproject.