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

fluidsynth-1.1.5 cmake no pkg-config #101

Closed
derselbst opened this issue Dec 9, 2011 · 4 comments
Closed

fluidsynth-1.1.5 cmake no pkg-config #101

derselbst opened this issue Dec 9, 2011 · 4 comments

Comments

@derselbst
Copy link
Member

If auto* is depreciated, cmake should install a pkg-config file.

Reported by: santabutthead

Original Ticket: fluidsynth/tickets/102

@derselbst
Copy link
Member Author

A pkg-config file (fluidsynth.pc) is installed on Unix like systems (for instance, Linux), but it is not installed in Windows. The reason is that pkg-config is popular and required for building software under Linux, but not in Windows. If the auto-tools buildsystem is deprecated or not is irrelevant in this case.

Original comment by: pedrolcl

@derselbst
Copy link
Member Author

Very relevant if cross-compiling.

Original comment by: santabutthead

@derselbst
Copy link
Member Author

  • owner changed from diwic3 to plcl
  • status changed from new to accepted

The auto-tools build system also uses and requires pkg-config, being deprecated or not. Fluidsynth using cmake and pkg-config does not imply that any other project using Fluidsynth needs to use cmake and pkg-config as well. That is the case of QSynth (available for Linux, Windows and Mac OSX), that uses cmake but links to libfluidsynth without needing pkg-config at all, because it detects and configures Fluidsynth in a different way.

Anyway, the argument of the request is nonsense, but I don't mind to add fluidsynth.pc to the install target of cmake.

Original comment by: pedrolcl

@derselbst
Copy link
Member Author

  • status changed from accepted to closed
  • resolution set to fixed

done in r440

Original comment by: pedrolcl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants