You’re right, the paths aren’t as expected so the build config process will fail to find them.
Resorting to symlinks shouldn’t be necessary (although when you poke around, linux seems to be built on the idea).
The build system is CMake and there are a couple of ways to specify these locations through it’s flags and environment variables.
They can also be specified through compiler flags.
It takes both to get Hyperion.ng it to build with CEC (the CMake ones alone should be enough) and even then it doesn’t find the library at runtime. So I think there may be a bug in the CMake units.
I have taken this as far as I can myself and filed a bug report. I’ll give them plenty of time to respond. If no fix is forthcoming then I too will be symlinking and I’ll issue the update to 2.0.16 with MDNS and CEC.
For all of that, your CEC experience is not surprising. I’ve found it a nightmare to work with in the past and resorted to hacky workarounds. Implementation varies so wildly with different combinations of device/manufacturer. It either works or it doesn’t!
Glad to hear it’s working.
I doubt you’re missing anything important with an incremental update here.
There were some build issues as referenced above. I was waiting on a bugfix/response from the developers before resorting to a workaround, but didn’t hear back yet.
In the meantime the required mDNS was causing problems with wifi.
Yeah it works like a charm. I can update Hyperion using the method on their site but the internal frame grabber does not work with Kodi. And I am not able to build a version with amlogic support. No skills on that. You think you can help out? Build a fork so I can test things?
Sorry to resurrect such an old thread, but I’ve been relying on @hissingshark’s awesome install script for many years now, firstly on a Vero4K, and I was pleasantly surprised to see it was just as happy on my Vero V.
I’ve just noticed Hyperion has released a new major version (v2.1.1) which seems to have a bunch of new features, bugfixes and performance enhancements.
I was wondering if anyone had any first hand experience building that version from source on a Vero V (using @hissingshark’s installer)? or (if @hissingshark is still monitoring this thread?) whether they might consider making an official pre-built binary?
Either way, thanks for all the effort that went into this @hissingshark - it’s given my family many years of enjoyment.
I had a look at this a little while ago. The build system has become more complicated with way more options. I doubt most of it actually applies to us at all, but it’s meant I’ve been unsuccessful building it on more recent versions.
It’s something I need to come back to. Although I have to say the lack of HDR support is still disappointing. If I can get around to actually sorting out a separate USB grabber I may have to jump ship to Hyper-HDR as that seems to be the only option in that regard.
At least it’s still working for now 
I really appreciate your efforts.