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

Generate and install pkg-config file for slint_cpp #7219

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

task-jp
Copy link
Contributor

@task-jp task-jp commented Dec 25, 2024

No description provided.

@ogoffart
Copy link
Member

Thanks.
Looks sensible.
I don't know much about pkg-config. How is one supposed to use it? How will it work with the slint-compiler?

@tronical
Copy link
Member

I think this may be a generally useful feature to have, but I have concerns similar to Olivier:

  • I think the target interface compile features should be propagated (via cflags?) if possible. (For Msvc we’d also need the compile options, but perhaps we don’t need msvc support?)
  • It’s unclear to me how other properties like the enabled/disabled feature list becomes accessible to pkg-config users.
  • As this may likely break, we should IMO have an automated test that ensures this feature continues to work (build systems are fragile :-)
  • If we decide to support pkg-config consuming build systems in Slint, then we need to document how this works, what the limitations are, and how users can correctly invoke the Slint-compiler.

If we can come to an agreement on these points (scope and what is going to be implemented), then I think this makes sense to take in as first PR.

@task-jp could you elaborate on your use-case here? Is cmake not an option in the environment you’d like to use Slint in?

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

Successfully merging this pull request may close these issues.

3 participants