From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: How to develop and integrate brand new module into GRUB2?
Date: Thu, 26 Sep 2013 09:35:56 +0200 [thread overview]
Message-ID: <5243E3DC.8090507@gmail.com> (raw)
In-Reply-To: <CACixeCgZ2Ke_xZkyrUsqSxxWA2L6MEAdnhiwihzcfk8p6n0SSw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
On 26.09.2013 09:28, Vijayakumar Venganti wrote:
> Dear Friends,
>
> I need to develop a new module and integrate into GRUB2. I already have
> the code written, my question is how to integrate the code into the
> existing GRUB2 build system so that the code gets built when make is
> entered at GRUB2's top level directory?
>
> My module is located at <Working
> directory>/grub2/grub-core*/testmodule/Makefile*
> So, I want to run the Makefile inside testmodule and integrate that
> module into GRUB2.
> Any help is greatly appreciated..
>
Do not create your own Makefile. Look at grub-conf/Makefile.core.def
>
> Thanks,
> Vijay
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
next prev parent reply other threads:[~2013-09-26 7:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 7:28 How to develop and integrate brand new module into GRUB2? Vijayakumar Venganti
2013-09-26 7:35 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-10-02 22:03 ` Mat Troi
2013-10-02 22:25 ` Vladimir 'φ-coder/phcoder' Serbinenko
-- strict thread matches above, loose matches on Subject: below --
2013-08-28 0:21 Mat Troi
2013-08-31 11:19 ` Andrey Borzenkov
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=5243E3DC.8090507@gmail.com \
--to=phcoder@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.