Bug 212964
| Summary: | [NEW PORT] devel/arduino-builder: Command-line tool for building Arduino sketches | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Kyle Evans <kevans> | ||||||||
| Component: | Individual Port(s) | Assignee: | Boris Samorodov <bsam> | ||||||||
| Status: | Closed FIXED | ||||||||||
| Severity: | Affects Only Me | CC: | bsam | ||||||||
| Priority: | --- | ||||||||||
| Version: | Latest | ||||||||||
| Hardware: | Any | ||||||||||
| OS: | Any | ||||||||||
| Bug Depends on: | 212956 | ||||||||||
| Bug Blocks: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 175583 [details]
shar(1) archive of devel/arduino-builder
Port altered based on suggestions by swills@ -- no longer requires changes to go.mk.
Created attachment 175584 [details]
Updated shar(1) archive of devel/arduino-builder
Forgot to add the build dep on Go back in after removing USES=go -- this is fixed.
A commit references this bug: Author: bsam Date: Tue Oct 11 15:02:05 UTC 2016 New revision: 423766 URL: https://svnweb.freebsd.org/changeset/ports/423766 Log: arduino-builder is a command line tool for compiling Arduino sketches. It is used by newer versions of the Arduino IDE, and may also be used standalone if provided hardware definitions and a tools directory. WWW: https://github.com/arduino/arduino-builder PR: 212964 Submitted by: bsdports@kyle-evans.net Changes: head/devel/Makefile head/devel/arduino-builder/ head/devel/arduino-builder/Makefile head/devel/arduino-builder/distinfo head/devel/arduino-builder/pkg-descr Committed, thanks!
I've just made a tiny fix: env -> ${SETENV}. We recommend against using direct commands.
|
Created attachment 175129 [details] shar(1) archive of devel/arduino-builder Hello! arduino-builder is a comand-line tool for building Arduino sketches. It's required for the newer versions of the Arduino IDE (not yet brought into the ports tree). It's a golang app. split into four packages with three external dependencies. I wasn't entirely sure how to handle this cleanly, so any feedback is appreciated. I have an open PR #212956 that proposes how to handle bringing in multiple packages or supporting a build where the application source is packaged as an 'out-of-tree' kind of build (root of the repository != root of package).