From: Mario Domenech Goulart <mario@ossystems.com.br>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Gary Thomas <gary@mlbassoc.com>
Subject: Re: How to re-run configure after changing Makefile.am
Date: Thu, 13 Mar 2014 14:59:07 +0000 [thread overview]
Message-ID: <87fvmmi1qc.fsf@parenteses.org> (raw)
In-Reply-To: <CAP9ODKrSoShhnyYQMhCBwhWt=kQ7T04Qn0DqVA-YOi=6ctzUBw@mail.gmail.com> (Otavio Salvador's message of "Thu, 13 Mar 2014 11:57:04 -0300")
On Thu, 13 Mar 2014 11:57:04 -0300 Otavio Salvador <otavio@ossystems.com.br> wrote:
> On Thu, Mar 13, 2014 at 11:54 AM, Gary Thomas <gary@mlbassoc.com> wrote:
>> On 2014-03-13 08:48, Otavio Salvador wrote:
>>> On Wed, Mar 12, 2014 at 11:54 PM, Norman Cheung <brjerome.1@gmail.com> wrote:
>>>> Hello,
>>>>
>>>> I wonder what bitbake commmand is used in Yocto to re-run configure?
>>>>
>>>> I have modified the gstreamer core elements Makefile.am, and updated a
>>>> source file.
>>>>
>>>> bitbake -f -c compile gstreamer doesn't seem to re-configure the Makefile
>>>
>>> bitbake -f -c configure gstreamer
>>
>> Probably better to do
>> bitbake gstreamer -C configure
>> which will restart the whole recipe at the configure step.
>>
>> If you use -c (lower case), you only get the configure step and
>> you then have to force a compile to complete the build.
>
> I didn't know this 'trick'; nice one :-) Mario, this is useful for
> your current debug ;-)
Indeed! Thanks for the tip, Gary.
Best wishes.
Mario
--
http://www.ossystems.com.br
prev parent reply other threads:[~2014-03-13 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 2:54 How to re-run configure after changing Makefile.am Norman Cheung
2014-03-13 14:48 ` Otavio Salvador
2014-03-13 14:54 ` Gary Thomas
2014-03-13 14:57 ` Otavio Salvador
2014-03-13 14:59 ` Mario Domenech Goulart [this message]
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=87fvmmi1qc.fsf@parenteses.org \
--to=mario@ossystems.com.br \
--cc=gary@mlbassoc.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.