All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Martin <s.martin49@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] (newbie question)
Date: Thu, 17 May 2012 02:08:02 +0200	[thread overview]
Message-ID: <CAHXCMM+=U2hTS_KkcMLErJwxvgBYKCAtLjzP6T2vWusw9QVkdw@mail.gmail.com> (raw)
In-Reply-To: <CAFC29aXHt7pqDojsYLRHhrwReZOTny84S1zUZo5YNqYSLe3C1w@mail.gmail.com>

Hi Ron,

2012/5/16 Ron Eggler <reggler@semiosbio.com>:
>
> Hi Arnout,
>
> Okay so I retried this, this time with another iteration of my buildroot
> directory.
> I attempted to add the weex driver that depends on
> python-configobj
> python-serial (already present)
> python-cheetah
> python-imaging

The 4 packages you attempted to add unfortunately use python easy-install.
Though easy-install does perfectly the job for natively installation,
it's really a PITA for integration in cross-dev environment.

Have a look at the python-netifaces. It uses easy-install too, but
with python-distutilscross (also in the Buildroot tree).

> so I added the required files, compiled and guess what, it's not working. I
> suspect that I did the same mistake as at my first try. Here are the diff
> files (see attached). (I hope I did it correctly now, if not, let me know!)
>
> Thank you,
> Ron


BTW, the toolchainfile.cmake is automatically generated by Buildroot.


Cheers,

Sam

      reply	other threads:[~2012-05-17  0:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 20:28 [Buildroot] (newbie question) Ron Eggler
2012-05-15 20:42 ` Thomas Petazzoni
2012-05-15 20:51   ` Arnout Vandecappelle
2012-05-15 21:13   ` Ron Eggler
2012-05-15 21:30     ` Arnout Vandecappelle
2012-05-15 21:52       ` Ron Eggler
2012-05-15 22:33         ` Samuel Martin
     [not found]         ` <4FB2D92E.9030905@mind.be>
2012-05-16 18:33           ` Ron Eggler
2012-05-17  0:08             ` Samuel Martin [this message]

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='CAHXCMM+=U2hTS_KkcMLErJwxvgBYKCAtLjzP6T2vWusw9QVkdw@mail.gmail.com' \
    --to=s.martin49@gmail.com \
    --cc=buildroot@busybox.net \
    /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.