From: Viswesh S <viswesh_vichu@yahoo.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Linking
Date: Fri, 25 Jul 2008 07:33:41 -0700 (PDT) [thread overview]
Message-ID: <694347.9013.qm@web31608.mail.mud.yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2083 bytes --]
Suppose I am adding a new command,so should I create a new file for that command and modify only the command,rmk accordingly?
All the other files get autogenerated by autogen.sh ?
Is this sufficient ?
Viswesh
----- Original Message ----
From: Colin D Bennett <colin@gibibit.com>
To: grub-devel@gnu.org
Sent: Friday, 25 July, 2008 7:31:28 PM
Subject: Re: Linking
On Fri, 25 Jul 2008 03:22:57 -0700 (PDT)
Viswesh S <viswesh_vichu@yahoo.com> wrote:
> The reason for hello to be put in a directory because it is a module
> and not a simple command.Understood myself
Actually, no. Every C source file in the 'commands' directory is
currently a module itself.
I think the reason that 'hello.mod' is separated out is to make it
easier to see that there is only one source file as part of 'hello.mod'.
Regards,
Colin
> ----- Original Message ----
> From: Viswesh S <viswesh_vichu@yahoo.com>
> To: The development of GRUB 2 <grub-devel@gnu.org>
> Sent: Friday, 25 July, 2008 3:44:48 PM
> Subject: Re: Linking
>
>
> Hi,
>
> So if I add a module or add a new command,which are the files which I
> should modify in general and which all gets generated automatically.
> Is this somewhere documented ?
>
> Why is it that hello command is put in a separate directory, while
> lspci is put inside the commands directory.
> Is there a specific reason for this.
>
>
> Viswesh
>
>
>
> ----- Original Message ----
> From: Pavel Roskin <proski@gnu.org>
> To: grub-devel@gnu.org
> Sent: Friday, 25 July, 2008 11:59:21 AM
> Subject: Re: Linking
>
> Quoting Viswesh S <viswesh_vichu@yahoo.com>:
>
> > Hi Pavel,
> > Could you please attach the modified file ?
> > Viswesh
>
> No, I'm just giving you an idea what you may be doing wrong.
>
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
Share files, take polls, and make new friends - all under one roof. Go to http://in.promos.yahoo.com/groups/
[-- Attachment #2: Type: text/html, Size: 3546 bytes --]
next reply other threads:[~2008-07-25 14:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 14:33 Viswesh S [this message]
2008-07-25 15:12 ` Linking Colin D Bennett
-- strict thread matches above, loose matches on Subject: below --
2008-07-25 10:22 Linking Viswesh S
2008-07-25 14:01 ` Linking Colin D Bennett
2008-07-25 10:14 Linking Viswesh S
2008-07-25 6:06 Linking Viswesh S
2008-07-25 6:29 ` Linking Pavel Roskin
2008-07-25 5:17 Linking Viswesh S
2008-07-25 5:35 ` Linking Pavel Roskin
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=694347.9013.qm@web31608.mail.mud.yahoo.com \
--to=viswesh_vichu@yahoo.com \
--cc=grub-devel@gnu.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