Hi,

Are we allowed to redistribute snn.lib? I'm a little confused, because the Digital Mars license says that we cannot redistribute DM software, yet we link statically to snn.lib in virtually all D programs, which get redistributed.

-- 
- Alex

On 1/19/2012 11:36 AM, Alex Rønne Petersen wrote:
> Are we allowed to redistribute snn.lib? I'm a little confused, because the
> Digital Mars license says that we cannot redistribute DM software, yet we link
> statically to snn.lib in virtually all D programs, which get redistributed.


You can redistribute snn.lib when it is statically linked into a program.

On 19-01-2012 22:36, Walter Bright wrote:
> On 1/19/2012 11:36 AM, Alex Rønne Petersen wrote:
>> Are we allowed to redistribute snn.lib? I'm a little confused, because
>> the
>> Digital Mars license says that we cannot redistribute DM software, yet
>> we link
>> statically to snn.lib in virtually all D programs, which get
>> redistributed.
>
>
> You can redistribute snn.lib when it is statically linked into a program.

Fair enough. However, can I bring the thread on the dmd-internals list about _tls_callbacks_a to your attention then? If I cannot redistribute an snn.lib where this symbol is patched out, this needs fixing, badly.

-- 
- Alex

On 1/19/2012 1:37 PM, Alex Rønne Petersen wrote:
> Fair enough. However, can I bring the thread on the dmd-internals list about
> _tls_callbacks_a to your attention then? If I cannot redistribute an snn.lib
> where this symbol is patched out, this needs fixing, badly.

You don't need to patch the library. Just supply your own tlsdata.obj.

On 1/19/2012 5:40 PM, Walter Bright wrote:
> On 1/19/2012 1:37 PM, Alex Rønne Petersen wrote:
>> Fair enough. However, can I bring the thread on the dmd-internals list about
>> _tls_callbacks_a to your attention then? If I cannot redistribute an snn.lib
>> where this symbol is patched out, this needs fixing, badly.
>
> You don't need to patch the library. Just supply your own tlsdata.obj.
Sure, what do we put in it though?