Re: [Ltib] single kernel module

[Stuart Hughes]

Hi Henry,

Yes, once you want to publish a package you should put all the related
files into a tarball.  This should at least have the files COPYING (for
the license), README and a Makefile.

If you have any other files related to this one that make up a bigger
package it's probably a good idea to put them into the same package.

If it really is just a single file as you have said already you could
add it as a patch to the kernel source that you are patching.

For an example of building kernel modules outside of the kernel sources,
see dist/lfs-5.1/helloworld/hello_mod.spec.  However if you use this
technique, you'll need to select that LTIB keeps the build kernel source
tree unpackaged.  In many ways the easiest thing for a single file would
be to add it as a patch to the kernel sources.

BTW: I'm still working on fontconfig (done), pango, DirectFB etc

Regards, Stuart

On Sun, 2007-11-18 at 12:43 -0800, hong zhang wrote:
> Stuart,
> 
> Does user have to create tar file as package to cross
> compile under ltib?
> What I mean is that I have a single file,
> skeleton.fb.c contains kernel module (I can put it
> inside kernel tree
> to cross compile using ltib). But if I want to put it
> outside kernel tree, what should I do?
> 
> ----henry
> 
> 
>       
> ____________________________________________________________________________________
> Get easy, one-click access to your favorites. 
> Make Yahoo! your homepage.
> http://www.yahoo.com/r/hs 
> 
> 
> _______________________________________________
> LTIB home page: http://bitshrine.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib