Getting sources and building a release with build.sh is not special for evbarm. However, the evbarm port has a very large number of CPU types, compared to i386 and amd64 which have one. The standard approach is to use -m to define MACHINE and -a to define "MACHINE_ARCH". build.sh supports aliases that can be passed a MACHINE value, but denote both MACHINE and a MACHINE_ARCH. The third line is an example (equal to the second in effect). |
Getting sources and building a release with build.sh is not special for evbarm. However, the evbarm port has a very large number of CPU types, compared to i386 and amd64 which have one. The standard approach is to use -m to define MACHINE and -a to define "MACHINE_ARCH". build.sh supports aliases that can be passed as a MACHINE value, but denote both MACHINE and a MACHINE_ARCH. The third line is an example (equal to the second in effect, for RPI2/33). |