ports/156143: New port: devel/arduino-mk: Build Arduino sketches from the command line

[Michael Scheidell]

The following reply was made to PR ports/156143; it has been noted by GNATS.

From: Michael Scheidell <scheidell at freebsd.org>
To: <bug-followup at FreeBSD.org>
Cc:  
Subject: Re: ports/156143: New port: devel/arduino-mk: Build Arduino sketches
 from the command line
Date: Thu, 23 Feb 2012 08:57:18 -0500

 On 2/22/12 9:58 PM, Craig Leres wrote:
 >      hot 53 % ls -l /usr/local/arduino/lib/version.txt
 >      -rw-r--r--  1 root  wheel  3 Nov 28 16:56
 > /usr/local/arduino/lib/version.txt
 >
 > I don't see any obvious problems and am not sure how to debug this.
 >
 > 		Craig
 
 build is done in a 'tinderbox' (you can use redports if you like)
 it starts with a clean 'jail', adds all the dependencies in 
 BUILD_DEPENDS and LIB_DEPENDS, and then tries to build port, create a 
 package, and then remove the package and checks for left over 'parts'
 
 it seems to fail, because arduino-mk needs the version.txt to PATCH, way 
 ahead of the 'build' side.
 
 (you can deinstall arduino, make sure version.txt is missing, then in 
 arduino-mk, do a:
 
 make patch
 
 to solve this, you add something like:
 
 PATCH_DEPENDS=    PATCH_DEPENDS=  
 ${LOCALBASE}/arduino/lib/version.txt:${PORTSDIR}/devel/arduino
 
 Q: you have arduino as a BUILD_DEPENDS, which does not mean that it is 
 automatically a RUN_DEPENDS, did you mean for this to be needed to RUN 
 arduino-mk also? if so, I can add it to RUN_DEPENDS.
 
 I have done both of the above, but you still have a problem with the port.
 
 you specified p5-YAML:${PORTSDIR}/textproc/p5-YAML
 
 p5-YAML is not an executable, (what happens when you type 'p5-YAML' ? 
 does it run?)
 
 you need something like:
 
 ${SITE_PERL}/YAML/Any.pm:${PORTSDIR}/textproc/p5-YAML
 
 which I have added.
 
 based on the p5-YAML issue, there is actually no way this port would 
 have built, unless you set the variable "FORCE_PKG_REGISTER"
        in your environment or the "make install" command line.
 
 I have added all of these above, and will be committing this new port 
 shortly.
 
 You have another new port pending, my suggestion:
 ask that the existing pr for that new port be closed, start with a clean 
 slate.
 join redports, test your new port with redports (does it depend on this 
 one? might take 4 hours for redports to sync mirrors)
 once you know you have it right, use 'send-pr -a'  (attachment) and open 
 a new pr, with a proper shar in it.
 
 
 
 
 -- 
 Michael Scheidell, CTO
  >*| * SECNAP Network Security Corporation
 d: +1.561.948.2259
 w: http://people.freebsd.org/~scheidell