[Mono-dev] make install doesn't copy monodroid profile assemblies to the prefix directory

[Jeremy Bell]

Thanks Rodrigo.

If you would, could you clarify on the issue of the AMQP driver? Do you
mean the RabbitMQ library? So this would affect System.Messaging.dll,
Mono.Messaging.dll, Mono.Messaging.RabbitMQ.dll, and RabbitMQ.Client.dll,
correct?

I'm not familiar with this RabbitMQ project but it is listed as being dual
licensed under The Apache License v2 and The Mozilla Public License,
although it has commercial support options. The Apache license should allow
for modifications to the original library (and thus indirectly any
generated code) and also distribution in binary form without the end-user
reverse engineering requirement of the LGPL. As for the other DLLs - the
source for those are all under mono/mcs/class, which lists the MIT license
at the root of that directory, so in theory these should be free to
distribute. Am I missing some dependency in the driver or the above DLLs?


Thanks again,
Jeremy



On Wed, May 29, 2013 at 9:05 PM, Rodrigo Kumpera <kumpera at gmail.com> wrote:

> The runtime is a mixture of LGPL and MIT and the BCL is mixture of MIT/X11
> and compatible licenses such as the Microsoft variant of MIT.
>
> As the Debian guys found out there are some non-free files used to
> generate some files, but the byproduct is fine. This is for the AMQP
> driver, I believe. They are non-free because they cannot be changed even if
> they can be distributed freely.
>
>
>
> On Wed, May 29, 2013 at 12:59 PM, Jeremy Bell <bell.jeremy at gmail.com>wrote:
>
>> Thanks Rodrigo. Copying sounds like the way to go.
>>
>>
>> As an aside, this is for an open source project and the intent is to use
>> the core mono runtime under the terms of the LGPL as stated in the
>> licensing documentation. If there is any code in the mono repository that
>> isn't dual licensed (in other words, commercial only, with no option for
>> LGPL use), that needs to be made explicitly clear, as currently there is no
>> mention of such in the licensing doc.
>>
>> Regards,
>> Jeremy
>>
>>
>>
>>
>> On Wed, May 29, 2013 at 12:22 PM, Rodrigo Kumpera <kumpera at gmail.com>wrote:
>>
>>> There are no install target as those assemblies are not consumed in a
>>> standard way, it's very useful to have them on either the GAC or a profile
>>> directory.
>>>
>>> What we do at Xamarin is to have them consumed as part of our product
>>> build, mostly due to historical reasons.
>>>
>>> If you're using Xamarin.Android beta and have a paid license[1], you can
>>> copy them over. Yes, it's brittle, I'm sorry for that.
>>>
>>> But it's something that should be fixed on the build system.
>>>
>>> Cheers,
>>> Rodrigo
>>>
>>> [1]Starter edition doesn't allow random assemblies be used for the BCL.
>>>
>>>
>>>
>>> On Wed, May 29, 2013 at 12:10 PM, Jeremy Bell <bell.jeremy at gmail.com>wrote:
>>>
>>>> Hmm, is there a separate install target that does install them? It's
>>>> easy enough to copy the directory in a build script after make install, but
>>>> that's a little brittle. Better that the build system handle that, I think.
>>>>
>>>>
>>>> On Wed, May 29, 2013 at 11:58 AM, Rodrigo Kumpera <kumpera at gmail.com>wrote:
>>>>
>>>>> Yes, it's not copied because those assemblies are not very useful on
>>>>> the desktop.
>>>>>
>>>>>
>>>>> On Wed, May 29, 2013 at 11:40 AM, Jeremy Bell <bell.jeremy at gmail.com>wrote:
>>>>>
>>>>>> When I build the monodroid assemblies with the configure option
>>>>>> --with-monodroid=yes, the profile is built correctly in the master branch,
>>>>>> but when you make install, the monodroid profile assemblies are not copied
>>>>>> to the install prefix directory with the other profiles. Is this expected
>>>>>> behavior?
>>>>>>
>>>>>> Here is my config options:
>>>>>>
>>>>>> ./autogen.sh --with-glib=embedded --prefix=$INSTALL_PREFIX --with-monodroid=yes
>>>>>>
>>>>>> make && make install
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Mono-devel-list mailing list
>>>>>> Mono-devel-list at lists.ximian.com
>>>>>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20130530/568c05dc/attachment.html>