Closed hsghost closed 2 years ago
THMonster
commented
2 years ago I have no idea about this. Theoretically, it should be fine on aarch64. Tauri will consume a large amount of both RAM and disk space on building, 2GB is definitely not enough.
hsghost
commented
2 years ago Worked around the above problem by setting NODE_OPTIONS=--max_old_space_size=1536, which is 2 GB - 512 MB, as suggest in vitejs/vite#2433.
Yet, some other hidden dependencies were discovered - libwebkit2gtk-4.0-dev, libjavascriptcoregtk-4.0-dev, libgtk-3-dev, librust-openssl-dev, libdbus-1-dev and pkg-config, and may be even more on a barebone Debian distor - which should be covered in the README or Wiki, I suggest. It took me several hours to resolve these all.
hsghost
commented
2 years ago Well, it finished the build process, yet stuck the same problem of JavaScript heap overflow during make install. What an unfortunate outcome...
I can see that the build has made a .deb file under some path, is it possible to install it directly through dpkg? Any side effect installing it like this?
THMonster
commented
2 years ago Worked around the above problem by setting
NODE_OPTIONS=--max_old_space_size=1536, which is2 GB - 512 MB, as suggest in vitejs/vite#2433.Yet, some other hidden dependencies were discovered -
libwebkit2gtk-4.0-dev,libjavascriptcoregtk-4.0-dev,libgtk-3-dev,librust-openssl-dev,libdbus-1-devandpkg-config, and may be even more on a barebone Debian distor - which should be covered in the README or Wiki, I suggest. It took me several hours to resolve these all.
This is the difference between distros, I cannot list all the trivia from every distros. For example, webkit2gtk means you should install some about webkit2gtk on your distro, it may not be called "webkit2gkt" exactly on your distro.
THMonster
commented
2 years ago Well, it finished the build process, yet stuck the same problem of JavaScript heap overflow during
make install. What an unfortunate outcome...I can see that the build has made a
.debfile under some path, is it possible to install it directly throughdpkg? Any side effect installing it like this?
That deb file is auto packing by tauri build system, I don't recommend to using that.
hsghost
commented
2 years ago Hmm... I've tried it. Seems it only installs the GUI part. The dmlive daemon is not installed, so nothing functioning, I guess.
Will try to tweak the JavaScript heap later, see if I could get it to work.
hsghost
commented
2 years ago Manually copying the dmlive executable into /usr/bin does the trick, although I may have to change my distro again as I discovered there's no mpp support for hwdec on the current one, so mpv is constantly dropping frames.
Anyway, it's fairly possible to get Revda to work on a resource limited ARM SBC, I conclude. Actually, I managed to get the older version qliveplayer to work on a Ubuntu on Surface 3, which also had merely 2 GB of RAM, without any frills. Just reporting these to the community, so that anyone interested can make reference.
Thanks for your work, @THMonster .
Hi there,
I'm trying to build and install Revada on a Debian distribution on Tinker Board, which employs a Rockchip RK3288 SoC, which is of
armhfarchitecture, and 2 GB of RAM. All of the earlier procedures went smoothly, untilmake:I've tried both setting up a swap, and
NODE_OPTIONS=--max_old_space_size=4096, yet nothing seemed to help. Still failed with the same error messages.Any ideas on this? I understand that the app is designed to run under x86/x64, is this the cause? Could there be a possibility for porting?
Thanks,