diff options
author | Jin^eLD <jin@mediatomb.cc> | 2014-03-23 02:01:45 +0100 |
---|---|---|
committer | Jin^eLD <jin@mediatomb.cc> | 2014-03-23 02:05:57 +0100 |
commit | 70475d281dacb742e807c78a7f0fc951d85044a3 (patch) | |
tree | 6bbb2453a2b248b0644107e8b9e3f3add76e35a5 /libtoxcore.pc.in | |
parent | ba4681ef1eafe6de3742e037da01c1e069777470 (diff) |
Fix NaCl builds for *BSD
From what I see there is a difference between *BSD and Linux when
linking vs. toxcore which has been bulit vs. the NaCl library:
on Linux it only links if NaCl's object files (i.e. randombytes.o) is
present in the linker options, however on *BSD systems this will cause a
linking error, see:
https://github.com/Tox/toxic/issues/31#issuecomment-38224441
This commit makes sure that we do not add the NaCl object files to our
pkg-config settings on *BSD, but do add them on Linux.
Diffstat (limited to 'libtoxcore.pc.in')
-rw-r--r-- | libtoxcore.pc.in | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/libtoxcore.pc.in b/libtoxcore.pc.in index 1e2b9365..57d3f8ef 100644 --- a/libtoxcore.pc.in +++ b/libtoxcore.pc.in | |||
@@ -7,5 +7,5 @@ Name: libtoxcore | |||
7 | Description: Tox protocol library | 7 | Description: Tox protocol library |
8 | Requires: | 8 | Requires: |
9 | Version: @PACKAGE_VERSION@ | 9 | Version: @PACKAGE_VERSION@ |
10 | Libs: -L${libdir} @NACL_LDFLAGS@ -ltoxcore @NACL_LIBS@ @LIBS@ | 10 | Libs: @NACL_OBJECTS_PKGCONFIG@ -L${libdir} @NACL_LDFLAGS@ -ltoxcore @NACL_LIBS@ @LIBS@ |
11 | Cflags: -I${includedir} | 11 | Cflags: -I${includedir} |