Michael Smith

Thanks for replying so quickly! Let's see... > Overall, yes, any Clang binary should in principle be able to cross compile for any target; if you call the clang binaries...

> Unfortunately, the way this is done right now, by setting `-DCLANG_DEFAULT_RTLIB=compiler-rt` when doing the cmake configuration, it applies to any cross target. Allowing to hardcode different defaults for different...

> Yeah - I generally have a rather hard policy of not carrying local patches in my distribution - the only customization is in wrapper scripts or in the build...

Update on the Defender theory: I figured out how to disable it (you have to go through safe mode, seriously?) and concluded that it makes no difference. Got all the...

> FWIW I went ahead and tried to make a stripped down, MSVC-targeting build of the toolchain, have a go at https://martin.st/temp/llvm-mingw-msvc-x86_64.zip. I built this with these tweaks: https://github.com/mstorsjo/llvm-mingw/commits/msvc-toolchain This...

> Right, so previously - within the same command prompt, you build for both 32 and 64 bit, and don't have those env vars set, and then rely on Clang...

Hi, I decided to do a quick Google; apparently desktop Spotify uses Vorbis while web Spotify uses MP3 (maybe for compatibility or something?). So there's no way to do this...

I'm pretty sure the default is a direct rip but I'll need check once I log into my computer. If it is then you can just FFMpeg it from there...

This is an [upstream issue](https://github.com/TooTallNate/node-spotify-web/issues/130), by the way, so whatever solution is required will probably be worked out there or in some fork.

I don't know why everyone's still saying "same here." This tool hasn't worked for a while, unfortunately, and I don't know if anyone is working to fix it. You can...