cb36add970
When an older version of the library being built is installed in the same prefix as external dependencies, we have to be careful to construct the linker or compiler command line. If a -L flag from external dependencoes comes before a -L flag pointing to builddir, it is possible for the linker to load older libraries from the installation prefix instead of the newly built ones, which is likely to cause undefined reference error. Since the order of dependencies is not significant, we cannot expect internal dependencies to appear before external dependencies when recursively iterating the list of dependencies. To make it harder to make mistakes, linker flags come from internal and external dependencies are now stored in different order sets. Code using _get_dependencies_flags are expected to follow the order when constructing linker command line: 1. Internal linker flags 2. LDFLAGS set by users 3. External linker flags It is similar to what automake and libtool do for autotools projects. |
||
|---|---|---|
| ci | ||
| ciimage | ||
| cross | ||
| data | ||
| docs | ||
| graphics | ||
| man | ||
| manual tests | ||
| mesonbuild | ||
| msi | ||
| test cases | ||
| tools | ||
| .appveyor.yml | ||
| .coveragerc | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| COPYING | ||
| MANIFEST.in | ||
| README.md | ||
| __main__.py | ||
| contributing.md | ||
| ghwt.py | ||
| meson.py | ||
| mesonconf.py | ||
| mesonintrospect.py | ||
| mesonrewriter.py | ||
| mesontest.py | ||
| run_cross_test.py | ||
| run_meson_command_tests.py | ||
| run_project_tests.py | ||
| run_tests.py | ||
| run_unittests.py | ||
| setup.cfg | ||
| setup.py | ||
| sideci.yml | ||
| skip_ci.py | ||
| wraptool.py | ||
README.md
Status
Dependencies
Installing from source
You can run Meson directly from a revision control checkout or an
extracted tarball. If you wish you can install it locally with the
standard Python distutils command python3 setup.py install <your options here>.
Meson is also available from
PyPi, so it can be installed
with pip3 install meson (this does not require a source checkout,
pip will download the package automatically). The exact command to
type to install with pip can vary between systems, be sure to use the
Python 3 version of pip.
Running
Meson requires that you have a source directory and a build directory and that these two are different. In your source root must exist a file called 'meson.build'. To generate the build system run this command:
meson <source directory> <build directory>
Depending on how you obtained Meson the command might also be called
meson.py instead of plain meson. In the rest of this document we
are going to use the latter form.
You can omit either of the two directories, and Meson will substitute the current directory and autodetect what you mean. This allows you to do things like this:
cd source_root; mkdir builddir; cd builddir; meson ..
or
cd source_root; mkdir builddir; meson builddir
To compile, cd into your build directory and type ninja. To run unit
tests, type ninja test.
Install is the same but it can take an extra argument:
DESTDIR=/destdir/path ninja install
DESTDIR can be omitted. If you are installing to system directories,
you may need to run this command with sudo.
Contributing
We love code contributions. See the contributing.txt file for details.
IRC
The irc channel for Meson is #mesonbuild over at Freenode.
Further info
More information about the Meson build system can be found at the project's home page.
Meson is a registered trademark of Jussi Pakkanen