InpaintFunc.avs - Different result depending on Avisynth version - Page 4

qyot27 · 27th June 2019, 17:51

GCC should work fine. That was the original use-case for the C interface anyway, so it wouldn't surprise me if that was the basic assumption about how C plugins would be built (although strangely, IIRC I couldn't get 32-bit AviSynth+-GCC to use the 32-bit AVSInpaint GCC build when I was testing it...or I'm remembering wrong). I don't know if there's an issue here concerning avisynth.def, or not. AssRender seemingly used MSVC despite being a C plugin, and its 32-bit builds interact with MSVC builds of AviSynth with no issue.

It's the main reason I now have to compile 3 different builds of FFmpeg for full AviSynth+ support (one for standard MSVC 32-bit, one for standard MSVC or GCC 64-bit, and one expressly for 32-bit AviSynth+-GCC). stdcall vs. cdecl is just a nightmare on 32-bit.

27th June 2019, 17:51	#61 \| Link
qyot27 ...? Join Date: Nov 2005 Location: Florida Posts: 1,420	GCC should work fine. That was the original use-case for the C interface anyway, so it wouldn't surprise me if that was the basic assumption about how C plugins would be built (although strangely, IIRC I couldn't get 32-bit AviSynth+-GCC to use the 32-bit AVSInpaint GCC build when I was testing it...or I'm remembering wrong). I don't know if there's an issue here concerning avisynth.def, or not. AssRender seemingly used MSVC despite being a C plugin, and its 32-bit builds interact with MSVC builds of AviSynth with no issue. It's the main reason I now have to compile 3 different builds of FFmpeg for full AviSynth+ support (one for standard MSVC 32-bit, one for standard MSVC or GCC 64-bit, and one expressly for 32-bit AviSynth+-GCC). stdcall vs. cdecl is just a nightmare on 32-bit.