On Tue, Jun 22, 2010 at 11:32 PM, Naveen Maheshwari <naveenmah@gmail.com> wrote:
Yeah David is right.If you link your application with open source libraries you have to open your code.
This is not necessary if you're talking about "open source libraries" in general. They are plenty of open-source license that allow you
to keep your own source code closed: BSD, MIT and even the LGPL (under certain conditions). The GPL is more restrictive in the
way it requires you to distribute your _own_ sources if they link to anything GPL.
That's why what I am trying to do is the code that uses open source I make it as separate module and run that as remote service.
Now since this service is running as a separate process so I am oblized to open only source code for this service...
So the basic idea is
A my app has some data and it needs to process this data... When it needs to process this data it runs a remote service B. This service process the data and returns back to A.
B is the service that is using open source code and is running as a remote service. which is different process than app A.
Source code for B will be made open source.
So as far as I know there should not be any legal issues and all can go as same .apk.
Thanks--On Wed, Jun 23, 2010 at 3:14 PM, Chi Kit Leung <michaelchikit@gmail.com> wrote:
I think david is very right about that.On Wed, Jun 23, 2010 at 4:04 PM, David Turner <digit@android.com> wrote:
On Tue, Jun 22, 2010 at 9:33 PM, HaMMeReD <adamhammer2@gmail.com> wrote:If you can use it without modifying the source then just do it, and
provide credit to the library creator clearly in your app.
this is wrong on many levels. As soon as you *distribute* the binaries (e.g. through Market),you must provide the sources of _all_ your program if you link against the GPLed sources.This is true of GPLv2 or GPLv3.The LGPL is different, but conditions are very specific, and probably corresponds more towhat you describe. However, this does not apply to the GPLv3.Please read the GPL Faq, it contains useful information.If you need to modify the source, then you need to be able to provide
the modifications. If you need to integrate it with your app deeply so
that you can't use the modified version without your app, then you
need to open source the entire thing.
IANAL but using a open source library in a closed source project
without any modification should not provide any serious legal issues
as long as everyone is properly credited and there is no stipulations
in the license or on the creators website.
I wouldn't recommend doing complex workarounds, because it just
increases the amount of changes and dependencies between your app and
the open source app, and shows that you were trying to circumvent
things. Just do your best to not change it, and check the creators
site to see if they sell alternate licenses that might server your
needs better, if you do need to modify the source in certain ways.
Adam Hammer
On Jun 22, 12:10 am, Naveen <naveen...@gmail.com> wrote:
> Hi!
> I need to use some open source code with GPL3.
>
> As usual I don't want to open source code for full application.
>
> Now what I understand is if I make two separate process one with my
> main application code and other as a service or something with Open
> source library then in that case I have to open source code only for
> the other one.
>
> Now the question is what is the best way to do so in Android.
>
> Suppose
> My Main App is A
> Open Source code is B
>
> So A will give some data to B. B will process this and sends data back
> to A. B may not need to have any UI.
>
> 1. Is it possible to install 2 seperate applications / processes from
> one APK?
> 2. What is the best way ?Should B be a service? How will be the
> communication between A and B ?
> 3. Is it possible to run/call B from A?
>
> Pls. advice
>
> Thanks
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=enYou received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
No comments:
Post a Comment