Closed Be-ing closed 3 years ago
@emabrey can you look into this?
Yeah this is my bad. I forgot to add in the code to fix this. I anticipated this problem when I was working on this, but I just lost track of it while I was working on it I guess.
Are there any workaround to this for now?
Thanks for looking into this @emabrey.
@TheEvilSkeleton I've been commenting out the code in the about dialog locally. :/
@Be-ing can you show me how/where/what you commented? I don't know much about programming. I wouldn't mind making a patch for the flatpak for the time being, so we can at least get a working flatpak publicly as soon as possible.
Here is the line that is failing in your Flatpak build: https://github.com/tenacityteam/tenacity/blob/a30f84e449eb3bcbb722a1e8b346a92a5c89904d/src/AboutDialog.cpp#L241
Just add //
to the front of the line. Or wait for @emabrey to fix the bug.
@TheEvilSkeleton I made a quick patch that the Flatpak can use, and made a PR for your Flatpak repo. https://github.com/TheEvilSkeleton/flatpaks/pull/6
I forgot to put the #ifdef
s back because I was going to modify the CMake configuration, but upon looking through it there's no quick and easy way to do this that I can figure. I wanted to use the ternary setup since there is a lot of chance for #ifdef
to hide code compilation problems, but they didn't configure CMake to spit out the macros at all if there is an OFF configuration.
Right now the cmake config options get mapped like so:
use_portmixer = ON, local, system, etc. -> #define USE_PORTMIXER = 1
use_portmixer = OFF -> USE_PORTMIXER = <undefined>
So I just added some ifdef
s to revert the changes I was going to make until I can finish it.
I forgot to put the #ifdefs back
I am confused. #361 did not remove #ifdefs for these optional features.
Likely a regression from #361