Replies: 2 comments
-
|
Hello! I read about this briefly in this paper where a Graduate student at the University of Colorado mentioned this exact same problem. It's been a few years since the paper, and it generally seems as though Basilisk has transitioned away from running on embedded systems, but it is possible that this paper will provide some insight. Please reply if it was helpful! |
Beta Was this translation helpful? Give feedback.
-
|
Hey! If you're still looking for a solution, I managed to work around this issue by using Buildroot to cross-compile both CSPICE and Basilisk for my BeagleBone Black (ARMv7-A architecture).
################################################################################
#
# cspice
#
################################################################################
CSPICE_VERSION = N0067
# The file is a .Z archive (old Unix compress), which requires custom extraction logic
CSPICE_SOURCE = cspice.tar.Z
CSPICE_SITE = https://naif.jpl.nasa.gov/pub/naif/toolkit//C/PC_Linux_GCC_64bit/packages
CSPICE_LICENSE = NAIF
CSPICE_LICENSE_FILES = doc/html/index.html
CSPICE_INSTALL_STAGING = YES
CSPICE_INSTALL_TARGET = NO
# ------------------------------------------------------------------------------
# 1. EXTRACT COMMANDS (The Fix)
# ------------------------------------------------------------------------------
# Buildroot doesn't natively handle .Z files well in all versions.
# We force it to use zcat (gzip) to decompress, then pipe to tar.
define CSPICE_EXTRACT_CMDS
$(ZCAT) $(CSPICE_DL_DIR)/$(CSPICE_SOURCE) | tar --strip-components=1 -C $(@D) -xf -
endef
# ------------------------------------------------------------------------------
# 2. BUILD COMMANDS
# ------------------------------------------------------------------------------
# -fPIC: Required for creating Python bindings later
# -w: Suppress warnings
define CSPICE_BUILD_CMDS
mkdir -p $(@D)/lib
cd $(@D)/src/cspice && $(TARGET_CC) $(TARGET_CFLAGS) -fPIC -w -c *.c -I$(@D)/include
cd $(@D)/src/cspice && $(TARGET_AR) cr $(@D)/lib/libcspice.a *.o
$(TARGET_RANLIB) $(@D)/lib/libcspice.a
endef
# ------------------------------------------------------------------------------
# 3. INSTALL COMMANDS
# ------------------------------------------------------------------------------
define CSPICE_INSTALL_STAGING_CMDS
$(INSTALL) -D -m 0644 $(@D)/lib/libcspice.a $(STAGING_DIR)/usr/lib/libcspice.a
mkdir -p $(STAGING_DIR)/usr/include/cspice
$(INSTALL) -m 0644 $(@D)/include/*.h $(STAGING_DIR)/usr/include/cspice/
endef
$(eval $(generic-package)) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey everyone,
I am trying to run basilisk on a Raspberry Pi 5 (armv8 processor architecture).
However, when trying to build, an error occurs showing that cspice does not support gcc on linux armv8. Does anyone know whether there might be a workaround for this or different version of cspice that does support this? If so, how could I tell the basilisk compilation to load that version?
Thanks a lot for your help
Beta Was this translation helpful? Give feedback.
All reactions