From mboxrd@z Thu Jan  1 00:00:00 1970
From: Yann E. MORIN <yann.morin.1998@free.fr>
Date: Wed, 23 Dec 2015 20:09:49 +0100
Subject: [Buildroot] LIB_SYMLINK in top-level Makefile
In-Reply-To: <CAKbGBLgHuT-cQh4SW_NMBJ9iSpf_gan_3cjRn3Kc4pT+bEtTZw@mail.gmail.com>
References: <CAKbGBLgHuT-cQh4SW_NMBJ9iSpf_gan_3cjRn3Kc4pT+bEtTZw@mail.gmail.com>
Message-ID: <20151223190949.GG3426@free.fr>
List-Id: <buildroot.busybox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: buildroot@busybox.net

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.  |
'------------------------------^-------^------------------^--------------------'