Should a config be automatically generated?

[KingEdogaa]

So this isn't really for me, it's for someone else having an issue who does not have a github account. They use Debian Linux and they ran it twice.

Anyways, they compiled the software from source and when they ran it, they looked for the configuration files, under .config. There was nothing, we know that the regular discord client creates a directory under .config, does this work the same way? If so, any idea why it doesn't?

Or does it not work at all similarly to how discord does and we have to create the directory?

May not be able of getting answers too quickly since they are often busy but trying to see if there are any clear answers, I guess?

[KingEdogaa]

So I figured out part of it, no idea if the issue is resolved on their end but it seems that they used Void Linux and i assumed Debian because it was their prior distro. Thus, I started up a VM and set it up myself, here are instructions I wrote for any future user based of what I understood from how i set things up on my void install running XFCE.

Void Linux Installation Instruction for discord-screenaudio
Step one, run:
xbps-install cmake base-devel qt5-webengine-devel qt5-webchannel-devel qt5-location-devel knotification-devel kxmlgui-devel pkg-config pipewire pipewire-devel wireplumber-devel git

step two: remove pulseaudio if you set it up on your system since pipewire is a drop in replacement anyways.

xbps-remove pulseaudio

Step Three: read the docs on how to set up pipewire https://docs.voidlinux.org/config/media/pipewire.html

here is what I did in my VM install, but not everyone might want to set it up this way

ln -s /usr/share/applications/pipewire.desktop /etc/xdg/autostart/pipewire.desktop
ln -s /usr/share/applications/pipewire-pulse.desktop /etc/xdg/autostart/pipewire-pulse.desktop
mkdir -p /etc/pipewire/pipewire.conf.d
ln -s /usr/share/examples/wireplumber/10-wireplumber.conf /etc/pipewire/pipewire.conf.d
reboot

The rest is to follow the install guide in the read me, git clone, cd, cmake...etc etc... and then you can run it like any other application or in the build directory if you aren't installing it systemwide.

Hopefully this helps others...