[omniORB] omniORB licensing: Too strict for real life?

[Helge Penne]

We're looking into this at the moment, but the problem is this:

As we're talking about an embedded system, the library will have to include object code
for the libraries of a commercial real time operating system.  I'd be quite surprised
if their licensing terms permitted redistribution of their libraries in linkable
form....
2. The linker for this operating system might not support this kind of library linkage
to the extent necessary (the jury is still out on this).

What it all boils down to is that despite kind suggestions, I still haven't seen a
solution that would permitt us to use omniORB in a legally acceptable way without
distributing full source code for the application, something that is unacceptable to
the owner of the code.

If this is really the case, we'll either have to abandon omniORB or enter into some
kind of license term negotiations.

One of the points that I have been trying to get across is that the LGPL works just
fine for platforms like UNIX and Windows, where dynamic linkage is simple and easy.
For platforms or applications where dynamic linkage is impossible and free source code
is out of the question, it seems to leave you out in the cold if you need to use the
tool toghether with commercial tools.
I don't think the Free Software Foundation or the authors of omniORB had any of this in
mind when they decided on the license terms.

It would simply be to mind numbingly stupid to get stuck in a catch 22 situation like
this due to a legal technicality that none of the license authors probably even were
aware of at the time.

- Helge

David Riddoch wrote:

> On Tue, 25 May 1999, Helge Penne wrote:
>
> > One potential problem remains, however: The OS might force us to link statically
> > with omniORB, as the support for dynamic link libraries is somewhat limited.  Can
> > we still distribute the application without providing application source code or
> > complete object files, or will we run into license confilcts in this area too?
>
> Helge,
>
> The situation is that your customer must be able to relink a modified
> version of omniORB.  I understand that your problem is that you cannot
> distribute other third-party libraries which are part of your system.  All
> I can suggest is that you find some way to re-package these libraries and
> your object code in a way that makes everyone happy.
>
> Would it be possible to link these libraries with the object code of your
> application into a new library?  Then to relink, your customer just has to
> link this library and the omniORB library (probably with a dummy object
> file which ought to reference main).  I have no idea how to do this -- but
> I think it ought to be possible!
>
> David

--
Helge Penne (helge.penne@datarespons.no)
Senior Software Development Engineer
Data Respons AS, Postboks 489, N-1323 Høvik, Norway
Phone: +47 67112081 / 22719957 (work/home)