From: "Burton, Ross" <ross.burton@intel.com>
To: Ugesh Reddy <kumar.ugesh003@yahoo.com>
Cc: "bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: Re: .bb script file for auto tools
Date: Wed, 9 May 2018 12:44:25 +0100 [thread overview]
Message-ID: <CAJTo0LZGEBwiZr7csd3vxYaThN7-fTjexeRfkT+1ksX-AerbvA@mail.gmail.com> (raw)
In-Reply-To: <1184471455.1381374.1525832300014@mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
The easy way is to just use devtool to create the recipe for you. The
important bit is just "inherit autotools" to handle
autoreconf/configure/make/make install for you.
Ross
On 9 May 2018 at 03:18, Ugesh Reddy via bitbake-devel <
bitbake-devel@lists.openembedded.org> wrote:
> Hello All,
>
> I am new to bitbake and having the basic understanding on bitbake. My
> project uses auto tools and it has Makefile.am and configure.ac when it
> runs with autogen.sh it could able to generate Makefile and configure with
> generated files the bin program is generated. I would like to do the same
> with bitbake. The below are the structure
>
> As mentioned in the below link
> https://github.com/DynamicDevices/bbexample
>
> When it executed like below it works fine
> $ cd bbexample
> $ ./autogen.sh
> $ ./configure
> $ make
>
> How can i write the .bb file for the same ?
>
> Regards,
> Ugesh
>
>
>
>
>
>
>
>
> --
> _______________________________________________
> bitbake-devel mailing list
> bitbake-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/bitbake-devel
>
>
[-- Attachment #2: Type: text/html, Size: 3306 bytes --]
next prev parent reply other threads:[~2018-05-09 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1184471455.1381374.1525832300014.ref@mail.yahoo.com>
2018-05-09 2:18 ` .bb script file for auto tools Ugesh Reddy
2018-05-09 11:44 ` Burton, Ross [this message]
2018-05-09 15:59 ` Ugesh Reddy
2018-05-10 0:29 ` Andre McCurdy
2018-05-10 6:53 ` Ugesh Reddy
2018-05-10 10:58 ` Matt Hoosier
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=CAJTo0LZGEBwiZr7csd3vxYaThN7-fTjexeRfkT+1ksX-AerbvA@mail.gmail.com \
--to=ross.burton@intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=kumar.ugesh003@yahoo.com \
/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.