All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] prevent recursion in %_defconfig rules
Date: Wed, 22 Jan 2014 15:16:12 +0100 (CET)	[thread overview]
Message-ID: <686484103.4612359.1390400172918.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <20140121183820.GB3455@free.fr>


> > 
> > * Having a buildroot/ subdirectory at the root of the project
> > * Having a Makefile in the root of the project that correctly
> >   allows to build the project
> > * Having BR2_EXTERNAL be the root of the project (and as much
> >   as possible, all config files in the root of the project)
> > * Having an output/ subdirectory in the root of the project
> >   with all build files
> > * Having everything relocatable (since I want to save it to git, I
> >   can't have absolute paths)
> > 
> > That is currently not possible and maybe it's a bad idea, but this
> > layout seems to make sense to me and the relative path requirement
> > makes sense too, since it's needed for other people to use my
> > project
> 
> But your Makefile already does not use relative paths:
>     MAKEARGS := -C $(CURDIR)/buildroot
>     MAKEARGS += O=$(CURDIR)/output
>     MAKEARGS += BR2_EXTERNAL=$(CURDIR)
> 
> which is IMHO the way to go.
> 

ok, good. i'll stay with that approch (that doesn't use the br
generated makefile nor the .br-external file) for my project


> [--SNIP--]
> > Though I agree that it would be more sensible to have 0= and
> > BR2_EXTERNAL be relative to cwd...
> 
> But since we may call 'make -C /bla/bla', CWD is lost long before we
> even get to the point our Makefile is parsed.
> 

indeed. so no CWD, then. makes sense

<snip>


> 
> Well, just look at your repository! ;-)
> Unles I missed something obvious, that is... :-)
> 

yes, indeed. I didn't realize that it was working for me :)

BR2_EXTERNAL does indeed do what I want now. I'll move foward
with the next step in my proof of concept project: relocating
the various .config files

but that's a story for another day :)


> Regards,
> Yann E. MORIN.
> 
> --
> .-----------------.--------------------.------------------.--------------------.
> |  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics'
> |  conspiracy: |
> | +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___
> |               |
> | +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/
> |  There is no  |
> | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v
> |   conspiracy.  |
> '------------------------------^-------^------------------^--------------------'
> 

      reply	other threads:[~2014-01-22 14:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 16:22 [Buildroot] [PATCH] prevent recursion in %_defconfig rules Jérémy Rosen
2014-01-13  8:52 ` Jeremy Rosen
2014-01-13  8:59   ` Peter Korsgaard
2014-01-17 17:52 ` Yann E. MORIN
2014-01-17 18:09   ` Yann E. MORIN
2014-01-17 19:54     ` Yann E. MORIN
2014-01-20  8:03       ` Jeremy Rosen
2014-01-20  8:13         ` Jeremy Rosen
2014-01-20 18:31           ` Yann E. MORIN
2014-01-20 22:58           ` Romain Naour
2014-01-20 23:58             ` Yann E. MORIN
2014-01-21  8:44               ` Jeremy Rosen
2014-01-21 18:38                 ` Yann E. MORIN
2014-01-22 14:16                   ` Jeremy Rosen [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=686484103.4612359.1390400172918.JavaMail.root@openwide.fr \
    --to=jeremy.rosen@openwide.fr \
    --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 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.