On 03/10/2013 07:15 PM, Matt Shaver wrote:
On Sun, 10 Mar 2013 08:01:24 -0600
EBo e...@sandien.com wrote:
Looks like we need to email EFF or GNU for a determination. Matt
what you say is that 0MQ allows linking to anything, but GPLv2
requires that anything linked must then convey GPLv2,
On 03/10/2013 08:31 PM, John Kasunich wrote:
On Sun, Mar 10, 2013, at 09:25 PM, EBo wrote:
Frankly, I think halscope should either be changed back to to LGPL or
simply pulled.
Halscope is a stand-alone application. How does LGPL make sense
for it?
By the way, 'LGPL' no longer means
What is the best way to compile a new HAL driver without having to rebuild
the entire LinuxCNC suite all over??
I am not sure where to even put my source in what makefile so its included
in the build. (I am new to autotools, sorry)
Thanks!
On 11 March 2013 20:09, uMinded Strikes Again iceblu3...@gmail.com wrote:
What is the best way to compile a new HAL driver without having to rebuild
the entire LinuxCNC suite all over??
A driver or a component?
Drivers generally need a full build (but it gets much quicker the
second time, only
I need to write a low level gpio driver for HAL. I am using
src/hal/drivers/hal_gpio.c (from the rasberry pi) as an example.
I made a file called sun5i_gpio.c and did make in the src directory but it
was not picked up. Do I need to add an entry into a makefile or
config.infile for it to be
On 11 March 2013 21:29, uMinded Strikes Again iceblu3...@gmail.com wrote:
I made a file called sun5i_gpio.c and did make in the src directory but it
was not picked up. Do I need to add an entry into a makefile or
config.infile for it to be included?
You need to add it to the makefile (6
Hi,
On Tue, Mar 12, 2013 at 5:29 AM, uMinded Strikes Again iceblu3...@gmail.com
wrote:
I need to write a low level gpio driver for HAL. I am using
src/hal/drivers/hal_gpio.c (from the rasberry pi) as an example.
I made a file called sun5i_gpio.c and did make in the src directory but it
was
