Am Donnerstag, 30. Mai 2013 schrieb Eric Keller: > On Thu, May 30, 2013 at 11:34 AM, Michael Haberler <[email protected]> wrote: > > as for EtherCAT - read this first, its a license minefield: > > http://www.xenomai.org/pipermail/xenomai/2013-May/028597.html > > We went through this agonizing process with open source licenses a > while back. Since that was a basic architecture question, that had to > be done. In the case of a hal component that uses some badly licensed > interface, I have always wondered if there was a way to do avoid > tainting linuxcnc by having an external interface that allows tainted > components.
Please forgive me my ignorance, but why would you want to licence EterCAT at all? You would not be able to sell/advertise your product under the name/brand "EterCAT", but that would be all. Or is this a US speciality to get licensing problems when you did not sign a licensing contract that gives you that licensing problems in the first place? Nik ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
