Kaleidoscope

Commit Graph

Author	SHA1	Message	Date
Brian Cully	39d1f70812	Add rules and scripts for building on FreeBSD. * Uses usbconfig to determine the Model 01's USB modem port. * Works around incompatibe avrsize flags. You need to be able to run usbconfig to flash the firmware from the buildtools. This can be accomplished with appropriate groups and devfs rules. Requires gmake, perl, avrdude, and (probably) arduino18 from ports. The version of avrdude in ports uses an avr-size command that doesn't understand the -C or --mcu flags. From what I can tell, these flags are uneccessary, as the size computed with them is the same as what you get from adding up the appropriate segments from the standard output of avr-size without any flags. However, since the size is only informative, I've opted to simply check to see if the command succeeded, and if not, output a string saying it could not be. It would probably be better to: * Determine appropriate flags based on build tools, or, * Just not use the flags at all, and grab the .text, etc., segment sizes from the standard output and add them up via `dc` for display. I've been using this toolchain to build successfully on FreeBSD 12 for the Model 01 without issue. It should work with earlier versions of FreeBSD as well. Signed-off-by: Brian Cully <bjc@kublai.com>	6 years ago

Author

SHA1

Message

Date

Brian Cully

39d1f70812

Add rules and scripts for building on FreeBSD.

* Uses usbconfig to determine the Model 01's USB modem port.

  * Works around incompatibe avrsize flags.

You need to be able to run usbconfig to flash the firmware from the
buildtools. This can be accomplished with appropriate groups and devfs
rules.

Requires gmake, perl, avrdude, and (probably) arduino18 from ports.

The version of avrdude in ports uses an avr-size command that doesn't
understand the -C or --mcu flags. From what I can tell, these flags
are uneccessary, as the size computed with them is the same as what
you get from adding up the appropriate segments from the standard
output of avr-size without any flags. However, since the size is only
informative, I've opted to simply check to see if the command
succeeded, and if not, output a string saying it could not be.

It would probably be better to:

  * Determine appropriate flags based on build tools, or,

  * Just not use the flags at all, and grab the .text, etc., segment
    sizes from the standard output and add them up via `dc` for
    display.

I've been using this toolchain to build successfully on FreeBSD 12 for
the Model 01 without issue. It should work with earlier versions of
FreeBSD as well.

Signed-off-by: Brian Cully <bjc@kublai.com>

1 Commits (31c80b58116c05e182c9e9b90472c11beadc996f)