On 2015-01-26 06:29, James Abernathy wrote:

On Jan 23, 2015, at 12:37 PM, Gary Thomas <g...@mlbassoc.com> wrote:

On 2015-01-23 10:24, Jim Abernathy wrote:
I'm starting a project mostly for self-education.  I have already done the 
project using Ubuntu Server 14.04 using a Intel NUC and a Pandaboard as 
targets.  Now I want to see how
easy it is to move it to Yocto.

Starting with the NUC, I can boot Dizzy 1.7.1 core-image-minimal and 
core-image-sato, both built with bitbake and not the prebuilt images. However, 
core-image-minimal doesn't have
WiFi and core-image-sato does, but I don't need all the GUI stuff.  It's a 
headless application.

So what is recommended; eliminating the GUI from sato or adding wifi and 
wpa-supplicant, etc to minimal??  Also any pointers to how to do the 
adding/subtracting would be most helpful.

Once this is working all I have to do is put apache-tomcat, and openjdk-7-jre, 
then my application.

We use just iw & wpa-supplicant and set up the configuration
files manually (e.g. the wpa-supplicant configurations).

Could you help with a little more details.  What I envision is adding an append 
statement of some kind to local.conf to load in the wireless related files to 
core-image-minimal, same with openjdk-7-jre and tomcat7, but my first efforts 
have generated some unintelligible error for me.  So that’s why I’m looking for 
direction on where to start with this.

What was the error you got?  I'll bet it was for 'iw' which
is a package from meta-oe, so you'll need to add that layer

Once you've added the meta-oe layer, you should be able to
put this line in your local.conf:
  CORE_IMAGE_EXTRA_INSTALL += " iw wpa-supplicant"

--
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to