Re-opening: this is not the correct fix. A driver should only access what's available using lirc-driver.h; having all sors of private headers available is opening a can of worms.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The real problem here is a bad include path in media/lirc.h; this is already fixed in [87c021] without changing the .pc file include paths. Ditching clumsy patch which makes all sorts of private headers visible in the driver.
Users not using master running into this issue could change
#include<config.h>
to
#include<lirc/config.h>
in include/media/lirc.h. Downstream patches will take this approach.
Fixed in [712f35], closing
Related
Commit: [712f35]
Re-opening: this is not the correct fix. A driver should only access what's available using lirc-driver.h; having all sors of private headers available is opening a can of worms.
The real problem here is a bad include path in media/lirc.h; this is already fixed in [87c021] without changing the .pc file include paths. Ditching clumsy patch which makes all sorts of private headers visible in the driver.
Users not using master running into this issue could change
to
in include/media/lirc.h. Downstream patches will take this approach.
Related
Commit: [87c021]
Last edit: Alec Leamas 2017-05-08
Fix was broken, resulting in downstream bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872074. Finally fixed in [ec4232] (master) and [11e1e9] (release-0.10)
Related
Commit: [11e1e9]
Commit: [ec4232]