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

Some small fixes for nc-config #305

Merged
merged 4 commits into from Aug 17, 2016
Merged

Conversation

ZedThree
Copy link
Contributor

PR #235 fixed a couple of hard-coded paths in nc-config.cmake.in. This PR fixes them in nc-config.in, used by autotools. It also adds some flags which I think should be included: --libdir, by analogy with --includedir; --has-fortran, rather than the specific --has-{f90,f03}, which are only available if nf-config is found; and the flags/libs needed for the C++ API, which can be checked with ncxx{,4}-config, assuming it's been found (by analogy to the Fortran flags/libs).

This was fixed in a previous commit for nc-config.cmake.in, but not for
the autotools version
pkg-config isn't used in the cmake version of nc-config, so probably
shouldn't be used in autotools version either?
- Add --has-fortran, in addition to the specific --has-f90, --has-f03
- Add --libdir to print just the libdir
- Also 'which nf-config' will spit out errors if nf-config is not found.
  Silence these errors
@WardF
Copy link
Member

WardF commented Aug 17, 2016

Very helpful and much appreciated, thanks! Reviewing now, will merge shortly unless issues are discovered. Thanks!

@WardF WardF added this to the 4.4.1.1 milestone Aug 17, 2016
@WardF WardF self-assigned this Aug 17, 2016
@WardF WardF merged commit bf7e5b3 into Unidata:master Aug 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants