BitHeaven
/
picom
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

README: mentions how to specify header/library path 

Closes #155

Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com>
This commit is contained in:
Yuxuan Shui 2019-04-14 13:32:33 +01:00
parent aee496aeff
commit adc52798db
No known key found for this signature in database
GPG Key ID: 37C999F617EA1A47
1 changed files with 13 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -54,14 +54,22 @@ $ meson --buildtype=release . build
$ ninja -C build $ ninja -C build
``` ```
On FreeBSD, `ld` does not look by default in /usr/local/lib, and you will get errors about some libraries being not found. Built binary can be found in `build/src`
To fix that, prepend `LDFLAGS="-L/usr/local/lib"`:
If you have libraries and/or headers installed at non-default location (e.g. under `/usr/local/`), you might need to tell meson about them, since meson doesn't look for dependencies there by default.
You can do that by setting the `CPPFLAGS` and `LDFLAGS` environment variables when running `meson`. Like this:
```bash ```bash
$ LDFLAGS="-L/usr/local/lib" meson --buildtype=release . build $ LDFLAGS="-L/path/to/libraries" CPPFLAGS="-I/path/to/headers" meson --buildtype=release . build
$ ninja -C build
``` ```
Built binary can be found in `build/src` As an example, on FreeBSD, you might have to run meson with:
```bash
$ LDFLAGS="-L/usr/local/include" CPPFLAGS="-I/usr/local/include" meson --buildtype=release . build
$ ninja -C build
```
### To install ### To install