From: hobbesc7 <hob...@gm...> - 2013-02-12 20:25:00
|
Is there a trick to installing development packages? I added procps and procps-dev to my gumstix-console-image.bb, and my image seems to build OK (bitbake doesn't complain about not finding procps or procps-dev.) But my crosscompiler still gives the following error when building my application: fatal error: proc/readproc.h: No such file or directory compilation terminated. And when I look in the console image rootfs tarball I don't see readproc.h anywhere. (I want to use this lib to get ps info from within my C app.) -- View this message in context: http://gumstix.8.n6.nabble.com/development-packages-tp4966784.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Trevor W. <two...@gm...> - 2013-02-13 14:09:40
|
On Tue, Feb 12, 2013 at 3:24 PM, hobbesc7 <hob...@gm...> wrote: > Is there a trick to installing development packages? I added procps and > procps-dev to my gumstix-console-image.bb, and my image seems to build OK > (bitbake doesn't complain about not finding procps or procps-dev.) But my > crosscompiler still gives the following error when building my application: > > fatal error: proc/readproc.h: No such file or directory > compilation terminated. > > And when I look in the console image rootfs tarball I don't see readproc.h > anywhere. (I want to use this lib to get ps info from within my C app.) This is an interesting question, if you don't have any luck on this list I'd recommend trying it on the yocto mailing list (if you haven't already). I assume you are cross-compiling your C application on your build machine (rather than building it natively on your gumstix device)? If that is true, my understanding is that you shouldn't need to include procps-dev in your image since including the development files in your target image isn't going to make much of a difference when cross-compiling on your build host. I have a feeling the procps recipe needs some tweaking. I tried a bunch of different stuff and couldn't get the proc/readproc.h file to appear anywhere where it would be found by the cross-development tools when doing cross-development on the build machine. |
From: Trevor W. <two...@gm...> - 2013-02-14 17:32:02
|
On Wed, Feb 13, 2013 at 9:09 AM, Trevor Woerner <two...@gm...> wrote: > I have a feeling the procps recipe needs some tweaking. Yes. I'm no expert, but I'm rather certain the procps recipe needs some extra work. When I install my distribution's procps-devel package onto my machine I get a bunch (including the one you're looking for) of header files in ${prefix}/include/proc. But when I download the procps package itself and perform a "make install", no header files are installed anywhere (ah... the joys of 'homemade' Makefiles :-) ). For now you'll have to kludge together whatever you can (e.g. copy the header file into your build manually or explicitly provide an '-I') but long term this recipe needs some work. |
From: Ryan <rya...@ut...> - 2013-02-18 13:29:26
|
>From what I understand you can install development packages by adding an image feature to your image.bb file. This will install development packages for all packages included in the image, however. IMAGE_FEATURES += "dev-pkgs" Source: http://www.yoctoproject.org/docs/1.2/poky-ref-manual/poky-ref-manual.html#ref-features-image -- View this message in context: http://gumstix.8.n6.nabble.com/development-packages-tp4966784p4966832.html Sent from the Gumstix mailing list archive at Nabble.com. |