You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, pods_use_pkg_config_packages calls pkg-config with the --cflags-only-I option and uses the result to populate the list of include directories. However, this means that pre-processor definitions that packages place in their pkg-config file (e.g for Bullet compiled with double-precision: -DBT_USE_DOUBLE_PRECISION) are ignored.
The text was updated successfully, but these errors were encountered:
i can't see a good reason for not using --cflags instead. but we'll obviously want to test that. On quick inspection, all of the files in my build/lib/pkgconfig directory have only -I commands in their cflags... so it looks pretty safe.
The problem is that the pods macro doesn't just append the cflags, it strips out the directory names and then adds them as include directories via cmake
oh. i see. so it's possible but annoying to have to do the same thing for the remaining flags.
On Mar 27, 2014, at 1:41 PM, Andres Valenzuela [email protected] wrote:
The problem is that the pods macro doesn't just append the cflags, it strips out the directory names and then adds them as include directories via cmake
—
Reply to this email directly or view it on GitHub.
Currently,
pods_use_pkg_config_packages
callspkg-config
with the--cflags-only-I
option and uses the result to populate the list of include directories. However, this means that pre-processor definitions that packages place in their pkg-config file (e.g for Bullet compiled with double-precision:-DBT_USE_DOUBLE_PRECISION
) are ignored.The text was updated successfully, but these errors were encountered: