- Remove custom build/install targets left in place after r505321
- Switch to the new GO_TARGET tuple syntax introduced in r512001
- Switch to go:modules when upstream already uses them
Reviewed by: tobik
Approved by: araujo (mentor), portmgr (adamw)
Differential Revision: https://reviews.freebsd.org/D21741
This allows for port testing with lang/go-devel via GO_PORT, setting
up the Go build environment in a single place, and is step one in
simplifying Go ports that often define too complicated do-build
targets themselves.
USES=go gains new arguments 'run' to add lang/go to RUN_DEPENDS and
'no_targets' for ports with composite builds that call 'go' themselves
and do not need the do-build/do-install targets of USES=go.
PR: 238849
Submitted by: dg@syrec.org (also D20745)
Reviewed by: mat, tobik
Exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D20746
The most notable change in this update is that .hpp and .hh files are now
included when searching for libraries.
PR: 217961
Submitted by: Kyle Evans <bsdports@kyle-evans.net> (maintainer)
devel/arduino-builder. =)
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
=() for finding the proper utility for flashing (devel/bossa vs.
devel/avrdude)
2.) Use devel/arduino-builder + devel/arduino-tools directly, flash
the result 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 nice for "advanced" (or not-so-advanced) applications (such
as using a Raspberry Pi to compile+flash firmware for a 3D printer
=)). As such, we add an OPTION to make this a more straightforward
process of install devel/arduino-builder and 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})
PR: 213749
Submitted by: Kyle Evans <bsdports@kyle-evans.net> (maintainer)
