Re: Hard coded paths in csc and relocatable chicken

[Mario Domenech Goulart]

Hi Matt,

On Thu, 20 May 2021 15:04:16 -0700 Matt Welland <mattrwelland@gmail.com> wrote:

> As mentioned in the coding jam I put together a chicken bundle including the 
> iup egg ready to go outside the box. It turns out that my assertion that
> it worked was wrong. I tested by running csi and was able to load iup and 
> create a button and I assumed that if this worked then so would compilation
> with csc. Not so. While a little script hackery could swizzle the full paths 
> in the .info files for eggs I don't think there is any way to change the
> paths in compiled binaries such as csc. 
>
> I really would like to be able to make a relocatable build system to enable 
> us to use chicken in our ever more constrained compute environment. 
>
> The directories are all pointing to the original install directory. E.g. 
>> strings csc | less
> ...
> _edata
> __bss_start
> _end
> /home/matt/buildall/ck5.2/lib
> GLIBC_2.3
> GLIBC_2.2.5
>
> Any suggestions or ideas on how to work around this?

Would static linking be an acceptable solution in this case?

All the best.
Mario
-- 
http://parenteses.org/mario