chore: support building libstrophe as a subproject#2141
chore: support building libstrophe as a subproject#2141jubalh merged 1 commit intoprofanity-im:masterfrom
Conversation
45ebd0f to
9e55deb
Compare
|
Huge 👎 from me on this. Only because one can do something doesn't necessarily mean it's a good idea. Next step would then be if there's no compiler you download the GCC sources and build that one? |
|
Yes, I'm not sure. You have automatic dependency resolution and installation for binary packages in most GNU/Linux distros. |
|
I like the change. Sometimes it happens that we need a change on libstrophe. Usually then jaeckel implemented in there. We have had this a couple of times in the past, probably the issues are tagged So we get a new feature request/bug -> it needs a change in libstrophe -> change is implemented there but only on master -> people can use this feature to build profanity with latest git libstrophe -> people can easily test and give feedback/use the new feature. What I'm unsure about is the So I think I would prefer to have this via a switch? |
Allow building the latest libstrophe from upstream Git automatically when -Dforce_fallback_for=libstrophe is passed. Default to find and link against system-provided libstrophe stays the same. Signed-off-by: Paul Fertser <fercerpav@gmail.com>
9e55deb to
5670ccb
Compare
When pkg-config doesn't find usable libstrophe this will download and build it automatically.