Impact on modifying the current planning code (was Re: Plans for ASDF 3.3)

[Robert Goldman]

On 5/4/17 May 4 -2:05 PM, Faré wrote:
> On Thu, May 4, 2017 at 7:56 AM, Mark Evenson <evenson at panix.com> wrote:
>>     Still, what has been
>>     implemented (and what I am proposing), seems to violate Faré's
>>     description of ASDF as a build system that should only deal with
>>     Common Lisp artifacts.
>>
> I don't remember writing that ASDF *should* only deal with CL
> artifacts. Historically, that's what it always did; but "CL artifacts"
> has included "C code linked into the CL runtime" for a *long* time.
> And this year, this includes static linking as well as dynamic
> linking. Moreover, ASDF has the potential of doing more than that.
> Indeed, cl-unicode drives processing of data files using ASDF. QRes
> also used to massage its configuration files or to generate CL code
> from ASDF.
> 
> ASDF *should* do whatever you need to build your CL application. Now
> to actually make that happens can be easy or hard, depending on what
> that is.

Seconded.  We routinely use ASDF to load systems in other programming
languages that are built with MAKE, but that our CL code interacts with....