Project

General

Profile

Actions

Feature #1224

open

Port all apps to use installed toolchain.

Added by Hammel 2 days ago. Updated about 20 hours ago.

Status:
In Progress
Priority:
Immediate
Assignee:
Category:
00 - Basic Build Issues
Target version:
Start date:
13 Sep 2025
Due date:
% Done:

20%

Estimated time:
Severity:
01 - Critical

Description

This just means that the "-t" option or the TC variable should default to the installation directory for the toolchain.
However, we need to know which hardware we're building for, so all cross.sh need a -b (for "board") option added that can be one of
  1. rpi1
  2. rpi2 (for rpi2, rpi3)
  3. rpi4
  4. xeon

It might be worthwhile to add common code to a sourced script in the toolchain tree. Then all the cross.sh could do "source <toolchain>/common.sh" and Makefiles could include <toolchain>/common. Or these could go in the higher level ~/.pibox, since these would be board inspecific common bits.


Related issues

Blocked by PiBox - Feature #1225: rundock updates to avoid interactive shellNewHammel14 Sep 2025

Actions
Actions #1

Updated by Hammel 1 day ago

  • Blocked by Feature #1225: rundock updates to avoid interactive shell added
Actions #2

Updated by Hammel about 20 hours ago

  • % Done changed from 0 to 20

Support for GNU Make builds has been added with the app-defs.mk installation via the xcc-install target. That file can be included in config.mk for GNU Make based builds. See libleak for an example. The use of this can greatly simplify the GNU Make based builds.

Support for autoconf based builds is in development. It isn't clear if the app-defs.mk can be integrated into the .am files or if a shell script will need to be created that slurps it in an parses it into something cross.sh can utilize.

Actions #3

Updated by Hammel about 20 hours ago

  • Status changed from New to In Progress
Actions

Also available in: Atom PDF