New port: devel/arduino-bsd-mk - build Arduino sketches with make(1)

[leres]

Summary

Proposed commit message:

This adds devel/arduino-bsd-mk which installs a make(1) makefile
(bsd.arduino.mk) that is used to build Arduino sketches from
the command line. It is designed to be an FreeBSD-friendly
alternative to the existing gmake based devel/arduino-mk port.
It includes a man page and optionally installs an example sketch
with an exmaple Makefile.

Reviewed by: ? (mentor)
Approved by: ? (mentor)
Differential Revision: ?

[matthew]

devel/arduino-bsd-mk/Makefile

8 ↗

(On Diff #35832)

While it is possible to add your disfiles to the ports tree (as you have done here), this is something that should be used sparingly. In this case, I think you've enough
content here that you should create a tarball of it. Place that tarball in ~leres/public_distfiles on Freefall and use MASTERSITE = LOCAL/leres unless you prefer to use some other distribution site.

27 ↗

(On Diff #35832)

This line should be wrapped to within 80 columns as far as possible

42 ↗

(On Diff #35832)

Using a tarball as I said above makes this target redundant

46 ↗

(On Diff #35832)

This is creating the same directory multiple times. Plus it's usual to create the installation directories as part of the 'do-install:' target.

You can simplify all this quite a lot by setting variables something like this:

SCRIPTS_INSTALL_DIR= arduino-bsd-mk/scripts
SCRIPTS= arduino-boards.py arduino-version.sh gcc-version.sh

Alternatively, if you distribute a tarball, you can structure the tarball so that you can use COPYTREE_BIN to install all your scripts in a one-liner, which includes creating all the directories you need under staging

devel/arduino-bsd-mk/pkg-descr

8 ↗

(On Diff #35832)

Comic sans?

[mat]

devel/arduino-bsd-mk/Makefile

20 ↗

(On Diff #35832)

Does this run with Python 3.6 ?

[leres]

Split makefile, man page and scripts into a separate distribution

[leres]

devel/arduino-bsd-mk/Makefile

8 ↗

(On Diff #35832)

Ok, I've reworked it to package the content separately from the port

20 ↗

(On Diff #35832)

Not sure; I changed USES to specify python 2 and also patch the script to use ${PYTHON_CMD} in the script.

27 ↗

(On Diff #35832)

(It moved to the distribution makefile.)

46 ↗

(On Diff #35832)

The ":u" should eliminate the duplicates; but I added :O (sort) just to be sure.

I guess I don't like COPYTREE_BIN in this case since I like to have file extensions in the distribution but remove them on installation. Anyway see if the new version is acceptable.

devel/arduino-bsd-mk/pkg-descr

8 ↗

(On Diff #35832)

im-comic-sans-********

[matthew]

devel/arduino-bsd-mk/Makefile

40 ↗

(On Diff #35942)

USES shebangfix

should be used to set the python interpreter

devel/arduino-bsd-mk/pkg-descr

8 ↗

(On Diff #35832)

Heh.

[leres]

Add shebangfix to USES as suggested by matthew@

[leres]

devel/arduino-bsd-mk/Makefile

40 ↗

(On Diff #35942)

That's sweet, thanks!

[mat]

devel/arduino-bsd-mk/Makefile

18–19 ↗

(On Diff #35943)

Out of order. See Chapter 14. Order of Variables in Port Makefiles.

42 ↗

(On Diff #35943)

s/"*"/./

20 ↗

(On Diff #35832)

No, you just said "I want the python2" symlink. Saying you want Python 2 is written as USES=python:2.7.

[leres]

devel/arduino-bsd-mk/Makefile

18–19 ↗

(On Diff #35943)

(Somewhat surprised portlint doesn't catch this.)

This version should be better.

20 ↗

(On Diff #35832)

I guess I don't see how you can have python2 installed and not have some specific version (e.g. 2.7) of python installed?

(Or is your point that I don't *need* python2, just python27?)

Anyway: fixed.

[leres]

Address mat@'s comments

[leres]

Address mat@'s comments [take #2: actually update Makefile]

[matthew]

LGTM

[matthew]

Note: be sure to use ${PORTSDIR}/Tools/scripts/addport to commit your new port -- this will ensure that it gets hooked up to the ports tree correctly.