Chiebot-Mirror
/
meson
mirror of https://github.com/mesonbuild/meson.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
The Meson Build System http://mesonbuild.com/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
13080 Commits
76 Branches
171 Tags
74 MiB
Tag: Branch: Tree: 6860e42c06
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '6860e42c06'
${ noResults }
meson/test cases/unit/90 devenv/meson.build

18 lines
568 B
Raw Normal View History Unescape

Revert "devenv: Set PYTHONPATH where we install python modules" This reverts commit 79c6075b560dbf1c3e4e0b30f1c472dc2086421e. # Conflicts: # docs/markdown/snippets/devenv.md # mesonbuild/modules/python.py # test cases/unit/91 devenv/test-devenv.py PYTHONPATH cannot be reliably determined. The standard use case for installing python modules with Meson is mixed pure sources (at least `__init__.py`) and compiled extension_modules or configured files. Unfortunately that doesn't actually work because python will not load the same package hierarchy from two different directories, one a source directory and one a (mandatory) out of tree build directory. (It kind of can, but you need to do what this test case accidentally stumbled upon, which is namespace packages. Namespace packages are a very specific use case and you are NOT SUPPOSED to use them outside that use case, so people are not going to use them just to circumvent Meson devenv stuff as that would have negative install-time effects.) Adding PYTHONPATH anyway will just lead to documentation commitments which we cannot actually uphold, and confusing issues at time of use because some imports *will* work... and some will *not*. The end result will be a half-created tree of modules which just doesn't work together at all, but because it partially works, users attempting to debug it will spend time wondering why parts of it do import. For any case where the automatic devenv would work correctly, it will also work correctly to use `meson.add_devenv()` a single time, which is very easy to manually get correct and doesn't provide any significant value to automate. In the long run, an uninstalled python package environment will require "editable installs" support.
3 years ago
project('devenv', 'c')
Add `meson devenv` command and meson.add_devenv()
4 years ago
meson.add_devenv('TEST_A=1')
foo_dep = dependency('foo', fallback: 'sub')
env = environment()
env.append('TEST_B', ['2', '3'], separator: '+')
meson.add_devenv(env)
Allow setting method/separator in environment() and meson.add_devenv()
3 years ago
meson.add_devenv({'TEST_B': '0'}, separator: '+', method: 'prepend')
env = environment({'TEST_B': ['4']}, separator: '+', method: 'append')
meson.add_devenv(env)
Add `meson devenv` command and meson.add_devenv()
4 years ago
# This exe links on a library built in another directory. On Windows this means
# PATH must contain builddir/subprojects/sub to be able to run it.
executable('app', 'main.c', dependencies: foo_dep, install: true)