Turns out I had -static-libgcc added to the wrong line.  It needs to be 
in DLLWRAP, not CXXFLAGS.  The compile with that flag added succeeded 
and eliminated libgcc_s_sjlj-1.dll and libstdc++-6.dll from the 
dependencies.  Still didn't work though - my DAW spun for a while on 
rescanning the VST directory, started up and still doesn't show the 
newly generated VST under effects or instruments.

On 4/4/2015 1:19 PM, Aaron Altman wrote:
> objdump -x suggests that this might be due to a couple of mingw libraries:
>
> root@altie-VirtualBox:~/faust-examples# objdump -x karplus.dll | grep DLL
>       DLL
>    vma:            Hint    Time      Forward  DLL       First
>       DLL Name: KERNEL32.dll
>       DLL Name: msvcrt.dll
>       DLL Name: USER32.dll
>       DLL Name: libgcc_s_sjlj-1.dll
>       DLL Name: libstdc++-6.dll
>
> According to
> http://stackoverflow.com/questions/12921911/mingw-libgcc-s-sjlj-1-dll-is-missing
> I should add "-static-libgcc" to my CXXFLAGS in faust2w32vst.  I tried
> that and still see the same lines in objdump.  Giving it some more
> thought...
>
> On 4/4/2015 12:57 PM, Aaron Altman wrote:
>> Hi all.  I'm struggling to get a toolchain set up that will allow me
>> to use the Faust-STK examples as VSTis on Windows 7 x64.  Has anyone
>> pulled this off?
>>
>> The closest I've gotten so far is to compile one of them in a
>> virtualized Linux environment with `faust2w32vst` and then copy it
>> back out into my VST folder.  When I rescan that folder in my DAW, the
>> new instrument (let's say, harpe) doesn't show up.
>>
>> I thought maybe this could be due to a difference in calling
>> conventions or a missing dependency.  When I open the resulting
>> harpe.dll up in Dependency Walker, it shows missing dependencies on
>> the following DLLs:
>>
>> API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL
>> API-MS-WIN-CORE-WINRT-ERROR-L1-1-0.DLL
>> API-MS-WIN-CORE-WINRT-L1-1-0.DLL
>> API-MS-WIN-CORE-WINRT-ROBUFFER-L1-1-0.DLL
>> API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
>> API-MS-WIN-SHCORE-SCALING-L1-1-1.DLL
>> DCOMP.DLL
>> IESHIMS.DLL
>>
>> A little bit of googling around suggests that that's due a missing
>> MSVC++ runtime, but I've installed every one I can find.  Any ideas?
>>
>> If I had a clear path to compile with Visual Studio 2013, that would
>> also avoid the issue.  Anyone pulled that off recently?
>>
>> Thanks,
>>
>> Aaron
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Faudiostream-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/faudiostream-users


------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Faudiostream-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/faudiostream-users

Reply via email to