| From: | Martin Baute |
| Date: | 5 Sep 2000 at 11:24:52 |
| Subject: | Re: Elate Ports & Legal Rubbish (was AMIOPEN: vpcc as a C++ compiler) |
Hello Gary
On 04-Sep-00, you wrote:
> On Sun, 3 Sep 2000 14:19:17 +0100, owner-open@amiga.com "Matthew J
> Fletcher" <amimjf@connectfree.co.uk> wrote:
>> Which reminds me, i asked a while ago about the NDA coverage of elates
>> internals, if a port needs some elate spesific code (i.e not c cleanups
>> or ansi stuff) but say elate threading, can these changes be made public
>> ?
>
> No, our SDK (other than the actual GPL stuff) is proprietary.
Please elaborate on this.
There is open source project X. I make some changes to the source
which make includes and calls to SDK libraries, like
#ifdef SYSTEM_ELATE
#include "/usr/amiga/lib/whatever.h"
void foo()
{
call_to_some_elate_function();
}
#endif
...and successfully make the maintainers of X merge these changes
back into the main source tree.
The program would now work on Elate / Ami, too. No source or library
from the SDK has been included in the X archive; I only made calls to
code only available to those owning a SDK.
Is this still against the "spirit" of the SDK NDA?
Regards
Subscribe/Unsubscribe: open-request@amiga.com
Amiga FAQ: http://www.amiga.com/faq.html