Giter VIP home page Giter VIP logo

meta-labgrid's People

Contributors

bastian-krause avatar ejoerns avatar emantor avatar fbertux avatar h-assmann avatar hnez avatar jluebbe avatar prevas-jdtn avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

meta-labgrid's Issues

kirkstone: python3-xmodem: do_install append is no longer required

The following packaging logic from python3-xmodem is causing an error when used with kirkstone layer. It appears that is logic is on longer required as we can see the correct files are installed in the correct locations (rather than in "${D}/usr/doc/").


do_install:append() {
    # Move the documentation files to the expected location so they are
    # packaged in the *-docs package.
    mkdir -p ${D}${docdir}/
    mv ${D}/usr/doc/* ${D}${docdir}/
    rmdir ${D}/usr/doc
}

Here is the error that is produced:

mv: cannot stat '<SNIP>/python3-xmodem/0.4.6-r0.2/image/usr/doc/*': No such file or directory
WARNING: exit code 1 from a shell command.                                   
ERROR: Logfile of failure stored in: <SNIP>/python3-xmodem/0.4.6-r0.2/temp/log.do_install.10947  

We can see that the correct files are installed:

$ find <SNIP>/python3-xmodem/0.4.6-r0/image/
<SNIP>/python3-xmodem/0.4.6-r0/image/
<SNIP>/python3-xmodem/0.4.6-r0/image/usr
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/share
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/share/doc
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/share/doc/ymodem.txt
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/share/doc/XMODEM.TXT
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/share/doc/XMODEM1K.TXT
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/share/doc/XMODMCRC.TXT
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/lib
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/lib/python3.9
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/lib/python3.9/site-packages
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/lib/python3.9/site-packages/xmodem-0.4.6-py3.9.egg-info
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/lib/python3.9/site-packages/xmodem-0.4.6-py3.9.egg-info/SOURCES.txt
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/lib/python3.9/site-packages/xmodem-0.4.6-py3.9.egg-info/PKG-INFO
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/lib/python3.9/site-packages/xmodem-0.4.6-py3.9.egg-info/top_level.txt
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/lib/python3.9/site-packages/xmodem-0.4.6-py3.9.egg-info/dependency_links.txt
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/lib/python3.9/site-packages/xmodem
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/lib/python3.9/site-packages/xmodem/__pycache__
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/lib/python3.9/site-packages/xmodem/__pycache__/__main__.cpython-39.pyc
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/lib/python3.9/site-packages/xmodem/__pycache__/__init__.cpython-39.pyc
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/lib/python3.9/site-packages/xmodem/__main__.py
<SNIP>/python3-xmodem/0.4.6-r0/image/usr/lib/python3.9/site-packages/xmodem/__init__.py

pyproject.toml packaging does not work correctly with kirkstone version of openembedded

labgrid switched to pyproject.toml based packaging recently and support for that was added to this layer in 1d2b916 . The support for this in openembedded seems to be undergoing some change currently, but the implementation in openembedded-core@kirkstone does not fully support it. For labgrid (as packaged via the recipes in this layer@ 101db61 ) it produces a mostly empty package, lacking basically all of labgrid:

tree packages-split/python3-labgrid/
packages-split/python3-labgrid/
├── etc
│   └── labgrid
│       ├── configuration.yaml
│       └── environment
├── lib
│   └── systemd
│       ├── system
│       │   └── labgrid-exporter.service
│       └── system-preset
│           └── 98-python3-labgrid.preset
└── usr
    └── lib
        └── python3.11
            └── site-packages
                └── labgrid-23.0b2.dev20.dist-info
                    ├── entry_points.txt
                    ├── LICENSE
                    ├── METADATA
                    ├── RECORD
                    ├── top_level.txt
                    └── WHEEL

I'm leaving this here to document this behavior. I moved on to using the current master branch of openembedded-core and it works fine there.

In case anyone is looking into how to workaround this (since kirkstone is the current LTS release and compatibility with it would be nice) the command that is run and produces an almost empty wheel is:

# line: 33, file: /work/layers/external/poky/meta/classes/python_pep517.bbclass
python_pep517_do_compile() {
    cd /build/workspace/sources/python3-labgrid
    nativepython3 -c "import setuptools.build_meta as api; api.build_wheel('/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/python3-labgrid/git-r0/dist')"
}

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.