mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: anil dahiya <ak_ait@yahoo.com>
To: linux-kernel@vger.kernel.org, kernelnewbies@nl.linux.org,
	sam@ravnborg.org
Subject: makefile for 2.6 kernel
Date: Tue, 10 Jan 2006 09:44:19 -0800 (PST)	[thread overview]
Message-ID: <20060110174419.56611.qmail@web60212.mail.yahoo.com> (raw)
In-Reply-To: <20060104182356.14925.qmail@web60217.mail.yahoo.com>

Hi Sam
Thanks fop your help ..but my problem is not solved it
...i putting my real problem here below.

1>my fist need is to make  module1.ko made using
a1/a1.c , a1/a11.c & a2/a2.c a2/a22.c and all .c file
use /home/include/a.h 

 
2>Now my 2nd need is to make module2.ko using
module1.ko and b/b1.c & b/b11.c (these both .c files
use /home/include/a.h and /home/module2/include/b.h) 

In short my directory  structure is as:
  
/home/------
              |_ include _
              |           |
              |           a.h 
              | 
              |___module1_
              |           |__ a1 ____________
              |           |          |       |
              |           |         a1.c   a11.c
              |           |
                          |__ a2 ___________
              |           |           |     |
              |           |         a2.c   a22.c
              |
              |___ moudule2_
              |             |             
              |             |__include _
              |             |           |
              |             |           b.h 
              |             |___b1________
              |                     |     |
              |                   b1.c   b11.c
         
                                    
Looking forward for ur reply 
thanks in advance
 ---- Anil 


--- anil dahiya <ak_ait@yahoo.com> wrote:

> hello 
> I want to make kernel module dummy.ko using multiple
> .c and .h files. In short i am telling .c and .h
> files
> with directory structure
> 
> 1> dummy.ko should made be using module1.ko and
> module2.o (i.e 
>    module2.o uses module1.ko to make dummy.ko)
> 
> 2> module1.ko made using a1/a1.c & a2/a2.c and  both
> .c file   
>    use /home/include/a.h 
> 3> module2.o should made using b/b1.c which use   
>    use /home/module2/include/b.h 
> 
> Suggest me tht should make i make module2.o or
> module2.ko and then combine it with module1.o to
> make
> dummy.ko 
> 
> 
> /home/------
>              |_ include _
>              |           |
>              |           a.h 
>              | 
>              |___module1_
>              |           |__ a1 ____
>              |           |          | 
>              |           |         a1.c 
>              |           |
>                          |__ a2 ____
>              |           |           | 
>              |           |         a2.c 
>              |
>              |___ moudule2_
>              |             |             
>              |             |__include _
>              |             |           |
>              |             |           b.h 
>              |             |___b1__
>              |                     | 
>              |                   b1.c 
>         
>                                    
> Looking forward for ur reply 
> thanks in advance
> ---- Anil 
> 
> 
> 		
> __________________________________________ 
> Yahoo! DSL – Something to write home about. 
> Just $16.99/mo. or less. 
> dsl.yahoo.com 
> 
> 
> --
> Kernelnewbies: Help each other learn about the Linux
> kernel.
> Archive:      
> http://mail.nl.linux.org/kernelnewbies/
> FAQ:           http://kernelnewbies.org/faq/
> 
> 



		
__________________________________________ 
Yahoo! DSL – Something to write home about. 
Just $16.99/mo. or less. 
dsl.yahoo.com 


  parent reply	other threads:[~2006-01-10 17:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04 18:23 anil dahiya
2006-01-04 18:55 ` Sam Ravnborg
2006-01-06  7:20   ` Nauman Tahir
2006-01-06 15:55     ` Sam Ravnborg
2006-01-10 17:44 ` anil dahiya [this message]
2006-01-10 19:07   ` Sam Ravnborg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060110174419.56611.qmail@web60212.mail.yahoo.com \
    --to=ak_ait@yahoo.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®