[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] Chicken integration into OpenEmbedded
From: |
Felix |
Subject: |
Re: [Chicken-users] Chicken integration into OpenEmbedded |
Date: |
Wed, 15 Jun 2011 09:28:11 -0400 (EDT) |
>>
>> Yes, applying PROGRAM_PREFIX is probably wrong. But you want to link
>> in "-target" mode with the native libchicken.so, which will be used
>> on the target (that is, the one native to the target system), right?
>
> For OE and as far as I know for most toolchain documents native means
> the binary to run on host. So I am using "-target" to instruct cross
> chicken toolchain to link against target (binary thar will run on
> target) library.
>
Ah, ok, I think I get it, now.
>> I'm not sure I've understood, but if you want the cross-chicken to use
>> native eggs (that run on the build platform, which I call "host", but
>> the terminology is not consistent), then you should install eggs with
>> the "-host" option.
>
> Yes, I want to use native eggs (what you can host).
>
> The problem is that I do have chicken-native and this is used to build
> the binaries to be used by host. So the eggs end being installed into
> /var/lib/chicken/6/ but has the binary format to be run on host (in my
> case amd64).
>
> I therefore cannot build them with the cross chicken but want it to be
> able to load the native ones.
Ok. I think, I got that too. Sorry, I'm easily confused by these
cross-development issues and constantly mix up host and target.
There might be a misunderstanding here: the "cross-chicken" _is_ a
native chicken, but invokes cross-build-tools and links with a
target-specific library. I assume you followed the method given in the
manual (http://wiki.call-cc.org/man/4/Cross%20development). The
cross-chicken can both install and build code for the host ("native")
or target system, just pass either "-host" ("chicken-install" + "csc")
or "-target" ("chicken-install"). Target-specific installation should
probably use "-prefix" to install into the appropriate location that
holds the target-specific binaries.
So, you shouldn't need to have a separate "chicken-native"
installation. Alternatively you can configure it during build-time
("EGGDIR=...") to share the egg-repository with the (native parts of
the) cross-chicken, but this may be a bit of a hack.
I hope this is in some way helpful. I'm afraid I don't have enough
experience with OE to give a more competent answer.
cheers,
felix