Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix build #4

Closed
Closed

Conversation

MathieuDuponchelle
Copy link
Contributor

Fixing various issues encountered when building the AudioManager with the default options in a custom prefix (-DCMAKE_INSTALL_PREFIX=[...])

The wrong variables from pkg_check_modules were used,
effectively forcing the inclusion of dlt.h to happen
from /include.

Fix this to take advantage of pkg-config and allow building
against a non-system-wide dlt-daemon.
The -L flags were not retrieved from pkg_check_modules, except
for automotive-dlt, where LDFLAGS was added to the LIBS variable,
which was then passed to TARGET_LINK_LIBRARIES.

This led to compile-time errors when compiling in a custom
prefix.

We also propagate the LIB_DIRECTORIES and use them in
AmControlInterfaceTest and AudioManagerDaemon.
The regeression was introduced by 791557b, fix it in
a similar fashion.
pkg-config looks for the exact, case-sensitive names listed
in the requirements.
MathieuDuponchelle added a commit to MathieuDuponchelle/AudioManagerPlugins that referenced this pull request Oct 26, 2016
There were two issues on my machine:

The dependencies are installed in a custom prefix, we thus make
use of the newly-defined AudioManagerUtilities_LIB_DIRECTORIES
variable (see GENIVI/AudioManager#4)

-std=gnu++11 -Wno-variadic-macro needed to be set in the CXXFLAGS
First issue is that libraries might be installed to lib64,
not lib.

Second issue is that these libraries aren't installed in
$(libdir)/audiomanager , simply $(libdir), thus adding
the suffix is wrong.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants