On Friday, 6 January 2023 8:50:30 PM AEDT Leopold Bloom wrote: > Hello, > > I have question about potential using the GeoTools in the commercial app. > > > > We are planning to develop a new app and we would like to use GeoTools > library in it. Because LGPL licence terms are not easy to read I´d like to > ask you directly. > > > > > Our software in the executable form would use GeoTools library by the static > linking. I read that static linking can be problematic towards the > commercial apps. Can we distribute the executable form of the software by > Google Play and AppStore without revealing source code of our whole > software? Or which requirements we have to fulfill to do so?
I am not your lawyer, nor do I speak on behalf of the project. However I think the terms of the LGPL are pretty clear in this situation. In particular, assuming you aren't making any changes to GeoTools, then the requirement for static linking is that you allow relinking (see Section 6(a) of the LGPLv2.1). An executable is not sufficient. There are also notice requirements about use of the Library (see Section 6). If you are making changes to GeoTools (what the license calls "works based on the library"), then you need to release those under the LGPL (or compatible license). One way to think about this is "how am I going to allow users to modify and upgrade the GeoTools parts of my program"? If you can explain that, then I think you are well on the way to planning your license compliance. There is a good explanation at https://copyleft.org/ if you need more background, but fundamentally you should seek professional legal advice if you are unsure. HTH. Brad _______________________________________________ GeoTools-GT2-Users mailing list GeoTools-GT2-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
