Skip to content
This repository was archived by the owner on Jan 15, 2021. It is now read-only.
This repository was archived by the owner on Jan 15, 2021. It is now read-only.

Possible to link local targets and have local modules installed by default? #788

@kzidane

Description

@kzidane

Hi,

total beginner here. have a couple of questions, if you don't mind. I have the following local targets under /usr/lib/yotta_targets with YOTTA_PREFIX pointing to /usr:

  • bbc-microbit-classic-gcc
  • mbed-gcc

specified bbc-microbit-classic-gcc as a global target (as with yotta target -g ...), but the target appears as missing when creating a new module (even though it's under yotta_targets).

$ mkdir bar
$ cd bar
$ yotta init
...
$ yotta target
bbc-microbit-classic-gcc,* missing 

is there a way to get yotta to link targets from yotta_targets by default?

if not, I'm able to yotta link-target bbc-microbit-classic-gcc in a newly created module, but that leaves mbed-gcc missing, so I have to do another yotta link-target mbed-gcc. is there a way to link the former and have the latter linked automatically (assuming both exist under yotta_targets)?

also possible to have a module like lancaster-university/microbit (https://github.com/lancaster-university/microbit) linked and installed by default within newly created modules (so that I don't have to yotta link and yotta install manually inside every module I create)? that is (assuming microbit is under /usr/lib/yotta_modules), instead of:

mkdir foo
cd foo
yotta init
yotta link-target  bbc-microbit-classic-gcc
yotta link-target mbed-gcc
yotta link microbit
yotta install microbit

is there a way to only need to do:

mkdir foo
cd foo
yotta init

thanks!

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions