Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: aurelien coulaud <aurelien.coulaud@thalesgroup.com>
To: buildroot@busybox.net
Subject: [Buildroot] migrating manual makefile to autotools-based packages
Date: Wed, 6 Apr 2016 17:18:05 +0000 (UTC)	[thread overview]
Message-ID: <loom.20160406T191601-706@post.gmane.org> (raw)
In-Reply-To: loom.20160406T145801-819@post.gmane.org

aurelien coulaud <aurelien.coulaud@...> writes:

> 
> Hello,
> 
> I am using an old buildroot 2011 with external packages using manual
makefiles.
> 
> Now I am migrating to buildroot 2016.02 and this doc
> (http://free-electrons.com/~thomas/buildroot/manual/html/ch11.html) explains
> that manual makefile are now obsolete.
> 
> and the official doc of buildroot does not mention manual makefile :
> https://buildroot.org/downloads/manual/manual.html
> 
> manual makefile is not supported on 2016.02, I am right ?
> Is there a way to continue to use manual makefile?
> 
> Otherwise is there a tool to migrate easily manual makefile to
autotools-based ?
> 
> Thank you for your answer.
> Best regards,
> 
> AC
> 

hello I found the solution into this slides (page 272):
http://free-electrons.com/doc/training/buildroot/buildroot-slides.pdf

"Note: as of Buildroot 2015.05,
TARGETS
has been renamed to
PACKAGES"

So now my old Package with manual makefile compiles.

Bye,

  reply	other threads:[~2016-04-06 17:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06 13:14 [Buildroot] migrating manual makefile to autotools-based packages aurelien coulaud
2016-04-06 17:18 ` aurelien coulaud [this message]
2016-04-08  2:31   ` Thomas Petazzoni
2016-04-08  8:49     ` aurelien coulaud
2016-04-28  8:24       ` Peter Korsgaard

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=loom.20160406T191601-706@post.gmane.org \
    --to=aurelien.coulaud@thalesgroup.com \
    --cc=buildroot@busybox.net \
    /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