Doom9's Forum - View Single Post

qyot27 · 22nd March 2019, 00:09

It's been quite a while since the last time we tried this, so here's a GCC build of AviSynth+:
AviSynth+ (GCC) r2831-g316b54aa-20190321

And a corresponding pair of FFmpeg and mpv builds that include builds capable of handling otherwise-difficult 32-bit GCC builds of AviSynth+:
FFmpeg r93433+7
mpv r46865+11

Unlike the previous GCC build of AviSynth+, it now will not interfere with your existing plugin folders. There is a separate registry entry and plugin folder path GCC builds look for, plugins+gcc. Examples below - change the path accordingly for where AviSynth+ is installed, but the point is that the plugins folder for GCC builds of AviSynth+ should be separate from the folder(s) for normal MSVC builds.

64-bit:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth]
@="E:\\Programs\\AviSynth+"
"plugindir2_5"="E:\\Programs\\AviSynth+\\plugins64"
"plugindir+"="E:\\Programs\\AviSynth+\\plugins64+"
"plugin+gcc"="E:\\Programs\\AviSynth+\\plugins64_gcc"

32-bit:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth]
@="E:\\Programs\\AviSynth+"
"plugindir2_5"="E:\\Programs\\AviSynth+\\plugins"
"plugindir+"="E:\\Programs\\AviSynth+\\plugins+"
"plugindir+gcc"="E:\\Programs\\AviSynth+\\plugins_gcc"

C-plugins should work with the GCC builds (the FFMS2 C-plugin definitely works). C++ plugins will not (excepting possibly if they were built with g++, but I've not tried this yet).

For those not wanting duplicate copies of FFMS2-C floating around, symbolic links should work fine.

22nd March 2019, 00:09	#4597 \| Link
qyot27 ...? Join Date: Nov 2005 Location: Florida Posts: 1,420	It's been quite a while since the last time we tried this, so here's a GCC build of AviSynth+: AviSynth+ (GCC) r2831-g316b54aa-20190321 And a corresponding pair of FFmpeg and mpv builds that include builds capable of handling otherwise-difficult 32-bit GCC builds of AviSynth+: FFmpeg r93433+7 mpv r46865+11 Unlike the previous GCC build of AviSynth+, it now will not interfere with your existing plugin folders. There is a separate registry entry and plugin folder path GCC builds look for, plugins+gcc. Examples below - change the path accordingly for where AviSynth+ is installed, but the point is that the plugins folder for GCC builds of AviSynth+ should be separate from the folder(s) for normal MSVC builds. 64-bit: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth] @="E:\\Programs\\AviSynth+" "plugindir2_5"="E:\\Programs\\AviSynth+\\plugins64" "plugindir+"="E:\\Programs\\AviSynth+\\plugins64+" "plugin+gcc"="E:\\Programs\\AviSynth+\\plugins64_gcc" 32-bit: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\AviSynth] @="E:\\Programs\\AviSynth+" "plugindir2_5"="E:\\Programs\\AviSynth+\\plugins" "plugindir+"="E:\\Programs\\AviSynth+\\plugins+" "plugindir+gcc"="E:\\Programs\\AviSynth+\\plugins_gcc" C-plugins should work with the GCC builds (the FFMS2 C-plugin definitely works). C++ plugins will not (excepting possibly if they were built with g++, but I've not tried this yet). For those not wanting duplicate copies of FFMS2-C floating around, symbolic links should work fine. Last edited by qyot27; 22nd March 2019 at 11:17.