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?
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 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 ma
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 wrote:
> Yes, it's not c
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.Androi
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 wo
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 a
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 li
The RabbitMQ driver has no non-free bits itself, only it's build system
that uses one to generate apache licensed files.
On Thu, May 30, 2013 at 10:18 AM, Jeremy Bell wrote:
> Thanks Rodrigo.
>
> If you would, could you clarify on the issue of the AMQP driver? Do you
> mean the RabbitMQ library
