> From: Martin Jansa > > Are you talking about openembedded as openembedded-classic or > meta-openembedded? > > Use samba from meta-openembedded.
That's what I tried first. It's not a layer, but a collection of layers, and the layer that contains samba is called meta-oe. So I tried to include meta-openembedded/meta-oe, and it barfed due to the absence of fontcache.bbclass. But fontcache.bbclass is nowhere to be found in meta-openembedded; it's contained in openembedded-core/meta. So I included openembedded-core/meta, and got some other error message containing about a dozen lines of Python script that had raised an exception. I tried including openembedded instead/too, and got other error messages. To someone who understands the shape of the universe, this is probably easy to figure out. I might feel the trunk, or the tail, but I don't know it's an elephant yet. Since samba is a fairly common, standard module, I was hoping someone here had already done this, and could tell me what buttons to push. I've read the scant docs on bitbake, and pretty much the entire Yocto docs and Openembedded docs, and my head is spinning. I don't mind learning some stuff, but if I have to spend six months becoming an expert on something just to get it to work, then this is an economically unviable project for me. Or maybe I should just build the system without samba, run it, manually install samba just like any other user, and then use dd to save the modified image for production use. Does that sound like a good idea? -- Ciao, Paul D. DeRocco Paul mailto:pdero...@ix.netcom.com _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto