Re: [yocto] m4-native, zedboard, "Please port gnulib fseeko.c to your platform"
On Wed, Nov 14, 2018 at 5:19 PM Gunnar Andersson wrote: > > Robert, > > On Tue, 2018-11-13 at 15:28 -0500, Robert P. J. Day wrote: > > been away from YP for a few months, diving back in, want to build a > > core-image-minimal for my zedboard, and i will first admit that i'm > > using a non-approved distro (fully-updated fedora 29): > > > > [...] > > > but i'm unsure (read, have no clue) how to deal with this > > If upgrading Yocto/poky and layers is not an option for you, then building > in a container is the typical approach. This isolates you from any host- > distro issues, since any distro can be used in the container. > > Many just set up their own with a simple Docker file, but from what I > remember the CROPS project is one common project recommended in the past. > Here's a random starting point I found [1]. > move to thud, ive confirmed it works on fedora 29 after seeing the same issue, or ...VM with Debian / Ubuntu > HTH, > - Gunnar > > [1] https://www.yoctoproject.org/learn-items/cross-platform-enablement-for-t > he-yocto-project-with-containers/ > > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] using pip3-native to install python requirements
On Mon, Nov 12, 2018 at 3:22 PM Belisko Marek wrote:
>
> Hi,
>
> I'm having recipe for custom python3 application whcih need to install
> ~20 python dependencies. I've create requirements.txt and using pip on
> PC I can install necessary python packages. When try to use
> pip3-native (as DEPENDS) and call pip3 I get some errors:
>
> pkg_resources.VersionConflict: (pip 8.1.1
> (/usr/lib/python3/dist-packages), Requirement.parse('pip==9.0.1'))
>
> I would like to ask it pip3 can be used (didn't find any other
> occurrence in poky) or should I add python dependencies as RDEPENDS ?
i believe you just need to add inherit setuptools3 to the recipe your
trying to use pip3 for
> Thanks.
>
> BR,
>
> marek
>
>
> --
> as simple and primitive as possible
> -
> Marek Belisko - OPEN-NANDRA
> Freelance Developer
>
> Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
> Tel: +421 915 052 184
> skype: marekwhite
> twitter: #opennandra
> web: http://open-nandra.com
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] core-image-weston w/ initramfs
so core-image-weston works fine with the touch screen, then we added core-image-minimal initramfs so we could boot with encrypted filesystem, however now it seems the touch screen has lost its touch and pointed capabilities, ive determined that much by looking at the logs for when weston fails, same occurs with x11 image ideas where to look to re-enable this -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: [meta-raspberrypi] Problem with adding udev rules
couldnt this have been a udev_append.bb
instead of writing your own my-rules
On Wed, Nov 7, 2018 at 6:46 PM Markus W wrote:
>
> This my bb file and than I have added the following to local.conf
> IMAGE_INSTALL_append = " my-rules ...".
>
> SUMMARY = "My rules"
> LICENSE = "CLOSED"
> PR = "r1"
>
> SRC_URI = "file://90-interfaces.rules"
>
> do_install[nostamp] = "1"
> do_unpack[nostamp] = "1"
>
> do_install () {
> install -d ${D}${sysconfdir}/udev/rules.d
> install -m 0666 ${WORKDIR}/90-interfaces.rules
> ${D}/etc/udev/rules.d/90-interfaces.rules
>
> }
>
> FILES_${PN} += " /etc/udev/rules.d/90-interfaces.rules"
>
> PACKAGES = "${PN}"
> PROVIDES = "my-rules"
>
> Hope this helps
>
> /Markus
>
> On Wed, 7 Nov 2018 at 12:41, Outback Dingo wrote:
>>
>> so curious, as im trying to add 2 udev rules also that i require in my
>> build, so how was your recipe configured?
>>
>> mine keeps telling me i have a conflict between packages as they both
>> install files to the same name and same place
>> On Wed, Nov 7, 2018 at 4:53 PM Outback Dingo wrote:
>> >
>> >
>> >
>> > On Wed, Nov 7, 2018, 16:44 Markus W > >>
>> >> I have resolved this issue. My problem was that in my layer I have a
>> >> recipe-core and within that I had the following structure
>> >> udev/udev-extra-rules and udev-extra-rules.bb file and a files dir on
>> >> the same level.
>> >>
>> >> By renaming udev/udev-extra-rules to my-udev/my-udev-extra-rules it
>> >> suddenly worked.
>> >>
>> >> Cool
>> >>
>> >>
>> >> Regards,
>> >> Markus
>> >>
>> >> On Tue, 6 Nov 2018 at 14:06, Outback Dingo wrote:
>> >> >
>> >> > On Tue, Nov 6, 2018 at 11:57 AM Markus W wrote:
>> >> > >
>> >> > > Hi!
>> >> > >
>> >> > > I want to append the rules in the
>> >> > > recipe-core/udev/udev-rules-rpi/99-com.rules with the rules below from
>> >> > > within my own recipe. I can´t figure out how to do that.
>> >> > >
>> >> > > I have tried to add those rules as separate rules file in a recipe in
>> >> > > my own layer. After the build I can see that the rules file is in the
>> >> > > correct directory /etc/udev/rules.d (next to 99-com.rules) but the
>> >> > > rules didn't get applied. The groups below I have created by
>> >> > > inheriting the useradd class (GROUPADD_PARAM_${PN} = "-r spi; -r i2c;
>> >> > > -r gpio") in a different layer with a higher priority than the layer
>> >> > > with the rules recipe.
>> >> > >
>> >> > > Not sure why this is not working. Any suggestions?
>> >> > >
>> >> > > 90-interfaces.rules file:
>> >> > >
>> >> > > SUBSYSTEM=="input", GROUP="input", MODE="0660"
>> >> > > SUBSYSTEM=="i2c-dev", GROUP="i2c", MODE="0660"
>> >> > > SUBSYSTEM=="spidev", GROUP="spi", MODE="0660"
>> >> > > SUBSYSTEM=="bcm2835-gpiomem", GROUP="gpio", MODE="0660"
>> >> > >
>> >> > > SUBSYSTEM=="gpio", GROUP="gpio", MODE="0660"
>> >> > > SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c '\
>> >> > > chown -R root:gpio /sys/class/gpio && chmod -R 770 /sys/class/gpio;\
>> >> > > chown -R root:gpio /sys/devices/virtual/gpio && chmod -R 770
>> >> > > /sys/devices/virtual/gpio;\
>> >> > > chown -R root:gpio /sys$devpath && chmod -R 770 /sys$devpath\
>> >> > > '"
>> >> > >
>> >> >
>> >> > might help to post the recipe used.
>> >> >
>> >> >
>> >> > > Regards,
>> >> > > Markus
>> >> > > --
>> >> > > ___
>> >> > > yocto mailing list
>> >> > > yocto@yoctoproject.org
>> >> > > https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: [meta-raspberrypi] Problem with adding udev rules
On Wed, Nov 7, 2018, 16:44 Markus W I have resolved this issue. My problem was that in my layer I have a
> recipe-core and within that I had the following structure
> udev/udev-extra-rules and udev-extra-rules.bb file and a files dir on
> the same level.
>
> By renaming udev/udev-extra-rules to my-udev/my-udev-extra-rules it
> suddenly worked.
>
> Cool
>
>
> Regards,
> Markus
>
> On Tue, 6 Nov 2018 at 14:06, Outback Dingo wrote:
> >
> > On Tue, Nov 6, 2018 at 11:57 AM Markus W wrote:
> > >
> > > Hi!
> > >
> > > I want to append the rules in the
> > > recipe-core/udev/udev-rules-rpi/99-com.rules with the rules below from
> > > within my own recipe. I can´t figure out how to do that.
> > >
> > > I have tried to add those rules as separate rules file in a recipe in
> > > my own layer. After the build I can see that the rules file is in the
> > > correct directory /etc/udev/rules.d (next to 99-com.rules) but the
> > > rules didn't get applied. The groups below I have created by
> > > inheriting the useradd class (GROUPADD_PARAM_${PN} = "-r spi; -r i2c;
> > > -r gpio") in a different layer with a higher priority than the layer
> > > with the rules recipe.
> > >
> > > Not sure why this is not working. Any suggestions?
> > >
> > > 90-interfaces.rules file:
> > >
> > > SUBSYSTEM=="input", GROUP="input", MODE="0660"
> > > SUBSYSTEM=="i2c-dev", GROUP="i2c", MODE="0660"
> > > SUBSYSTEM=="spidev", GROUP="spi", MODE="0660"
> > > SUBSYSTEM=="bcm2835-gpiomem", GROUP="gpio", MODE="0660"
> > >
> > > SUBSYSTEM=="gpio", GROUP="gpio", MODE="0660"
> > > SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c '\
> > > chown -R root:gpio /sys/class/gpio && chmod -R 770 /sys/class/gpio;\
> > > chown -R root:gpio /sys/devices/virtual/gpio && chmod -R 770
> > > /sys/devices/virtual/gpio;\
> > > chown -R root:gpio /sys$devpath && chmod -R 770 /sys$devpath\
> > > '"
> > >
> >
> > might help to post the recipe used.
> >
> >
> > > Regards,
> > > Markus
> > > --
> > > ___
> > > yocto mailing list
> > > yocto@yoctoproject.org
> > > https://lists.yoctoproject.org/listinfo/yocto
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Fwd: [meta-raspberrypi] Problem with adding udev rules
On Tue, Nov 6, 2018 at 11:57 AM Markus W wrote:
>
> Hi!
>
> I want to append the rules in the
> recipe-core/udev/udev-rules-rpi/99-com.rules with the rules below from
> within my own recipe. I can´t figure out how to do that.
>
> I have tried to add those rules as separate rules file in a recipe in
> my own layer. After the build I can see that the rules file is in the
> correct directory /etc/udev/rules.d (next to 99-com.rules) but the
> rules didn't get applied. The groups below I have created by
> inheriting the useradd class (GROUPADD_PARAM_${PN} = "-r spi; -r i2c;
> -r gpio") in a different layer with a higher priority than the layer
> with the rules recipe.
>
> Not sure why this is not working. Any suggestions?
>
> 90-interfaces.rules file:
>
> SUBSYSTEM=="input", GROUP="input", MODE="0660"
> SUBSYSTEM=="i2c-dev", GROUP="i2c", MODE="0660"
> SUBSYSTEM=="spidev", GROUP="spi", MODE="0660"
> SUBSYSTEM=="bcm2835-gpiomem", GROUP="gpio", MODE="0660"
>
> SUBSYSTEM=="gpio", GROUP="gpio", MODE="0660"
> SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c '\
> chown -R root:gpio /sys/class/gpio && chmod -R 770 /sys/class/gpio;\
> chown -R root:gpio /sys/devices/virtual/gpio && chmod -R 770
> /sys/devices/virtual/gpio;\
> chown -R root:gpio /sys$devpath && chmod -R 770 /sys$devpath\
> '"
>
might help to post the recipe used.
> Regards,
> Markus
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Where to look when literally nothing happens?
On Thu, Nov 1, 2018 at 6:50 PM Outback Dingo wrote: > > On Thu, Nov 1, 2018 at 6:33 PM Erik Hoogeveen > wrote: > > > > Hello, > > > > I’m rather new to embedded software and Yocto. I hope this is the right > > place to ask. If not I’d appreciate it if someone could point me the right > > way to do so. > > > > I’m trying to make a Yocto build for a raspberry pi 3. I’ve got it booting > > and doing things on a regular plain vanilla Raspberry pi 3 board. It boots > > and over serial console I can log in and do things. > > But the ultimate target is to run this image on my own board which is built > > around a Raspberry Pi Compute Module 3 Lite. Since regular Raspbian (what’ > > I’ve used so far) works fine on both boards without modification I assumed > > that this would be the case as well with this image I made myself. But it > > turns out I was wrong. > > > > When I take the image from the build and stick it in my compute module > > board, literally nothing happens. The boot sequence doesn’t seem to even > > begin, I get nothing on the serial console, and none of the peripherals > > like the ethernet ever come to life either. > > > > And since nothing happens I really have no idea where to look for a > > solution. I’m guessing this is a bit of a noob issue? It would be great if > > someone could point me in a direction to look at. > > you probably built for a raspberrypi3 or raspberrypi3-64 ffor the 64bit > > i believe the compute module 3 target is raspberrypi-cm3 > > you could pretty muuchh do a diff uunder the meta-raspberryypi ffor > the differences in whats built Yupp see The choices for MACHINE are raspberrypi (BCM2835) raspberrypi0 (BCM2835) raspberrypi0-wifi (BCM2835) raspberrypi2 (BCM2836 or BCM2837 v1.2+) raspberrypi3 (BCM2837) raspberrypi-cm (BCM2835) raspberrypi-cm3 (BCM2837) see https://jumpnowtek.com/rpi/Raspberry-Pi-Systems-with-Yocto.html its a good read on PIs > > > > > Kind regards, > > Erik Hoogeveen. > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Where to look when literally nothing happens?
On Thu, Nov 1, 2018 at 6:33 PM Erik Hoogeveen wrote: > > Hello, > > I’m rather new to embedded software and Yocto. I hope this is the right place > to ask. If not I’d appreciate it if someone could point me the right way to > do so. > > I’m trying to make a Yocto build for a raspberry pi 3. I’ve got it booting > and doing things on a regular plain vanilla Raspberry pi 3 board. It boots > and over serial console I can log in and do things. > But the ultimate target is to run this image on my own board which is built > around a Raspberry Pi Compute Module 3 Lite. Since regular Raspbian (what’ > I’ve used so far) works fine on both boards without modification I assumed > that this would be the case as well with this image I made myself. But it > turns out I was wrong. > > When I take the image from the build and stick it in my compute module board, > literally nothing happens. The boot sequence doesn’t seem to even begin, I > get nothing on the serial console, and none of the peripherals like the > ethernet ever come to life either. > > And since nothing happens I really have no idea where to look for a solution. > I’m guessing this is a bit of a noob issue? It would be great if someone > could point me in a direction to look at. you probably built for a raspberrypi3 or raspberrypi3-64 ffor the 64bit i believe the compute module 3 target is raspberrypi-cm3 you could pretty muuchh do a diff uunder the meta-raspberryypi ffor the differences in whats built > > Kind regards, > Erik Hoogeveen. > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding own shell script to the image
On Mon, Oct 29, 2018 at 8:47 PM Uwe Geuder wrote:
>
> On Mon, Oct 29, 2018 at 3:28 PM Zolee K zoleelikesdebian-at-gmail.com wrote:
>
> > The error message:
> >
> > /home//recipes-z/testing/testing.bb: Unable to get checksum for testing
> > SRC_URI entry testscript: *file could not be found*
> > Which I don't understand, since the file is definitaly there:-(
> > Could you please help me out with this?
my working recipe
cat eventmanager_0.0.5.bb
LICENSE = "CLOSED"
LIC_FILES_CHKSUM = ""
PR="r1"
RDEPENDS_${PN} = " \
python3-sdnotify \
"
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI = " \
file://${BPN}_${PV}.7z \
"
inherit bin_package systemd
do_unpack[depends] += "p7zip-native:do_populate_sysroot"
S = "${WORKDIR}"
do_install() {
--SNIP---
~/Yocto/meta-event/recipe-event/eventmanager ls -al
total 16
drwxrwxr-x. 3 dingo dingo 4096 Sep 30 07:48 .
drwxrwxr-x. 10 dingo dingo 4096 Oct 19 14:49 ..
-rw-r--r--. 1 dingo dingo 1147 Sep 30 00:37 eventmanager_0.0.5.bb
drwxrwxr-x. 2 dingo dingo 4096 Oct 20 10:30 files
ls -al files/
total 144
drwxrwxr-x. 2 dingo dingo 4096 Oct 20 10:30 .
drwxrwxr-x. 3 dingo dingo 4096 Sep 30 07:48 ..
-rw---. 1 dingo dingo 128273 Oct 20 10:30 eventmanager_0.0.5.7z
>
> Bitbake uses a search path to locate the files, see
>
> https://www.yoctoproject.org/docs/2.5.1/mega-manual/mega-manual.html#var-FILESEXTRAPATHS
>
> Either extend the path or move your file to a location on the path.
>
> If you are unsure what your current search path is you can always check
> from the output of
>
> bitbake -e
>
>
> Regards,
>
> Uwe Geuder
> Neuro Event Labs Oy
> Tampere, Finland
> uwe.gexder at neuroeventlabs.com (Bot check: fix one obvious typo)
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding own shell script to the image
On Mon, Oct 29, 2018 at 8:32 PM Outback Dingo wrote:
>
> SRC_URI = "file://testscript"
>
> FILESEXTRAPATHS_prepend := "${THISDIR}/file:"
>
> and file should be files
crap ... sorry for the top post
> On Mon, Oct 29, 2018 at 8:28 PM Zolee K wrote:
> >
> > Hi All,
> >
> > I'm struggling with this:
> >
> > The error message:
> >
> > /home//recipes-z/testing/testing.bb: Unable to get checksum for testing
> > SRC_URI entry testscript: file could not be found
> > Which I don't understand, since the file is definitaly there:-(
> > Could you please help me out with this?
> >
> > #
> > this is my test folder:
> >
> > testing/
> > ├── file
> > │ └── testscript
> > └── testing.bb
> > #
> > cat testing/testing.bb
> > DESCRIPTION = "test script"
> > LICENSE = "Z"
> > SRC_URI = "file://testscript"
> > SRC_URI[md5sum] = "e51375ed8c617ea7a6ac39b81c757e39"
> > do_install() {
> > install -d ${D}${bindir}
> > install -m 0770 testscript ${D}${bindir}
> > }
> > ###
> > cat testing/file/testscript
> > #!/bin/sh
> > echo "hello world"
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] adding own shell script to the image
SRC_URI = "file://testscript"
FILESEXTRAPATHS_prepend := "${THISDIR}/file:"
and file should be files
On Mon, Oct 29, 2018 at 8:28 PM Zolee K wrote:
>
> Hi All,
>
> I'm struggling with this:
>
> The error message:
>
> /home//recipes-z/testing/testing.bb: Unable to get checksum for testing
> SRC_URI entry testscript: file could not be found
> Which I don't understand, since the file is definitaly there:-(
> Could you please help me out with this?
>
> #
> this is my test folder:
>
> testing/
> ├── file
> │ └── testscript
> └── testing.bb
> #
> cat testing/testing.bb
> DESCRIPTION = "test script"
> LICENSE = "Z"
> SRC_URI = "file://testscript"
> SRC_URI[md5sum] = "e51375ed8c617ea7a6ac39b81c757e39"
> do_install() {
> install -d ${D}${bindir}
> install -m 0770 testscript ${D}${bindir}
> }
> ###
> cat testing/file/testscript
> #!/bin/sh
> echo "hello world"
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Installing Python app from source
On Fri, Oct 5, 2018 at 12:48 AM Brian Zambrano wrote:
>
> In a Python project with a setup.py file, you can actually do "pip install ."
> Of course you still need internet access for dependencies, which I have
> during the build. This is similar to running "python setup.py install" in
> the same directory.
curious where you found this innformatioon and what that recipe would
look like ?
>
> I've tried setting SRC_URI="saunders_backend" along with "import setuptools".
> That seems to run "python setup.py install" during the build phase, however
> I get an error that setup.py cannot be found.
>
> Also, my setup.py contains a section for scripts, which results on my script
> being placed into the a bin directory on the host when installed normally:
>
> scripts=['bin/server'],
>
> So, setup.py can do everything I need outside of bitbake/yocto...I just can't
> figure out how to get it working during the bitbake build.
>
> On Thu, Oct 4, 2018 at 11:08 AM Shantanoo Desai wrote:
>>
>> Hi Brian,
>>
>>
>>
>> It is confusing, I agree. But I think it is essential because I assume your
>> Target is not connected to the Internet. When you do pip install
>> normally the package if fetched from the internet and then installed. In
>> this case your app is local so need to have those files first built natively
>> and then need to be sent to the appropriate folders for python to access
>> them which I guess what setuptools does. Hence you set all the files in the
>> SRC_URI.
>>
>>
>>
>> Do_install_append is only when you have binaries which could be used as
>> command line utilities.
>>
>>
>> (But I could also be completely wrong, not a Yocto guru here)
>>
>>
>>
>> Cheers
>>
>>
>>
>> Shan
>>
>>
>>
>> Von: Brian Zambrano
>> Gesendet: Donnerstag, 4. Oktober 2018 18:33
>> An: de...@uni-bremen.de
>> Cc: yocto@yoctoproject.org
>> Betreff: Re: [yocto] Installing Python app from source
>>
>>
>>
>> Thanks very much for this Shan. I have that book and was working through it
>> yesterday, as a matter of fact.
>>
>>
>>
>> That part which is confusing to me in that recipe is that the SRC_URI points
>> to every single file, there is a "inherit setuptools" line and also a
>> do_install_append. I'm not sure how each of these are working together to
>> get the application installed. I believe that the "inherit setuptools" will
>> automatically run "python setup.py install", but when then is the source
>> code manually copied over?
>>
>>
>>
>> BZ
>>
>>
>>
>> On Thu, Oct 4, 2018 at 2:13 AM Shantanoo Desai wrote:
>>
>> Hi Brian,
>>
>>
>>
>> What you need in the .bb is a runtime-dependency. RDEPENDS_${PN} += “
>> ${PYTHON_PN}-flask ${PYTHON_PN}-jinja ${PYTHON_PN}-markdown” and so on. This
>> will add these modules in the root-filesystem and will be available on the
>> target.
>>
>>
>>
>> If you need some basic help with a python recipe, there is a git repository
>> YoctoCookbook
>> https://github.com/yoctocookbook/meta-custom/tree/master/recipes-python/python-helloworld
>> to get you some idea.
>>
>>
>>
>> Please not I am in no ways a Yocto expert on recipe creations but for the
>> past few weeks this is what I have been able to discover. Due to lack of
>> examples on custom recipes in python this is the best I can help you with.
>>
>>
>>
>>
>>
>> Best Regards,
>>
>>
>>
>> Shan
>>
>>
>>
>>
>>
>>
>>
>> Von: yocto-boun...@yoctoproject.org Im
>> Auftrag von Brian Zambrano
>> Gesendet: Donnerstag, 4. Oktober 2018 00:52
>> An: yocto@yoctoproject.org
>> Betreff: [yocto] Installing Python app from source
>>
>>
>>
>> I'm trying to install my own Python application from source, and having a
>> hard time finding resources on how to accomplish it. I'm new to this
>> ecosystem and am probably missing something fundamental.
>>
>> My recipe is structured like this...and my build is configure such that it
>> does actually find it.
>>
>> ├── firmware-1.0
>> │ ├── saunders_backend
>> │ └── saunders_frontend
>>
>> └── firmware_1.0.bb
>>
>> My application code which is for now just a "hello world" flask application,
>> is in saunders_backend. The setup.py file in there works as expected when I
>> use it in on my host machine.
>>
>> ├── firmware-1.0
>> │ ├── saunders_backend/
>> │ │ ├── bin/
>> │ │ │ └── server
>> │ │ ├── MANIFEST.in
>> │ │ ├── requirements.txt
>> │ │ ├── saunders_apollo/
>> │ │ │ ├── config.py
>> │ │ │ ├── __init__.py
>> │ │ │ ├── models.py
>> │ │ │ ├── static/
>> │ │ │ ├── templates/
>> │ │ │ └── views.py
>> │ │ └── setup.py
>>
>> │ └── saunders_frontend/
>> └── firmware_1.0.bb
>>
>>
>> I've been hacking on the .bb files to get it to install this into the
>> resulting image. I do have IMAGE_INSTALL_append = " firmware" in the
>> top-level local.conf.
>>
>>
>>
>> My primary confusion is that I don't know what I should be using for the
>> python application. do_install, do_install_append? What should SRC_UIR be?
>> In effect is
[yocto] Yocto poky headless Pi 0 W - OTG /RNDIS
Headless Raspberry PI 0 W cant get OTG rndis up, i followed the guide and set ENABLE_UART = "1" ENABLE_DWC2_PERIPHERAL = "1" current config is MACHINE ??= "raspberrypi0-wifi" SERIAL_CONSOLE = "" ENABLE_UART = "1" ENABLE_DWC2_PERIPHERAL = "1" DISABLE_RPI_BOOT_LOGO = "1" DISABLE_OVERSCAN = "1" DISABLE_SPLASH = "1" BOOT_DELAY = "0" GPU_MEM_256 = "128" GPU_MEM_512 = "196" GPU_MEM_1024 = "396" DISTRO_FEATURES_remove = "x11" DISTRO_FEATURES_append = " opengl" PACKAGE_CLASSES = "package_ipk" IMAGE_INSTALL_append = " chrony" IMAGE_INSTALL_append = " linux-firmware-bcm43430 wpa-supplicant" IMAGE_FSTYPES = "tar.bz2 ext4 rpi-sdimg" SDIMG_ROOTFS_TYPE = "ext4" CORE_IMAGE_EXTRA_INSTALL += "openssh" DISTRO_FEATURES_append += "bluez5 bluetooth wifi" as following the docs it stated ENABLE_UART = "1" ENABLE_DWC2_PERIPHERAL = "1" for OTG, buut i dont seem to see any rndis on my laptop via thhe second poort, Rasbian / DietPI work fine, so do i need to edit the config.txt and cmdline.txt like in Raspbian? also do we need a ssh file in boot as also with Raspbian ? Edit the file config.txt and add dtoverlay=dwc2 on its own line at the end. Edit the file cmdline.txt and add modules-load=dwc2,g_ether right after it says rootwait Thanks in Advance -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Function failed: do_package_qa
On Mon, Mar 12, 2018 at 3:59 PM, Outback Dingo <outbackdi...@gmail.com> wrote:
> -snip--
Okay ive confirmed this works, building fine again all the way through, thanks
>
> okay ive updated the makefile with your edits and read the doc, the
> new version is here... is it on the right track ??? much appreciated
> the insight
> modifications below
>
> #
> # This file was derived from the 'Hello World!' example recipe in the
> # Yocto Project Development Manual.
> #
>
> DESCRIPTION = "DLT Wrapper"
> SECTION = "libs"
> DEPENDS = "boost libusb1 dlt-daemon"
> LICENSE = "COMPANY_COMMON_LICENSES"
> LIC_FILES_CHKSUM =
> "file://${COMPANY_COMMON_LICENSES}/LICENSE;md5=18f1f6bf24836561f3a65cef19477d20"
>
> CFLAGS += "-std=gnu++14"
>
> inherit cmake
>
> # Use local tarball
> SRC_URI = "file://DLTWrapper.tgz"
>
> # The base package, this includes everything needed to actually run
> the application on the target system.
> PACKAGES += "FILES-${PN}-lib"
>
> FILES_${PN}-lib = "\
> ${libdir}/lib*.so.* \
> ${includedir}/*"
>
> # Make sure our source directory (for the build) matches the directory
> structure in the tarball
> S = "${WORKDIR}/DLTWrapper"
> PACKAGES = "${PN} FILES-${PN}-lib ${PN}-dev ${PN}-dbg ${PN}-staticdev"
>
> RDEPENDS_${PN}-staticdev = ""
> RDEPENDS_${PN}-dev = ""
> RDEPENDS_${PN}-dbg = ""
>
> INSANE_SKIP_${PN} = "ldflags"
> INHIBIT_PACKAGE_STRIP = "1"
> INHIBIT_SYSROOT_STRIP = "1"
> SOLIBS = ".so"
> FILES_SOLIBSDEV = ""
>
> do_install () {
> install -d ${D}${libdir}
> install -m 0755 ${WORKDIR}/libfoo.so ${D}${libdir}
> install -m 0755 ${WORKDIR}/DLTWrapper/include/* ${D}${includedir}
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Function failed: do_package_qa
-snip--
okay ive updated the makefile with your edits and read the doc, the
new version is here... is it on the right track ??? much appreciated
the insight
modifications below
#
# This file was derived from the 'Hello World!' example recipe in the
# Yocto Project Development Manual.
#
DESCRIPTION = "DLT Wrapper"
SECTION = "libs"
DEPENDS = "boost libusb1 dlt-daemon"
LICENSE = "COMPANY_COMMON_LICENSES"
LIC_FILES_CHKSUM =
"file://${COMPANY_COMMON_LICENSES}/LICENSE;md5=18f1f6bf24836561f3a65cef19477d20"
CFLAGS += "-std=gnu++14"
inherit cmake
# Use local tarball
SRC_URI = "file://DLTWrapper.tgz"
# The base package, this includes everything needed to actually run
the application on the target system.
PACKAGES += "FILES-${PN}-lib"
FILES_${PN}-lib = "\
${libdir}/lib*.so.* \
${includedir}/*"
# Make sure our source directory (for the build) matches the directory
structure in the tarball
S = "${WORKDIR}/DLTWrapper"
PACKAGES = "${PN} FILES-${PN}-lib ${PN}-dev ${PN}-dbg ${PN}-staticdev"
RDEPENDS_${PN}-staticdev = ""
RDEPENDS_${PN}-dev = ""
RDEPENDS_${PN}-dbg = ""
INSANE_SKIP_${PN} = "ldflags"
INHIBIT_PACKAGE_STRIP = "1"
INHIBIT_SYSROOT_STRIP = "1"
SOLIBS = ".so"
FILES_SOLIBSDEV = ""
do_install () {
install -d ${D}${libdir}
install -m 0755 ${WORKDIR}/libfoo.so ${D}${libdir}
install -m 0755 ${WORKDIR}/DLTWrapper/include/* ${D}${includedir}
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Function failed: do_package_qa
Well heres the dltwrapper bb file it appears to build fine
#
# This file was derived from the 'Hello World!' example recipe in the
# Yocto Project Development Manual.
#
DESCRIPTION = "DLT Wrapper"
SECTION = "examples"
DEPENDS = "boost libusb1 dlt-daemon"
LICENSE = "COMPANY_COMMON_LICENSES"
LIC_FILES_CHKSUM =
"file://${COMPANY_COMMON_LICENSES}/LICENSE;md5=18f1f6bf24836561f3a65cef19477d20"
TARGET_CFLAGS += "-std=gnu++14"
# This tells bitbake where to find the files we're providing on the
local filesystem
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
FILES_${PN} += "${includedir}/*"
inherit autotools gettext cmake
# Use local tarball
SRC_URI = "file://DLTWrapper.tgz"
# Make sure our source directory (for the build) matches the directory
structure in the tarball
S = "${WORKDIR}/DLTWrapper"
do_install() {
install -d ${D}${libdir}
install -d ${D}${includedir}
install -m 0755 ${WORKDIR}/build/libDLTWrapper.so ${D}${libdir}
install -m 0755 ${WORKDIR}/DLTWrapper/include/* ${D}${includedir}
}
On Mon, Mar 12, 2018 at 12:58 PM, Burton, Ross <ross.bur...@intel.com> wrote:
> At a guess as I don't have any of your recipes to look at, jsonparser and
> dltwrapper packages are broken and putting the libraries into the -dev
> packages. That probably caused a QA warning too.
>
> Ross
>
> On 12 March 2018 at 11:53, Outback Dingo <outbackdi...@gmail.com> wrote:
>>
>> ERROR: QA Issue: r4-hub rdepends on dltwrapper-dev [dev-deps]
>> ERROR: QA Issue: r4-hub rdepends on jsonparser-dev [dev-deps]
>> ERROR: QA run found fatal errors. Please consider fixing them.
>> ERROR: Function failed: do_package_qa
>> ERROR: Logfile of failure stored in: log.do_package_qa.21297
>>
>> seems ive created a bitbake recipe, which depends on a couple of
>> libraries to be built, so i created the bitbake for the libs and all
>> appears to build fine, however seeing the failure above its basically
>> telling me something isnt being created during the packaging process
>> for the libs to be properly included in the image, they does exist a
>> pkgname-dev.ipkg for each of the libs but not a packagename.ipkg ...
>> any ideas... its kind of holding me up at this point.
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Function failed: do_package_qa
ERROR: QA Issue: r4-hub rdepends on dltwrapper-dev [dev-deps] ERROR: QA Issue: r4-hub rdepends on jsonparser-dev [dev-deps] ERROR: QA run found fatal errors. Please consider fixing them. ERROR: Function failed: do_package_qa ERROR: Logfile of failure stored in: log.do_package_qa.21297 seems ive created a bitbake recipe, which depends on a couple of libraries to be built, so i created the bitbake for the libs and all appears to build fine, however seeing the failure above its basically telling me something isnt being created during the packaging process for the libs to be properly included in the image, they does exist a pkgname-dev.ipkg for each of the libs but not a packagename.ipkg ... any ideas... its kind of holding me up at this point. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
