Date: Mon, 24 Oct 2016 16:35:09 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 213749] [PATCH] devel/arduino-builder: Add TOOLS option to bring in tools for standalone building Message-ID: <bug-213749-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213749 Bug ID: 213749 Summary: [PATCH] devel/arduino-builder: Add TOOLS option to bring in tools for standalone building Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: bsdports@kyle-evans.net CC: bsam@FreeBSD.org Keywords: patch Created attachment 176107 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D176107&action= =3Dedit svn(1) diff of devel/arduino-builder Alright, this should be the last fundamental change for devel/arduino-build= er. =3D) Right now, there's two possible configurations for building and flashing Arduino projects: 1.) Use devel/arduino16 -- this pulls in devel/arduino-builder and devel/arduino-tools itself, and uses its own method (as it turns out, completely different from arduino-builder's discovery mechanism =3D() for f= inding the proper utility for flashing (devel/bossa vs. devel/avrdude) 2.) Use devel/arduino-builder + devel/arduino-tools directly, flash the res= ult yourself -- this has the pro of not requiring Java to build a project, but = the con that you do have to figure out how to flash the board (w/ devel/bossa or devel/avrdude) yourself. I suspect that #1 will be the most commonly used configuration, but #2 is n= ice for "advanced" (or not-so-advanced) applications (such as using a Raspberry= Pi to compile+flash firmware for a 3D printer =3D)). As such, we add an OPTION= to make this a more straightforward process of install devel/arduino-builder a= nd then Just Do It. This option will also add in a file at arduino/arduino-builder.options that= can be passed into arduino-builder through the -build-options-file. This removes the need for -hardware, -libraries, and -tools flags based on the defaults = for devel/arduino-tools. This also auto-populates the core version ("runtime.ide.version", -ide-version/-core-api-version, and the ARDUINO #define) with the minimally supported version (see: _COMPAT_VER, _IDE_VER -- these should be kept in sync, and correspond to versions of devel/arduino-{core,tools}) I...I think that's it. =3DP `poudriere testport` still looks good w/ TOOLS = on and TOOLS off, and portlint is still happy. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-213749-13>