From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] LIB_SYMLINK in top-level Makefile
Date: Wed, 23 Dec 2015 20:09:49 +0100 [thread overview]
Message-ID: <20151223190949.GG3426@free.fr> (raw)
In-Reply-To: <CAKbGBLgHuT-cQh4SW_NMBJ9iSpf_gan_3cjRn3Kc4pT+bEtTZw@mail.gmail.com>
Steven, All,
On 2015-12-23 00:44 -0800, Steven Noonan spake thusly:
> Are the LIB_SYMLINK definitions in the top-level Makefile defined at
> the time they're used in package/skeleton/skeleton.mk? It looks like
> those lines didn't get moved along with the rest of the bits from the
> $(STAGING_DIR) target.
As Thomas already replied, they are.
And even if they are defined after they are used', that is not a
problem. In Makefiles, the expansion of variables is not done at
the time of parsing, but at the time the rules are executed.
For example, test this simple Makefile:
$ cat Makefile
all:
@echo FOO="'$(FOO)'"
FOO=1234
$ make
FOO='1234'
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-12-23 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-23 8:44 [Buildroot] LIB_SYMLINK in top-level Makefile Steven Noonan
2015-12-23 10:10 ` Thomas De Schampheleire
2015-12-23 19:09 ` Yann E. MORIN [this message]
2015-12-23 21:32 ` Steven Noonan
2015-12-23 21:41 ` Yann E. MORIN
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=20151223190949.GG3426@free.fr \
--to=yann.morin.1998@free.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox