Isn't $(prefix)/include/stm32.h too generic?

[blacklion]

I'm not sure, is it bug or "as intended" but previous versions of stlink (1.6.0 and earlier) installed main include/stlink.h and several other headers under include/stlink/.
1.6.1 installs include/stlink.h, include/stm32.h and several other headers under include/stlink/.
Is it as intended? stm32.h looks too generic to be installed into system-wide include directory, isn't it?

[Nightwalker-87]

These project paths are still subject to change because of ongoing work. We had to find an interim solution for the recent Release v1.6.1, because we could not restructure the project all at once. Please give us some time to address this along with general improvements.

[Nightwalker-87]

I've reorganised some project source & header directories now.
However we still have stm32.h installed to /usr/local/include/ as it is solely linked to stlink.h.
Related to #903 I expect further changes around here. Looking at this, it should be ok for now.