Making Hexwave work on Steam Deck!
![Image](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgE21wfCGC-A41rMwIXf0SdTLoFy3122px9NxEDEogewcUYLYxL9zeQlc2Wcb5owYVT1mYTrZyWgAi5eiCaYkP_-vhFHRFnkNiLaNL51ePurtVSeisax1f_PiHRPKmy-ol6LgaM80XWWt1os_EAUludwWqBbBGZBzPzatytP4kQVFUNcsFLkc4j5MIt-8n7/w400-h116/hexwaveffmpegissue.webp)
Hi there! Welcome to another Hexwave blog. Hexwave currently only works on Linux, which is currently a blessing in disguise as the Steam Deck runs on Linux and, as I want to make Hexwave run on the Steam Deck, now is a great time to get it working! So, how do we do that? Well, the process was more complicated than anything I've dealt with before. See, Hexwave is made to be extremely flexible. You should be able to compile it, take the compiled binaries, throw it on an older/newer machine, and run it perfectly fine (there will be pre-compiled versions too). However, with the way FFmpeg is currently linked, this doesn't work. If Computer A has FFmpeg 0.0.59 and Hexwave is compiled on Computer A, but Computer B has 0.0.60, Computer B will refuse to run Hexwave, as it's looking for 0.0.59. This is exactly what was happening when I was trying to run Hexwave on the Steam Deck, as FFmpeg on the Steam Deck is more up-to-date than the version in Debian 12 Stable. Now, there are two