| Re: [incubation] wrap binaries into a plugin |
Mike, > Operating systems are typically treated as "exempt pre-reqs" because they are already installed on the target machine. I/O access libraries have to be treated on a case-by-case basis, and it makes a great deal of difference if you are distributing the library with your code, or simply calling a library that is already installed on the target machine. Thanks for the clarification. How would we treat operating systems as often sued on smaller IoT devices where the operating system is a library linked to the application (e.g., eCos, freeRTOS). Would these be treated like any library? I'll read through the docs. Thanks for the pointers. Alois > See http://www.eclipse.org/org/documents/ for the following documents:http://www.eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf[http://www.eclipse.org/org/documents/Eclipse_Policy_and_Procedure_for_3rd_Party_Dependencies_Final.pdf] > http://www.eclipse.org/org/documents/GPL_CE_Policy.php > http://www.eclipse.org/org/documents/LGPL_API_Policy.pdfHope that helps. -- Mike Milinkovich mike.milinkovich@xxxxxxxxxxx[mike.milinkovich@xxxxxxxxxxx] +1.613.220.3223 _______________________________________________ incubation mailing list incubation@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/incubation[https://dev.eclipse.org/mailman/listinfo/incubation]