chicken-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-hackers] [PATCH 3/3] Fix repository searching for "-link" f


From: felix . winkelmann
Subject: Re: [Chicken-hackers] [PATCH 3/3] Fix repository searching for "-link" flag and associated tests
Date: Mon, 26 Jun 2017 13:44:32 +0200

> On 2017-06-20 13:11, address@hidden wrote:
> >You seem to drop the reference to "destination-repository". Are you sure 
> >this is
> >right in the face of cross-compilation?
>
> I think so. Or rather, this patch makes "-link" behave like "normal"
> compilation in that it respects CHICKEN_REPOSITORY_PATH and the
> "repository-path" parameter, which is what we want, I think. Previously,
> it would ignore those values and go straight to the target repo, so
> something/lib/chicken/9, since the "destination-repository" helper
> doesn't seem to consider C_R_P at all. I might be missing something,
> though. How is C_R_P intended to behave when cross-compiling?

Indendent of C_R_P, "csc" must handle locating extensions in a cross
compilation setting. Redirecting to "eval" wouldn't work, since the latter
doesn't know anything about cross-compilation, it (mostly) is concerned with
locating things at runtime, where cross-compilation isn't an issue anymore.
When doing cross-compillation, C_R_P is probably not useful, since a cross
chicken already cleanly seperates the different repositories for host and
target. So I'd consider C_R_P of secondary importance in such a situation.
We can change the code in csc to respect the variable, but mostly it is 
important
to handle the target case, which your "find-static-extension" in eval.scm
will not do.


felix




reply via email to

[Prev in Thread] Current Thread [Next in Thread]