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, 03 Oct 2013 00:25:35 +0200 [thread overview]
Message-ID: <524C9D5F.5090002@gmail.com> (raw)
In-Reply-To: <CAA0a8nWaUad-4-KRRr4i3ugfqLGkaQO3ErfAfPQGqmubAnN8bA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2909 bytes --]
On 03.10.2013 00:03, Mat Troi wrote:
> Hi Vijayakumar Venganti,
>
> Sorry I overlooked your email last week :-( I had the same question
> before and below is how I got it to work. You need to regenerate
> Makefile.in file in your grub-core folder. First, you need to modify
> Makefile.core.am <http://Makefile.core.am> to include your new module;
> to see how to do this, search in Makefile.core.am
> <http://Makefile.core.am> for "hello" module. You also need to modify
> Makefile.core.def; again to see how to do this, search in
> Makefile.core.def for "hello" module. On another machine (will be
> referred to as machine B), you need to install m4-1.4.6 at
> ftp://ftp.gnu.org/gnu/m4/, install autoconf-2.64, install
> automake-1.11.2. Make sure your $PATH points to the stuff you just
> installed. Then in your grub2 directory there should be a file named
> autogen.sh. Copy autogen.sh and tries to run it on machine B. There
> will be warnings/errors for missing files, depending on the
> warnings/errors copy files from grub2 folder over to machine B. After
> autogen.sh runs successfully, copy Makefile.in back to your work
> environment and from there run your normal build.
>
"Why do easy if you can do complicated?"
Just change Makefile.core.def and rerun ./autogen.sh. That is.
> I hope this helps,
> Mat Troi
>
>
>
> On Thu, Sep 26, 2013 at 12:35 AM, Vladimir 'φ-coder/phcoder' Serbinenko
> <phcoder@gmail.com <mailto:phcoder@gmail.com>> wrote:
>
> On 26.09.2013 09 <tel:26.09.2013%2009>: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 <mailto:Grub-devel@gnu.org>
> > https://lists.gnu.org/mailman/listinfo/grub-devel
> >
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org <mailto:Grub-devel@gnu.org>
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
>
>
>
> _______________________________________________
> 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-10-02 22:25 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
2013-10-02 22:03 ` Mat Troi
2013-10-02 22:25 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
-- 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=524C9D5F.5090002@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).