Dear list readers,
>> Yes, this: "-static" when you link the installer executable will pull in
>> static libraries if available, and my toolchains have everything in DLL and
>> static library form.
> As simple as that? i had read that, but i thought it was specific
> to one single user build. A
Dear Ruben, dear Xunxun,
> Yes, this: "-static" when you link the installer executable will pull in
> static libraries if available, and my toolchains have everything in DLL and
> static library form.
As simple as that? i had read that, but i thought it was specific
to one single user build. Ag
2012/5/21 xunxun
> Add -static to your linker option
Yes, this: "-static" when you link the installer executable will pull in
static libraries if available, and my toolchains have everything in DLL and
static library form.
Ruben
>
> On Mon, May 21, 2012 at 9:30 PM, MARTIN Pierre wrote:
>
>>
Add -static to your linker option
On Mon, May 21, 2012 at 9:30 PM, MARTIN Pierre wrote:
> Dear list readers,
>
> i have a question relative to the MinGW-w64 runtimes (Correct
> me if i'm wrong: libgcc_s_sjlj-1.dll and libstdc++-6.dll).
> All my projects are fine with the dynamic version of the r
Dear list readers,
i have a question relative to the MinGW-w64 runtimes (Correct
me if i'm wrong: libgcc_s_sjlj-1.dll and libstdc++-6.dll).
All my projects are fine with the dynamic version of the runtimes.
But one of my project (In fact an installer) would require a static
version of those DLLs,
On Mon, May 21, 2012 at 9:28 AM, Kyle wrote:
> Hi,
>
> I just updated my MinGW-w64 tool chain and am having issues compiling
> FFmpeg now.
>
> I'm getting:
> /home/kyle/software/ffmpeg/source/ffmpeg-git/libavdevice/dshow.h:35:1:
> error: unknown type name 'VIDEO_STREAM_CONFIG_CAPS'
[...]
That's b
