-
Notifications
You must be signed in to change notification settings - Fork 879
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
[BUILD] Added macros resolved in srt.h to pkg-config file #2806
base: dev
Are you sure you want to change the base?
[BUILD] Added macros resolved in srt.h to pkg-config file #2806
Conversation
|
How do you get access to libssl then? This is also using pkg-config in the SRT build. This will likely have to use the right version of pkg-config from the cross-compile toolchain. I found something about it here |
openssl is built and installed by the maintainer of the build computer. SRT is kind of part of the firmware build |
Ok, so there's an alternative, enabled with If enabled, these flags will be placed in the generated version.h file. This file is automatically included by The controversy is that every user that is including the SRT header will have to use |
…t do not use pkg-config
Turning to draft: the way better method to do this is to provide the information about the compile options, but still the |
Fixes #2610
Replaces #2696
There are several preprocessor macros that are used as conditionals in srt.h; they should be always resolved before including this file.
In order to achieve this, you should add the result of
pkg-config --cflags srt
to your applications' compile command line options, just as well the result ofpkg-config --libs srt
to your applications' linker options. This will provide all required options your application should be compiled with, including macrodefinitions with which the library was originally compiled.