[Chicken-janitors] #1468: Static extensions with inter-component dependencies must be installed twice

[Chicken Trac]

#1468: Static extensions with inter-component dependencies must be installed 
twice
------------------------+----------------------------
 Reporter:  evhan       |                 Owner:
     Type:  defect      |                Status:  new
 Priority:  major       |             Milestone:  5.0
Component:  core tools  |               Version:  5.0
 Keywords:              |  Estimated difficulty:
------------------------+----------------------------
 If an egg has one file `a.scm` that depends on another `b.scm`, the first
 time the egg is built the generated link file `a.link` won't include
 `b.o`. Subsequent builds work fine, once the extension has been installed.

 There are two reasons for this:

 1. The build directory isn't considered when looking for static
 extensions.
 2. Even if it were, object files in the build directory are created with
 names that include "static" (e.g. `b.static.o`), which aren't found when
 looking for static objects (e.g. `b.o`). They ''are'' installed without
 the "static" bit, so once they're in the repository everything works OK.

 I think the fix for item 1 is to make `find-static-extension` consider
 `##sys#setup-mode` just like `find-dynamic-extension` already does, and to
 prepend the current directory to the search path when it's enabled. (It
 should also append it when disabled, for consistency with its dynamic
 counterpart.)

 I'm less sure what to do about item 2.

--
Ticket URL: <https://bugs.call-cc.org/ticket/1468>
CHICKEN Scheme <https://www.call-cc.org/>
CHICKEN Scheme is a compiler for the Scheme programming language.