Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • P porting-mr16-to-ath79
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Vermont Community Internet
  • Burlington Community Mesh Network
  • porting-mr16-to-ath79
  • Issues
  • #2

Closed
Open
Created Dec 13, 2019 by Martin Kennedy@hurricosOwner0 of 2 tasks completed0/2 tasks

Set up source branches correctly on `golem` for making builds

Instructions for working on code

You may ssh into gandalf and then ssh golem from gandalf. At that point, the Openwrt sources and image builder have been stuck under ~/devel/openwrt/.

Instructions for building an image

To build, an image, run make menuconfig to verify that the file .config is pointing at the right target to build (MR16 on the ar71xx or ath79), and then run make -j16 (16 core CPU). Note that the subtarget will not immediately have MR16 available in make menuconfig as it's not currently buildable under ar71xx (since it's been set to source only or something).

We will need to figure out based on other ports to ath79 (see the OpenWrt git) what changes are required for the MR16 to show up under the ath79 menuconfig.

Tasks

  • Determine how previous ath79 ports are showing up in make menuconfig under the ath79 target

    • In which file is it actually determined that a given board builds under a given file?
  • Make sure @sam is set up with golem

    • For separating commits between two people, we should set some profile variables or invoke Git in a particular way. Here's a stackexchange question on how this is done in practice with multiple people sharing the same build server.
Edited Dec 18, 2019 by Sam Jessup
Assignee
Assign to
Time tracking