Open dvzrv opened 2 years ago
After explicitly removing the common/freeverb directory before build, I am able to build successfully.
@dvzrv Thanks for reporting this, I'll see what I can do about a fix for the next version.
@dvzrv Is anybody maintaining the system freeverb3 package? If not, it might be better to build against the bundled freeverb3.
The package for Arch is maintained by me. However, the upstream is here: http://www.nongnu.org/freeverb3/
Judging from its history I don't see a lot of activity in the past years though: http://git.savannah.gnu.org/cgit/freeverb3.git Not sure whether that will change or not, but given that those are the sources you are using, what would be the upside to using the bundled sources you provide with dragonfly-reverb?
Sometimes I consider modernizing the freeverb3 library that is bundled with Dragonfly Reverb, doing things like finding a better way to avoid issues with denormals and such. I hesitate to diverge from the version at savannah.gnu.org because I know that some people build using the SYSTEM_FREEVERB3 env var, but if I didn't have to support that, it would give more freedom to optimize the bundled library.
Sometimes I consider modernizing the freeverb3 library that is bundled with Dragonfly Reverb, [..]
Then these changes should be upstreamed IMHO, so that others also benefit from it. Have you reached out to the current freeverb3 upstream about these changes?
The freeverb3 maintainer didn't write me back the last time I wrote, but I can try again.
I'd love there to be an optimized bundled freeverb3 just for dragonfly reverb. Disk space is relatively cheap, plus I can see what is being optimized.
@dvzrv Are there other arch packages that depend upon freeverb3?
Sorry for the late reply: Nope, not currently.
@dvzrv I think this will still be a problem with 3.2.7, as I am not currently set up to test a build on Arch Linux against the system freeverb3 library.
Hi! When building 3.2.6 as a package for Arch Linux I ran into issues:
This looks freeverb related and I am using
SYSTEM_FREEVERB3="true"
. Maybe it is not honored in some parts of the build?