From: Bernhard Roth <broth@roth-itk.de>
To: buildroot@busybox.net
Subject: [Buildroot] Adding libev to buildroot
Date: Sun, 07 Aug 2011 13:10:55 +0200 [thread overview]
Message-ID: <4E3E72BF.9040302@roth-itk.de> (raw)
Hello all,
I am using buildroot for a while now and I always have to add the libev
library for my projects. Libev is a lightweight and powerful alternative
to livevent.
Maybe it's possible to add libev support to the next official version of
buildroot.
Attached I send you the package config files for libev which I use
(based on libevent files)
Please put them into package/libev.
Finally following line has to be added to package/Config.in just after
libevent
source "package/libev/Config.in"
Best regards,
Bernhard Roth
--
____________________________________
Roth ITK Consulting GmbH
Landsberger Str. 398
81241 M?nchen
Germany
Fon: +49 89 461317-0
Fax: +49 89 461317-29
Email: broth at roth-itk.de
Web: http://www.roth-itk.de/
Gesch?ftsf?hrer: Bernhard Roth
HRB 174971, Amtsgericht M?nchen
UID: DE 261 708 872
____________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Config.in
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110807/7726e19d/attachment.in>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: libev.mk
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110807/7726e19d/attachment.ksh>
next reply other threads:[~2011-08-07 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 11:10 Bernhard Roth [this message]
2011-08-07 21:04 ` [Buildroot] Adding libev to buildroot Yegor Yefremov
[not found] ` <4E3F79CF.40608@roth-itk.de>
[not found] ` <CAGm1_ktqDGmoRtbWuN8uDM3qiL00K+kS-VbyVcDV3p9sqav9Jg@mail.gmail.com>
2011-08-08 13:19 ` Bernhard Roth
2011-08-08 14:55 ` Yegor Yefremov
2011-09-10 15:13 ` Peter Korsgaard
2011-09-10 21:27 ` Yegor Yefremov
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=4E3E72BF.9040302@roth-itk.de \
--to=broth@roth-itk.de \
--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.