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

pkg-config pc files not created for *_threads libs #180

Open
cimes-isi opened this issue Sep 11, 2019 · 4 comments
Open

pkg-config pc files not created for *_threads libs #180

cimes-isi opened this issue Sep 11, 2019 · 4 comments

Comments

@cimes-isi
Copy link

It appears that pc files are not being created (or at least installed) for the libraries that provide thread-related functions, which makes it difficult to automatically discover if these libraries are available. PR #52 describes nicely FFTW's position on threading, but since functions like fftw[f]_threads_init are provided by the FFTW *_threads libraries, those FFTW libraries need to be discoverable, even if their pkg-config files leave the actual thread linking to the application (e.g., -lpthread).

@matteo-frigo
Copy link
Member

I think that the right approach to this problem is to say that installing libFOO_threads.{a.so} installs a separate file FOO_threads.pc (as opposed to adding the threads library to the normal fftw3.pc file).
Does it sound reasonable?

@cimes-isi
Copy link
Author

Yes, that is what I'd expect. FOO_threads.pc should in turn have a Requires (or perhaps Requires.private) on FOO since libFOO.{a,so} is a transitive dependency.

@samueljmcameron
Copy link

I would be interested in this feature as well, though mainly for mpi, not threading.

@antoniovazquezblanco
Copy link
Contributor

I am currently dealing with this issue. It seems to get more complicated when fftw is installed via brew in a non-standard location and the compiler does not find the library by itself so meson build system needs extra configuration...

It would be awesome to see this fixed...

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

No branches or pull requests

4 participants