Hello Simon,
There are a few projects that do this; however none of them uses
automake to build the makefiles for the kernel objects; rather, they
have a Makefile.in that is not autogenerated, accepts the
substitutions for the install paths etc. and calls the kernel Makefile
with appropriate
Vladimir Vassilev [EMAIL PROTECTED] writes:
Can you point me to similar open source projects. I am mostly curious
what solution they chose for distributing the driver binaries after they
have been built. In the case of userspace programs and libraries the
autotools primitives (PROGRAMS,
Hello Russ,
Thanks for the input. Do you think that if the application startup
scripts take the whole responsibility of insmod-ing the drivers it would
be possible to use a different place than
/lib/modules/version-of-kernel/extra ? Then I hope doing a proper
depmod would not be necessary. I
Vladimir Vassilev [EMAIL PROTECTED] writes:
Thanks for the input. Do you think that if the application startup
scripts take the whole responsibility of insmod-ing the drivers it would
be possible to use a different place than
/lib/modules/version-of-kernel/extra ? Then I hope doing a proper
Hi,
Vladimir Vassilev schrieb:
If there are projects which address the same issue, please send some
pointers.
There are a few projects that do this; however none of them uses
automake to build the makefiles for the kernel objects; rather, they
have a Makefile.in that is not autogenerated,
Hello,
I am working on a complex project which involves both userspace
applications, libraries and Linux kernel drivers. What is the
recommended approach to build and distribute Linux drivers as part of a
GNU automake distribution. We hope there is an elegant way to generate
the Makefile
