From: Sapna Todwal <sapna@neoaccel.com>
To: linux-kernel@vger.kernel.org
Subject: prob with 2.6 Makefile
Date: Mon, 14 Nov 2005 11:34:02 +0530 [thread overview]
Message-ID: <1131948242.3168.19.camel@localhost.localdomain> (raw)
I have a few doubs with the 2.6 makefile
Suppose I have the following dir structure:
maindir
|
-------
| |
subdir1 subdir2
Now both of this subdirs have many .c files which are to be compiled and
linked together to make final1.o & final2.o files in the subdirs
subdir1 & subdir2 respectively.
Now i want to link this two files subdir1/final1.o & subdir2/final2.o ,
in the maindir to make file say final.o file in maindir .
So the Makefile in maindir looks like:
obj-m := subdir1/ subdir2/
This will traverse the subdir1 & subdir2 and call their makefiles.
But how do i make final.o from subdir1/final1.o and subdir2/final2.o
Kindly help me with the solution.
Thanks in advance,
Regards,
Sapna
next reply other threads:[~2005-11-14 6:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 6:04 Sapna Todwal [this message]
2005-11-14 20:27 ` 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=1131948242.3168.19.camel@localhost.localdomain \
--to=sapna@neoaccel.com \
--cc=linux-kernel@vger.kernel.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®