This is unfortunate (given the somewhat generic header names) but that's how it should be used to support non-system-wide installs.
With the previous include set up, building this plugin only worked when bitlbee's headers were in /usr/include/bitlbee, because /usr/include is in the default include path and the -I/usr/include/bitlbee is unused (because /usr/include/bitlbee/bitlbee does not exist)
This is unfortunate (given the somewhat generic header names) but that's how it should be used to support non-system-wide installs.
With the previous include set up, building this plugin only worked when bitlbee's headers were in
/usr/include/bitlbee
, because/usr/include
is in the default include path and the-I/usr/include/bitlbee
is unused (because/usr/include/bitlbee/bitlbee
does not exist)Likely related to #77