Bug 9537 - recipetool: support node.js code outside of npm
Summary: recipetool: support node.js code outside of npm
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 2.0
Hardware: x86 Multiple
: Medium+ enhancement
Target Milestone: 2.2 M3
Assignee: Paul Eggleton
QA Contact: Francisco Pedraza
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-04-27 23:59 UTC by Paul Eggleton
Modified: 2016-09-08 04:58 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2016-04-27 23:59:15 UTC
At the moment you can create a recipe for a Node.js module and its dependencies if you use npm to fetch the source, however if you point to a git repository or tarball of the source, it will recognise that it's Node.js code but doesn't know how to resolve the dependencies (since that his handled within BitBake's npm fetcher). We need to ensure the dependencies get brought in somehow.

An example:

 https://github.com/01org/SmartHome-Demo

We should also get to the point where creating the recipe for a module found through npm gives you pretty much the same built result (at least in terms of package names) as pointing recipetool at the git repository for that same module.
Comment 1 Paul Eggleton 2016-09-05 04:10:20 UTC
I hadn't intended to but I've pretty much ended up fixing this.