Bug 27247 - Shouldn't hardcode list of wocky headers to install
Summary: Shouldn't hardcode list of wocky headers to install
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: git master
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2010-03-22 10:03 UTC by Will Thompson
Modified: 2010-06-03 11:58 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Will Thompson 2010-03-22 10:03:40 UTC
Currently gabble/Makefile.am has a hard-coded list of Wocky headers to install if installing headers for building plugins is enabled, which can be updated by a helper script in that directory.

This is not ideal. For starters, it's incomplete: it should also include the -enumtypes headers, but my update-y script is not good enough. But actually, we should be able to just do this by running `make install` on Wocky itself. It needs to be conditional, because Gabbles built without --enable-plugin-api shouldn't install Wocky headers. I started doing this but couldn't make it work properly and had other things that needed doing.

http://git.collabora.co.uk/?p=user/wjt/wocky.git;a=shortlog;h=refs/heads/install-headers
http://git.collabora.co.uk/?p=user/wjt/telepathy-gabble-wjt.git;a=shortlog;h=refs/heads/update-wocky-headers-alternate
Comment 2 Will Thompson 2010-04-28 12:18:25 UTC
I like your Wocky branch, but it doesn't merge cleanly. So I reconstructed it, and pushed the reconstruction, with an apology to you. :)

http://git.collabora.co.uk/?p=wocky.git;a=commitdiff;h=9148378692967fbcc8b75ce8822a2ab58b3dee66

Now updating the Gabble one...
Comment 3 Will Thompson 2010-04-28 12:28:47 UTC
(In reply to comment #2)
> I like your Wocky branch, but it doesn't merge cleanly. So I reconstructed it,
> and pushed the reconstruction, with an apology to you. :)

aaaand i broke the build.
Comment 4 Mike Ruprecht 2010-05-30 11:02:25 UTC
I managed to get this working again:

http://git.collabora.co.uk/?p=user/maiku/wocky.git;a=shortlog;h=refs/heads/install-headers
http://git.collabora.co.uk/?p=user/maiku/telepathy-gabble.git;a=shortlog;h=refs/heads/update-wocky-headers-alternate

I noticed though one issue is that if you configure wocky with --with-installed-headers, but without setting it to a value, it installs the headers in a yes/ directory. That happens because if no value is set, AC_ARG_WITH sets the variable to "yes". I'm not sure how best to handle that though or how it should ideally act. Suggestions? or is it fine like it is?
Comment 5 Will Thompson 2010-05-31 08:47:10 UTC
(In reply to comment #4)
> I managed to get this working again:
> 
> http://git.collabora.co.uk/?p=user/maiku/wocky.git;a=shortlog;h=refs/heads/install-headers
> http://git.collabora.co.uk/?p=user/maiku/telepathy-gabble.git;a=shortlog;h=refs/heads/update-wocky-headers-alternate

Look good! (I feel bad, though; maybe you should claim --author-dom of these patches. ☺)

Oh, one thing, the Gabble branch should delete my beautiful gabble/generate-wockyinclude_HEADERS script.

> I noticed though one issue is that if you configure wocky with
> --with-installed-headers, but without setting it to a value, it installs the
> headers in a yes/ directory. That happens because if no value is set,
> AC_ARG_WITH sets the variable to "yes". I'm not sure how best to handle that
> though or how it should ideally act. Suggestions? or is it fine like it is?

I don't think it's that big a deal. I guess the options are, explicitly check for "yes" (and warn/fail), or use some other macro other than AC_ARG_WITH that doesn't have this behaviour? But given that this flag is pretty much just for Gabble's benefit...
Comment 6 Will Thompson 2010-06-03 11:58:48 UTC
Merged this! Hooray.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.