All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <trevor.woerner@linaro.org>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: inherit setuptools
Date: Sat, 22 Mar 2014 07:01:25 -0400	[thread overview]
Message-ID: <532D6D85.7010302@linaro.org> (raw)

Hi,

I'm trying to write a recipe to add a native python application to the
sysroot so it can be used while building an image.

If I build and install the python app "by hand" I get the following
install layout:

.
|-- bin
|   `-- bmaptool
`-- lib
    `-- python2.7
        `-- site-packages
            |-- bmap_tools-3.2-py2.7.egg
            |-- easy-install.pth
            |-- site.py
            `-- site.pyc

When I use my recipe I get:

.
|-- bin
|   `-- bmaptool
`-- lib
    `-- python2.7
        `-- site-packages
            |-- bmap_tools-3.2-py2.7.egg-info
            |   |-- PKG-INFO
            |   |-- SOURCES.txt
            |   |-- dependency_links.txt
            |   `-- top_level.txt
            `-- bmaptools
                |-- BmapCopy.py
                |-- BmapCopy.pyc
                |-- BmapCreate.py
                |-- BmapCreate.pyc
                |-- BmapHelpers.py
                |-- BmapHelpers.pyc
                |-- Filemap.py
                |-- Filemap.pyc
                |-- TransRead.py
                |-- TransRead.pyc
                |-- __init__.py
                `-- __init__.pyc

When my build tries to invoke the bmaptool it fails because:

| Traceback (most recent call last):
|   File
"/SSD/build/fsl/build-wandboard-dual/tmp/sysroots/x86_64-linux/usr/bin/bmaptool",
line 65, in <module>
|     from bmaptools import BmapCreate, BmapCopy, BmapHelpers, TransRead
| ImportError: No module named bmaptools

Should I ignore "setuptools" and write my own install task? Or is there
some quick and easy fix for this?


             reply	other threads:[~2014-03-22 11:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-22 11:01 Trevor Woerner [this message]
2014-03-22 19:45 ` inherit setuptools Burton, Ross
2014-03-22 21:07   ` Trevor Woerner
2014-03-25 16:08   ` Trevor Woerner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=532D6D85.7010302@linaro.org \
    --to=trevor.woerner@linaro.org \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.