Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Collapse
Brand Logo

ModalAI Forum

  1. ModalAI Support Forum
  2. VOXL SDK and Software
  3. SDK package versions and voxl-cross container versions

SDK package versions and voxl-cross container versions

Scheduled Pinned Locked Moved Unsolved VOXL SDK and Software
voxl-sdk
3 Posts 2 Posters 844 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • I Offline
    I Offline
    ianjsherman
    wrote on last edited by
    #1

    I have a Docker-based build pipeline that:

    • Inside the voxl-cross:2.7 container, installs ModalAI packages
    DEPS="
    libmodal-pipe
    "
    PLATFORM=qrb5165
    SECTION=sdk-1.4
    
    # Add to /etc/apt/sources.list.d
    DPKG_FILE="/etc/apt/sources.list.d/modalai.list"
    LINE="deb [trusted=yes] http://voxl-packages.modalai.com/ ./dists/$PLATFORM/$SECTION/binary-arm64/"
    sudo echo "${LINE}" > ${DPKG_FILE}
    
    ## Update package index
    sudo apt-get update -o Dir::Etc::sourcelist="sources.list.d/modalai.list" -o Dir::Etc::sourceparts="-" -o APT::Get::List-Cleanup="0"
    
    ## Install dependencies
    sudo apt install -y $DEPS
    
    • Inside the same container, builds my application

    Over the weekend my build broke due to an incompatibility between the newly released libmodal-pipe_2.13.1_arm64.deb (released to the sdk-1.4 apt repository) and the voxl-cross:2.7 build container.

    My workaround has been to pin the version of the libmodalpipe apt package I install: libmodal-pipe=2.10.6.

    How should I think about versioning guarantees between the SDK version and the voxl-cross container version? Should I expect packages in a given SDK version to continue to build in a given voxl-cross container version? Or is your recommendation to live at the bleeding edge of the voxl-cross container version?

    James StrawsonJ 1 Reply Last reply
    0
    • I ianjsherman

      I have a Docker-based build pipeline that:

      • Inside the voxl-cross:2.7 container, installs ModalAI packages
      DEPS="
      libmodal-pipe
      "
      PLATFORM=qrb5165
      SECTION=sdk-1.4
      
      # Add to /etc/apt/sources.list.d
      DPKG_FILE="/etc/apt/sources.list.d/modalai.list"
      LINE="deb [trusted=yes] http://voxl-packages.modalai.com/ ./dists/$PLATFORM/$SECTION/binary-arm64/"
      sudo echo "${LINE}" > ${DPKG_FILE}
      
      ## Update package index
      sudo apt-get update -o Dir::Etc::sourcelist="sources.list.d/modalai.list" -o Dir::Etc::sourceparts="-" -o APT::Get::List-Cleanup="0"
      
      ## Install dependencies
      sudo apt install -y $DEPS
      
      • Inside the same container, builds my application

      Over the weekend my build broke due to an incompatibility between the newly released libmodal-pipe_2.13.1_arm64.deb (released to the sdk-1.4 apt repository) and the voxl-cross:2.7 build container.

      My workaround has been to pin the version of the libmodalpipe apt package I install: libmodal-pipe=2.10.6.

      How should I think about versioning guarantees between the SDK version and the voxl-cross container version? Should I expect packages in a given SDK version to continue to build in a given voxl-cross container version? Or is your recommendation to live at the bleeding edge of the voxl-cross container version?

      James StrawsonJ Offline
      James StrawsonJ Offline
      James Strawson
      ModalAI Team
      wrote on last edited by
      #2

      @ianjsherman While we are slowly migrating packages to build in a new build environment, the API for libmodal_pipe should not have changed and installing the new binary package in voxl-cross 2.7 into order to build and link against should not have broken. Do you mind sharing what exactly broke in your build as there might have been something that I missed.

      James StrawsonJ 1 Reply Last reply
      0
      • James StrawsonJ James Strawson

        @ianjsherman While we are slowly migrating packages to build in a new build environment, the API for libmodal_pipe should not have changed and installing the new binary package in voxl-cross 2.7 into order to build and link against should not have broken. Do you mind sharing what exactly broke in your build as there might have been something that I missed.

        James StrawsonJ Offline
        James StrawsonJ Offline
        James Strawson
        ModalAI Team
        wrote on last edited by
        #3

        @James-Strawson

        hmmm, by any chance are you failing to link against symbols from libgmb.so? That is a new library dependency of libmodal_pipe. Most of our packages use the following linker flags to avoid recursive linking, I think this would be a better solution than specifying the libmodal_pipe version in install_build_deps.sh

        set(CMAKE_C_FLAGS "-Wl,--unresolved-symbols=ignore-in-shared-libs ${CMAKE_C_FLAGS}")
        set(CMAKE_CXX_FLAGS "-Wl,--unresolved-symbols=ignore-in-shared-libs ${CMAKE_CXX_FLAGS}")

        1 Reply Last reply
        0

        Reading along? Create a free ModalAI Forum account to join in.

        With an account you can reply, ask your own question, get an email when a ModalAI engineer answers, and mark the reply that solved it. Your place in each thread is saved between visits.

        Questions about VOXL, Flight Core, ESCs and ModalAI drones are answered here by the engineers who build them.

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        ModalAI
        Categories Recent Tags ModalAI.com Docs
        © 2026 ModalAI® · Accelerating autonomy for smaller, smarter, safer drones · Powered by NodeBB
        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups