[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-hackers] Questions about cross-compiling Chicken
From: |
Mario Domenech Goulart |
Subject: |
[Chicken-hackers] Questions about cross-compiling Chicken |
Date: |
Wed, 13 Feb 2013 16:57:00 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.2 (gnu/linux) |
Hi,
The "Cross development" chapter in the manual
(http://wiki.call-cc.org/man/4/Cross%20development) suggests the
following command line to build Chicken for the target machine:
make ARCH= \
PREFIX=/usr \
PLATFORM=linux \
HOSTSYSTEM=arm-none-linux-gnueabi \
DESTDIR=$HOME/target \
TARGET_FEATURES="-no-feature x86 -feature arm" \
install
Some questions:
1. Shouldn't ARCH be set with the target platform instead of set empty?
If it is empty, I suppose apply-hack won't be applied, even if it is
supported on the target platform. Is it right? If so, wouldn't it be
better to provide a value for ARCH?
2. On TARGET_FEATURES="-no-feature x86 -feature arm"
If I understand the hardware-related feature correctly, it is set
according to `machine-type', which is determined (in chicken.h --
C_MACHINE_TYPE) based on constants defined by the toolchain header
files. Since we provide HOSTSYSTEM, and C_COMPILER gets its value based
on that (i.e., the toolchain has been selected), is it necessary to
explicitly set TARGET_FEATURES?
Best wishes.
Mario
--
http://parenteses.org/mario
- [Chicken-hackers] Questions about cross-compiling Chicken,
Mario Domenech Goulart <=