This is a restriction by ownselves. Distributions exist with this
violating.  It is not nice to bring these distributions in a bad light.
All have the aim to make openocd popular.
The code exists and works fine. Nobody troubled  until somebody found
this problem.
It is necessary to make an additional exception on the licence for
linking drivers. This is the best solution for this problem.
Otherswise It is like a broken arm. The aim  is to make openocd to good
Jtag-Tool. I can see it work good for long time.

I have the same attitude like Freddie. Now it is a bug in the licence,
this is to correct!

Rene Doss


Freddie Chopin schrieb:
> (sorry for sending to David only in the first try, this "Reply-To"
> policy is really strange, and the "reasons" just don't convince me...)
>
> In my country such imaginary problems are often described as "a shot in
> one's own foot".
>
> If OpenOCD aims to be uber-GPLv3-h4x0r-friendly that's perfectly fine,
> but I just can't imagine majority of vista64 users building their own
> copy of OpenOCD. That's not just as easy as you think (MinGW + MSYS +
> like a dozen of different addons + some strange libraries)... These ppl
> will probably use some other tool which has a GUI (H-JTAG, CrossWorks
> demo, RIDE demo, Keil demo or IAR demo [whichever works with one's 
> JTAG], manufacturer's bootloaders) just for loading the flash (or 
> whatever memory they have). Or someone will just do a version with 
> FTDI's libraries and distribute it anyway.
>
> Sometimes I think that open-source is killing itself... All those rules,
> and I once thought that open-source is about freedom (here I recall 
> recent "spaces vs. tabs" - jeez...)
>
> BTW - there is also a sentence which goes like "stupid regulations
> should be violated" or something like that.
>
> 4\/3!!
>
> _______________________________________________
> Openocd-development mailing list
> Openocd-development@lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/openocd-development
>
>   

_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to