On 8/24/2017 9:36 PM, Ivan Kalvachev wrote:
> On 8/25/17, James Almer wrote:
>> On 8/24/2017 8:26 PM, Ivan Kalvachev wrote:
>>> On 8/24/17, James Almer wrote:
On 8/24/2017 12:01 PM, wm4 wrote:
> On Thu, 24 Aug 2017 11:20:17 +0200
> Michael Niedermayer wrote:
>
>> On Thu, Aug
On 8/25/17, James Almer wrote:
> On 8/24/2017 8:26 PM, Ivan Kalvachev wrote:
>> On 8/24/17, James Almer wrote:
>>> On 8/24/2017 12:01 PM, wm4 wrote:
On Thu, 24 Aug 2017 11:20:17 +0200
Michael Niedermayer wrote:
> On Thu, Aug 24, 2017 at 10:52:55AM +0200, wm4 wrote:
>> On W
On 8/24/2017 8:26 PM, Ivan Kalvachev wrote:
> On 8/24/17, James Almer wrote:
>> On 8/24/2017 12:01 PM, wm4 wrote:
>>> On Thu, 24 Aug 2017 11:20:17 +0200
>>> Michael Niedermayer wrote:
>>>
On Thu, Aug 24, 2017 at 10:52:55AM +0200, wm4 wrote:
> On Wed, 23 Aug 2017 19:23:12 -0300
> Jame
On 8/24/17, James Almer wrote:
> On 8/24/2017 12:01 PM, wm4 wrote:
>> On Thu, 24 Aug 2017 11:20:17 +0200
>> Michael Niedermayer wrote:
>>
>>> On Thu, Aug 24, 2017 at 10:52:55AM +0200, wm4 wrote:
On Wed, 23 Aug 2017 19:23:12 -0300
James Almer wrote:
> On 8/21/2017 2:51 PM, wm4
On 8/24/2017 12:01 PM, wm4 wrote:
> On Thu, 24 Aug 2017 11:20:17 +0200
> Michael Niedermayer wrote:
>
>> On Thu, Aug 24, 2017 at 10:52:55AM +0200, wm4 wrote:
>>> On Wed, 23 Aug 2017 19:23:12 -0300
>>> James Almer wrote:
>>>
On 8/21/2017 2:51 PM, wm4 wrote:
> From: Pedro Pombeiro
>
On Thu, 24 Aug 2017 11:20:17 +0200
Michael Niedermayer wrote:
> On Thu, Aug 24, 2017 at 10:52:55AM +0200, wm4 wrote:
> > On Wed, 23 Aug 2017 19:23:12 -0300
> > James Almer wrote:
> >
> > > On 8/21/2017 2:51 PM, wm4 wrote:
> > > > From: Pedro Pombeiro
> > > >
> > > > DLL data imports cause
On 8/24/2017 5:52 AM, wm4 wrote:
> On Wed, 23 Aug 2017 19:23:12 -0300
> James Almer wrote:
>
>> On 8/21/2017 2:51 PM, wm4 wrote:
>>> From: Pedro Pombeiro
>>>
>>> DLL data imports cause problems on Windows. They normally require
>>> each variable to be correctly marked with dllimport/dllexport
>>
On Thu, Aug 24, 2017 at 10:52 AM, wm4 wrote:
> On Wed, 23 Aug 2017 19:23:12 -0300
> James Almer wrote:
>
>> On 8/21/2017 2:51 PM, wm4 wrote:
>> > From: Pedro Pombeiro
>> >
>> > DLL data imports cause problems on Windows. They normally require
>> > each variable to be correctly marked with dllimp
On Thu, Aug 24, 2017 at 10:52:55AM +0200, wm4 wrote:
> On Wed, 23 Aug 2017 19:23:12 -0300
> James Almer wrote:
>
> > On 8/21/2017 2:51 PM, wm4 wrote:
> > > From: Pedro Pombeiro
> > >
> > > DLL data imports cause problems on Windows. They normally require
> > > each variable to be correctly mark
On Wed, 23 Aug 2017 19:23:12 -0300
James Almer wrote:
> On 8/21/2017 2:51 PM, wm4 wrote:
> > From: Pedro Pombeiro
> >
> > DLL data imports cause problems on Windows. They normally require
> > each variable to be correctly marked with dllimport/dllexport
> > declspecs. For MSVC, we define av_exp
On 8/21/2017 2:51 PM, wm4 wrote:
> From: Pedro Pombeiro
>
> DLL data imports cause problems on Windows. They normally require
> each variable to be correctly marked with dllimport/dllexport
> declspecs. For MSVC, we define av_export to dllimport declspec. This
> is not entirely correct - dependin
On Mon, 21 Aug 2017 19:51:56 +0200
wm4 wrote:
> From: Pedro Pombeiro
>
> DLL data imports cause problems on Windows. They normally require
> each variable to be correctly marked with dllimport/dllexport
> declspecs. For MSVC, we define av_export to dllimport declspec. This
> is not entirely cor
From: Pedro Pombeiro
DLL data imports cause problems on Windows. They normally require
each variable to be correctly marked with dllimport/dllexport
declspecs. For MSVC, we define av_export to dllimport declspec. This
is not entirely correct - depending on which sub-lib is built, they
should be m
13 matches
Mail list logo