Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] [PATCH v3] lcdapi: new package
From: Arnout Vandecappelle @ 2012-10-26 23:16 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <1351269168-12577-1-git-send-email-spdawson@gmail.com>

On 26/10/12 18:32, spdawson at gmail.com wrote:
> From: Simon Dawson<spdawson@gmail.com>
>
> Signed-off-by: Simon Dawson<spdawson@gmail.com>

Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Tested-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
  (build-test on a minimal PPC internal toolchain)

  Regards,
  Arnout
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

^ permalink raw reply

* [Buildroot] post-buil script in chrooted
From: Arnout Vandecappelle @ 2012-10-26 23:05 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <508AF8EF.4070002@free.fr>

On 26/10/12 22:56, David Bonnin wrote:
> Exactly, i want to create few users on the target, and copy files for each user, like ftpUser , httpdUser, userMyApp,
> userMyBackupApp.
> I doesn't want to copy files only for root.
>
> My apps(2) on the target doesn't run under root privileveges, and have theirs own default files/directory.

  If you want to set file owners and permissions on the target, you should use
the device table (BR2_ROOTFS_DEVICE_TABLE).  Look at
target/generic/device_table.txt for an example.

  Regards,
  Arnout
-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

^ permalink raw reply

* [Buildroot] [PATCH 05/47] package/usbredir: new package
From: Arnout Vandecappelle @ 2012-10-26 23:00 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <201210261939.13810.yann.morin.1998@free.fr>

On 26/10/12 19:39, Yann E. MORIN wrote:
> BTW, this series was just a kind of "drop the stuff onto the wall and see
> what happens", after requests on the IRC chan. It was not meant for
> inclusion. But getting early review is very nice! Thank you!

  I think in general it makes more sense to post an early version of a patch
and catch some review already, rather than spending a lot time to make a
patch that you think is perfect and then still get a lot of comments...

  Regards,
  Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

^ permalink raw reply

* [Buildroot] [PATCH 02/47] package/libfdt: new package
From: Arnout Vandecappelle @ 2012-10-26 22:58 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <201210261936.20493.yann.morin.1998@free.fr>

On 26/10/12 19:36, Yann E. MORIN wrote:
> Arnout, All,
>
> On Thursday 25 October 2012 Arnout Vandecappelle wrote:
[snip]
>>    dtc generates Flattened Device Trees (i.e. it flattens the device
>> tree).
>
>  From Documentation/manual.txt:
>
> ---8<---
> The currently supported Input Formats are:
>      - "dtb": "blob" format.  A flattened device-tree block with
>          header in one binary blob.
>      - "dts": "source" format.  A text file containing a "source"
>          for a device-tree.
>      - "fs" format.  A representation equivalent to the output of
>          /proc/device-tree  where nodes are directories and
>          properties are files.
>
> The currently supported Output Formats are:
>       - "dtb": "blob" format
>       - "dts": "source" format
>       - "asm": assembly language file.  A file that can be sourced
>          by gas to generate a device-tree "blob".  That file can
>          then simply be added to your Makefile.  Additionally, the
>          assembly file exports some symbols that can be used.
> ---8<---
>
> So, dtc does not /generate/ flattened, it uses them as _input_.

  Only the dtb is flattened, the source and fs are still a tree.
But anyway, what I wrote wasn't correct either.

> What about this formulation (also from the same manual.txt) :
>
>      The Device Tree Compiler, dtc, takes as input a device-tree in
>      a given format and outputs a device-tree in another format.

  Much better :-)


>>> +	  Note that only the library is installed for now.
>>    Why?  Build failures in the binaries?
>
> Because I do not need it in my use-case, so I did not test it, so
> I did not install it.

  Well, it just seems silly to do extra effort to remove something from the
build, unless there's a good reason for it. So unless there's a build
failure, I would include the dtc as well even if you haven't tested it
on the target.


> Also, this package could probably also be a host package. This patch
> only adds dtc as a target package.

  For the host package, it's probably dtc that you need anyway...

>
> [--SNIP--]
>>> ++++ dtc-e4b497f367a3b2ae99cc52089a14a221b13a76ef/Makefile	2012-10-22 22:03:21.151047833 +0200
>>> +@@ -18,7 +18,7 @@
>>> + CPPFLAGS = -I libfdt -I .
>>> + WARNINGS = -Werror -Wall -Wpointer-arith -Wcast-qual -Wnested-externs \
>>> + 	-Wstrict-prototypes -Wmissing-prototypes -Wredundant-decls
>>> +-CFLAGS = -g -Os -fPIC -Werror $(WARNINGS)
>>> ++CFLAGS = -g -Os -fPIC -Werror $(WARNINGS) $(EXTRA_CFLAGS)
>>
>>    Why not CFLAGS += ...?
>>
>>    And maybe CPPFLAGS should also be fixed.
>
> I'll look again at this.
>
> [--SNIP--]
>>> diff --git a/package/dtc/dtc.mk b/package/dtc/dtc.mk
>>> new file mode 100644
>>> index 0000000..d53e78a
>>> --- /dev/null
>>> +++ b/package/dtc/dtc.mk
>>> @@ -0,0 +1,36 @@
>>> +#############################################################
>>> +#
>>> +# libcurl
>
> dtc, not libcurl. Sigh...
>
>>> +#
>>> +#############################################################
>>> +
>>> +DTC_VERSION         = e4b497f367a3b2ae99cc52089a14a221b13a76ef
>>> +DTC_SITE            = git://git.jdl.com/software/dtc.git
>>> +DTC_LICENSE         = GPLv2+/BSD-2c
>>> +DTC_LICENSE_FILES   = README.license GPL
>>> +# Note: the dual-license only applies to the library.
>>> +#       The DT compiler (dtc) is GPLv2+, but we do not install it.
>>> +DTC_INSTALL_STAGING = YES
>>> +
>>> +# Need -fPIC for x86-64
>>    ???
>
> Probably left-over from debugging?...

  Now I see it: the -fPIC is in the upstream Makefile and is required
(unlike the -g -Os -Werror), so the CFLAGS shouldn't just be overridden.



  Regards,
  Arnout
[snip]

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

^ permalink raw reply

* [Buildroot] Licensing information
From: Yann E. MORIN @ 2012-10-26 22:02 UTC (permalink / raw)
  To: buildroot

Hello All!

In a few packages I've encountered, and for which we may install only part
of the package (eg. only the libs, or the libs and the programs), and those
parts are not under the same licensing terms (but not necesarily conflicting),
there is no way in buildroot to convey such information.

Also, there is no way (AFAICS) to specify a muti-licensed component.

For example, let's look at dtc, the Device Tree Compiler:
 - there are two parts in dtc:
   - libfdt, dual-licensed GPLv2+/BSD-2c
   - dtc (and accompanying tools), licensed GPLv2+

If we only install the library, should we write:
  DTC_LICENSE = GPLv2+/BSD-2c    # notice this is a single word
or
  DTC_LICENSE = GPLv2+ BSD-2c    # notice the space-separation

Then, now we also install the programs, should we write:
  DTC_LICENSE = GPLv2+/BSD-2c GPLv2+
or
  DTC_LICENSE = GPLv2+ BSD-2c

Then, reviewing the licensing information, the user may conclude (wrongly)
that dtc (the package) is dual-licensed GPLv2+ and BSD-2c, and thus decide
to choose the BSD-2c, and not redistribute the dtc package. This would be
bad (TM) in case the dtc programs are installed.

Unfortunately, we have no way to express this kind of multi-licensing cases.
Not that we would want to handle all possibilities either (it would be such
a nightmare), we should at least have a way to draw the user's attention
to such cases.

Here are a few ideas I write as I think of them:

 - add a keyword which genarates a warning:
    DTC_LICENSE = GPLv2+/BDS2- GPLv2+ WARNING

 - allow multi-licensing constructs:
    DTC_LICENSE = GPLV2+/BSD-2c GPLv2+
   (which would say: one part is dual-licensed GPLv2+/BSD-2c, another
   part is licensed GPLv2+)

 - add multi-license keywords:
    DTC_LICENSE += multi:GPLV2+/BSD-2c GPLv2+
   or to be pedantic:
    DTC_LICENSE += multi:GPLV2+/BSD-2c single:GPLv2+

 - don't care. ;-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

^ permalink raw reply

* [Buildroot] post-buil script in chrooted
From: David Bonnin @ 2012-10-26 20:56 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <507F15D3.2080805@mind.be>

Hello,

Exactly, i want to create few users on the target, and copy files for 
each user, like ftpUser , httpdUser, userMyApp, userMyBackupApp.
I doesn't want to copy files only for root.

My apps(2) on the target doesn't run under root privileveges, and have 
theirs own default files/directory.

Now, i understand BR, i did it statically, with copy files by post-build 
script and permissions target in customize package ( deprecated).
My next step, will be put the default directory/files in root folder, 
and at target board starting create/copy files for my users, in goal to 
remove customize package and my own Skeleton.

Thinking of starting, It seemed implicit that we can execute a personnal 
script in a fakeroot script for modify the target dir before make images.

My project works  now, and looking back BR is a good choice(better than 
TI-SDK, and easy to understand).

Le 17/10/2012 22:32, Arnout Vandecappelle a ?crit :
> On 16/10/12 00:03, David Bonnin wrote:
>> Hello,
>>
>> yes, sorry , i mean , i was looking for a post-build script for my 
>> board in a fakeroot environnement.
>> customize package is deprecated.
>>
>> in board/me/Myproject/rootfs-adds/root/
>>
>> i want to cp files of root user.
>
>  Do you mean, files that are owned by root and are not readable by you?
> That won't be possible.
>
>  Or do you mean, files that should be owned by root in the target?  In 
> that
> case, you can just copy them in the post-build script - buildroot will 
> make
> everything owned by root.
>
>
>> So i need to use custom skeletonfs or use customize package.
>
>  Neither of these will do anything that the post-build script cannot do.
>
>  Regards,
>  Arnout

^ permalink raw reply

* [Buildroot] [PATCH 01/47] package/cURL: fix static link whithopenSSL
From: Yann E. MORIN @ 2012-10-26 20:39 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <7D104BEF3E404707964408D74CCF1F01@JohanW7>

Johan, All,

[Please keep the list in CC, don't reply only to me]

On Friday 26 October 2012 Sagaert Johan wrote:
> Is this fixing the problem I had 6 months ago where the curl binary just
> said :segmentation fault when it was build with openssl support ?

No idea; probably not. This fixes a build-time issue.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

^ permalink raw reply

* [Buildroot] [Bug 5630] New: makefile error with toolchain helpers.mk
From: bugzilla at busybox.net @ 2012-10-26 19:23 UTC (permalink / raw)
  To: buildroot

https://bugs.busybox.net/show_bug.cgi?id=5630

           Summary: makefile error with toolchain helpers.mk
           Product: buildroot
           Version: 2012.08
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: gunslnger_ at hotmail.com
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


There are a couple errors in toolchain/helpers.mk in the check_glibc function. 
First, the strip $1 appears to remove everything, not just the trailing '/'. 
Second, the test command has a typo; it references SYSDROOT_DIR instead of
SYSROOT_DIR.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

^ permalink raw reply

* [Buildroot] [PATCH 05/47] package/usbredir: new package
From: Yann E. MORIN @ 2012-10-26 17:39 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <5089B76F.8070003@mind.be>

Arnout, All,

On Friday 26 October 2012 Arnout Vandecappelle wrote:
> On 24/10/12 23:25, Yann E. MORIN wrote:
> [snip]
> > +USBREDIR_VERSION         = 0.4.3
> > +USBREDIR_SOURCE          = usbredir-$(USBREDIR_VERSION).tar.bz2
> > +USBREDIR_SITE            =http://spice-space.org/download/usbredir
> > +USBREDIR_LICENSE         = LGPLv2.1+
> > +USBREDIR_LICENSE_FILES   = COPYING.LIB
> > +USBREDIR_INSTALL_STAGING = YES
> > +USBREDIR_DEPENDENCIES    = libusb
> > +
> > +USBREDIR_DEPENDENCIES    += host-pkg-config
> > +
> > +ifeq ($(BR2_PACKAGE_USBREDIR_SERVER),y)
> > +
> > +USBREDIR_LICENSE         += GPLv2+
> > +USBREDIR_LICENSE_FILES   += COPYING
> 
>   Nice!
> 
> > +
> > +else # BR2_PACKAGE_USBREDIR_SERVER != y
> > +
> > +# It's much easier to remove unwanted files after-the-fact, rather than trying
> > +# to install only what we want. Sad-and-dull life, but life nonetheless...
> > +# Note: do not forget to update the license, above, if you keep the server.
> 
>   It's not the first time this is done in buildroot, so: comment is redundant.

OK. The last sentence is wrong, too, as it's properly taken care of a few
lines above.

BTW, this series was just a kind of "drop the stuff onto the wall and see
what happens", after requests on the IRC chan. It was not meant for
inclusion. But getting early review is very nice! Thank you!

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

^ permalink raw reply

* [Buildroot] [PATCH 02/47] package/libfdt: new package
From: Yann E. MORIN @ 2012-10-26 17:36 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <5089B564.4090500@mind.be>

Arnout, All,

On Thursday 25 October 2012 Arnout Vandecappelle wrote:
>   The package is called dtc, not libfdt.

Gah... Yes.

> On 24/10/12 23:25, Yann E. MORIN wrote:
> > libfdt allows one to manipulate a Flat Device Tree.
> 
>   Flattened Device Tree

Yep.

[--SNIP--]
> > diff --git a/package/Config.in b/package/Config.in
> > index 1650c71..c9cb3ed 100644
> > --- a/package/Config.in
> > +++ b/package/Config.in
> > @@ -396,6 +396,7 @@ source "package/libaio/Config.in"
> >   source "package/libraw1394/Config.in"
> >   source "package/tslib/Config.in"
> >   source "package/libfreefare/Config.in"
> > +source "package/dtc/Config.in"
> 
>   Alphabetical order.

Yep.

>   Also, even if for now it only installs libftd, I guess it shouldn't be
> a problem to install dtc as well.  In that case it fits more in
> Development tools or Hardware handling.

"Hardware handling" sounds like the proper place, IMHO.

> >   source "package/libftdi/Config.in"
> >   source "package/libhid/Config.in"
> >   source "package/libiqrf/Config.in"
> > diff --git a/package/dtc/Config.in b/package/dtc/Config.in
> > new file mode 100644
> > index 0000000..7b86c60
> > --- /dev/null
> > +++ b/package/dtc/Config.in
> > @@ -0,0 +1,9 @@
> > +config BR2_PACKAGE_DTC
> > +	bool "dtc"
> > +	help
> > +	  dtc is the Device Tree Compiler, to generate Device Trees.
> 
>   dtc generates Flattened Device Trees (i.e. it flattens the device
> tree).

From Documentation/manual.txt:

---8<---
The currently supported Input Formats are:
    - "dtb": "blob" format.  A flattened device-tree block with
        header in one binary blob.
    - "dts": "source" format.  A text file containing a "source"
        for a device-tree.
    - "fs" format.  A representation equivalent to the output of
        /proc/device-tree  where nodes are directories and
        properties are files.

The currently supported Output Formats are:
     - "dtb": "blob" format
     - "dts": "source" format
     - "asm": assembly language file.  A file that can be sourced
        by gas to generate a device-tree "blob".  That file can
        then simply be added to your Makefile.  Additionally, the
        assembly file exports some symbols that can be used.
---8<---

So, dtc does not /generate/ flattened, it uses them as _input_.
What about this formulation (also from the same manual.txt) :

    The Device Tree Compiler, dtc, takes as input a device-tree in
    a given format and outputs a device-tree in another format.


> > +	  Note that only the library is installed for now.
>   Why?  Build failures in the binaries?

Because I do not need it in my use-case, so I did not test it, so
I did not install it.

Also, this package could probably also be a host package. This patch
only adds dtc as a target package.

[--SNIP--]
> > ++++ dtc-e4b497f367a3b2ae99cc52089a14a221b13a76ef/Makefile	2012-10-22 22:03:21.151047833 +0200
> > +@@ -18,7 +18,7 @@
> > + CPPFLAGS = -I libfdt -I .
> > + WARNINGS = -Werror -Wall -Wpointer-arith -Wcast-qual -Wnested-externs \
> > + 	-Wstrict-prototypes -Wmissing-prototypes -Wredundant-decls
> > +-CFLAGS = -g -Os -fPIC -Werror $(WARNINGS)
> > ++CFLAGS = -g -Os -fPIC -Werror $(WARNINGS) $(EXTRA_CFLAGS)
> 
>   Why not CFLAGS += ...?
> 
>   And maybe CPPFLAGS should also be fixed.

I'll look again at this.

[--SNIP--]
> > diff --git a/package/dtc/dtc.mk b/package/dtc/dtc.mk
> > new file mode 100644
> > index 0000000..d53e78a
> > --- /dev/null
> > +++ b/package/dtc/dtc.mk
> > @@ -0,0 +1,36 @@
> > +#############################################################
> > +#
> > +# libcurl

dtc, not libcurl. Sigh...

> > +#
> > +#############################################################
> > +
> > +DTC_VERSION         = e4b497f367a3b2ae99cc52089a14a221b13a76ef
> > +DTC_SITE            = git://git.jdl.com/software/dtc.git
> > +DTC_LICENSE         = GPLv2+/BSD-2c
> > +DTC_LICENSE_FILES   = README.license GPL
> > +# Note: the dual-license only applies to the library.
> > +#       The DT compiler (dtc) is GPLv2+, but we do not install it.
> > +DTC_INSTALL_STAGING = YES
> > +
> > +# Need -fPIC for x86-64
>   ???

Probably left-over from debugging?...

> > +define DTC_BUILD_CMDS
> > +	$(TARGET_CONFIGURE_OPTS) $(MAKE1) -C $(@D)                          \
>   Looking at the Makefile, I don't see why parallel builds would fail...

I will investigate again.

> > +	                                  EXTRA_CFLAGS="$(TARGET_CFLAGS)"   \
> > +	                                  PREFIX=/usr                       \
>   It's nicer to put these two options in DTC_MAKE_OPTS.

OK, I'll see to it.

Thanks!

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

^ permalink raw reply

* [Buildroot] [PATCH 01/47] package/cURL: fix static link whith openSSL
From: Yann E. MORIN @ 2012-10-26 17:25 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <5089B0C3.1060005@mind.be>

Arnout, All,

On Thursday 25 October 2012 Arnout Vandecappelle wrote:
> On 24/10/12 23:25, Yann E. MORIN wrote:
> > When openSSL is selected, cURL is configured to use it.
> >
> > But in this case, the libcurl.pc file /forgets/ to require link
> > against -ldl.
> >
> > This can happen, for example, when BR2_PREFER_STATIC_LIB is not set,
> > but an executable wants to be linked statically (for various reasons
> > which are irrelevant here).
> >
> > Fix that by appending a 'Requires: openssl' line to the installed
> > libcurl.pc, if openSSL is enabled.
[--SNIP--]
> > +define LIBCURL_FIX_STAGING_PC
> > +	printf 'Requires: openssl\n'>>$(STAGING_DIR)/usr/lib/pkgconfig/libcurl.pc
> > +endef
> >   LIBCURL_POST_INSTALL_STAGING_HOOKS += LIBCURL_STAGING_FIXUP_CURL_CONFIG
> > +LIBCURL_POST_INSTALL_STAGING_HOOKS += $(if $(BR2_PACKAGE_OPENSSL),LIBCURL_FIX_STAGING_PC)
> 
>   Why not add it to $(@D)/libcurl.pc.in in a post-patch hook?  Then it only has
> to be done once, and I also feel it's a better place to patch things.

Yep, good idea! Thanks!

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

^ permalink raw reply

* [Buildroot] [PATCH v3] lcdapi: new package
From: spdawson at gmail.com @ 2012-10-26 16:32 UTC (permalink / raw)
  To: buildroot

From: Simon Dawson <spdawson@gmail.com>

Signed-off-by: Simon Dawson <spdawson@gmail.com>
---
 v3: Use v0.3 tarball, instead of specific Git commit
 v2: Incorporated changes suggested by Arnout Vandecappelle, use new upstream

 package/Config.in        |    1 +
 package/lcdapi/Config.in |   11 +++++++++++
 package/lcdapi/lcdapi.mk |   41 +++++++++++++++++++++++++++++++++++++++++
 3 files changed, 53 insertions(+)
 create mode 100644 package/lcdapi/Config.in
 create mode 100644 package/lcdapi/lcdapi.mk

diff --git a/package/Config.in b/package/Config.in
index 1650c71..6ebf2ce 100644
--- a/package/Config.in
+++ b/package/Config.in
@@ -392,6 +392,7 @@ endmenu
 
 menu "Hardware handling"
 source "package/ccid/Config.in"
+source "package/lcdapi/Config.in"
 source "package/libaio/Config.in"
 source "package/libraw1394/Config.in"
 source "package/tslib/Config.in"
diff --git a/package/lcdapi/Config.in b/package/lcdapi/Config.in
new file mode 100644
index 0000000..5c997d1
--- /dev/null
+++ b/package/lcdapi/Config.in
@@ -0,0 +1,11 @@
+config BR2_PACKAGE_LCDAPI
+	bool "lcdapi"
+	depends on BR2_INSTALL_LIBSTDCPP
+	depends on BR2_TOOLCHAIN_HAS_THREADS
+	help
+	  C++ client API for lcdproc, containing a set of widget classes.
+
+	  https://github.com/spdawson/lcdapi
+
+comment "lcdapi requires a toolchain with C++ and thread support enabled"
+	depends on !BR2_INSTALL_LIBSTDCPP || !BR2_TOOLCHAIN_HAS_THREADS
diff --git a/package/lcdapi/lcdapi.mk b/package/lcdapi/lcdapi.mk
new file mode 100644
index 0000000..8125018
--- /dev/null
+++ b/package/lcdapi/lcdapi.mk
@@ -0,0 +1,41 @@
+#############################################################
+#
+# lcdapi
+#
+#############################################################
+LCDAPI_VERSION = v0.3
+LCDAPI_SITE = http://github.com/spdawson/lcdapi/tarball/$(LCDAPI_VERSION)
+LCDAPI_LICENSE = LGPLv2.1+
+LCDAPI_LICENSE_FILES = COPYING
+
+LCDAPI_INSTALL_STAGING = YES
+
+define LCDAPI_BUILD_CMDS
+	$(TARGET_MAKE_ENV) $(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D)
+endef
+
+define LCDAPI_INSTALL_STAGING_CMDS
+	$(TARGET_MAKE_ENV) $(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D) \
+		DESTDIR="$(STAGING_DIR)" install
+endef
+
+define LCDAPI_INSTALL_TARGET_CMDS
+	$(TARGET_MAKE_ENV) $(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D) \
+		DESTDIR="$(TARGET_DIR)" install
+endef
+
+define LCDAPI_UNINSTALL_STAGING_CMDS
+	$(TARGET_MAKE_ENV) $(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D) \
+		DESTDIR="$(STAGING_DIR)" uninstall
+endef
+
+define LCDAPI_UNINSTALL_TARGET_CMDS
+	$(TARGET_MAKE_ENV) $(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D) \
+		DESTDIR="$(TARGET_DIR)" uninstall
+endef
+
+define LCDAPI_CLEAN_CMDS
+	$(TARGET_MAKE_ENV) $(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D) clean
+endef
+
+$(eval $(generic-package))
-- 
1.7.10.4

^ permalink raw reply related

* [Buildroot] [PATCH v2] lcdapi: new package
From: Simon Dawson @ 2012-10-26 16:14 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <508A7065.8030304@mind.be>

On 26 October 2012 12:13, Arnout Vandecappelle <arnout@mind.be> wrote:
>  Maybe you can just create a tag?

Yes, okay; I'll do that. Thanks for the advice Arnout.

Simon.

^ permalink raw reply

* [Buildroot] QT application display problem
From: Zoltan Gyarmati @ 2012-10-26 16:00 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <1351266121304-33621.post@n4.nabble.com>

On 10/26/2012 05:42 PM, herve Bourricaud wrote:
> Hi zoltan
>
> yes I'have compiled testapp and QT sample  framebuffer app  myself !
> ( just running the right qMake and then make with the right compiler  :-)
>
> running it I have 3 beautifuls rectangles Red,gree,blue  on my LCD !
> and this output on my console
>
> # ./framebuffer
> The framebuffer device was opened successfully.
>
> Fixed screen info:
>          id:
>          smem_start:  0x23940000
>          smem_len:    261120
>          type:        0
>          type_aux:    0
>          visual:      2
>          xpanstep:    0
>          ypanstep:    1
>          ywrapstep:   0
>          line_length: 960
>          mmio_start:  0x700000
>          mmio_len:    4096
>          accel:       0
>
> The framebuffer device was mapped to memory successfully.
>
> Successfully switched to graphics mode.
>
> Variable screen info:
>          xres:           480
>          yres:           272
>          xres_virtual:   480
>          yres_virtual:   272
>          yoffset:        0
>          xoffset:        0
>          bits_per_pixel: 16
>          grayscale: 0
>          red:    offset:  0, length:  5, msb_right:  0
>          green:  offset:  5, length:  6, msb_right:  0
>          blue:   offset: 11, length:  5, msb_right:  0
>          transp: offset:  0, length:  0, msb_right:  0
>          nonstd:       0
>          activate:     0
>          height:       0
>          width:        0
>          accel_flags:  0x0
>          pixclock:     120816
>          left_margin:  2
>          right_margin: 2
>          upper_margin: 2
>          lower_margin: 2
>          hsync_len:    41
>          vsync_len:    10
>          sync:         3
>          vmode:        0
>
> Frame Buffer Performance test...
>          Average:   6083 usecs
>          Bandwidth: 40.938 MByte/Sec
>          Max. FPS:  164.393 fps
>
> Will draw 3 rectangles on the screen,
> they should be colored red, green and blue (in that order).
>    Done.
> #
>
>
> so I suppose bit per pixels for frame buffer is 16 !
> else how to check the frame buffer configuration ?
>
> in buildroot
>       -> Package Selection for the target
>     ?       -> Graphic libraries and applications (graphic/text)
>     ?         -> Qt (BR2_PACKAGE_QT [=y])
>     ?           -> Gui Module (BR2_PACKAGE_QT_GUI_MODULE [=y])
>     ?             -> Pixel depths  selected    8/15/16
>
> must I only select 16 ?
>
> thanks for your help !
> herv?.
>
>
>
>
>
> --
> View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/QT-application-display-problem-tp33619p33621.html
> Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

Yes, it seems your framebuffer is set to 16 pixel colordepth, so either 
set your framebuffer's color depth to the value you used when compiled 
Qt (you have to modify the kernel boot command line for that in your 
U-Boot config, and this is the place well you can check it as well), or 
set it to 16 in your Qt configuration, and recompile Qt. The first 
solution is quicker ;)

  Otherwise if you check the      examples/qws/framebuffer/main.c file 
in your Qt source tree, then you see, that this test app is checking the 
color depth of the framebuffer, and uses a color palette according to 
the framebuffer's set value. You might want to set up a similar 
mechanism in your code, if you want to use it in different environments.

Good luck

^ permalink raw reply

* [Buildroot] QT application display problem
From: herve Bourricaud @ 2012-10-26 15:42 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <508AA9BF.8000704@gmail.com>

Hi zoltan

yes I'have compiled testapp and QT sample  framebuffer app  myself !
( just running the right qMake and then make with the right compiler  :-)

running it I have 3 beautifuls rectangles Red,gree,blue  on my LCD ! 
and this output on my console 

# ./framebuffer
The framebuffer device was opened successfully.

Fixed screen info:
        id:
        smem_start:  0x23940000
        smem_len:    261120
        type:        0
        type_aux:    0
        visual:      2
        xpanstep:    0
        ypanstep:    1
        ywrapstep:   0
        line_length: 960
        mmio_start:  0x700000
        mmio_len:    4096
        accel:       0

The framebuffer device was mapped to memory successfully.

Successfully switched to graphics mode.

Variable screen info:
        xres:           480
        yres:           272
        xres_virtual:   480
        yres_virtual:   272
        yoffset:        0
        xoffset:        0
        bits_per_pixel: 16
        grayscale: 0
        red:    offset:  0, length:  5, msb_right:  0
        green:  offset:  5, length:  6, msb_right:  0
        blue:   offset: 11, length:  5, msb_right:  0
        transp: offset:  0, length:  0, msb_right:  0
        nonstd:       0
        activate:     0
        height:       0
        width:        0
        accel_flags:  0x0
        pixclock:     120816
        left_margin:  2
        right_margin: 2
        upper_margin: 2
        lower_margin: 2
        hsync_len:    41
        vsync_len:    10
        sync:         3
        vmode:        0

Frame Buffer Performance test...
        Average:   6083 usecs
        Bandwidth: 40.938 MByte/Sec
        Max. FPS:  164.393 fps

Will draw 3 rectangles on the screen,
they should be colored red, green and blue (in that order).
  Done.
#


so I suppose bit per pixels for frame buffer is 16 !
else how to check the frame buffer configuration ?

in buildroot 
     -> Package Selection for the target 
   ?       -> Graphic libraries and applications (graphic/text) 
   ?         -> Qt (BR2_PACKAGE_QT [=y]) 
   ?           -> Gui Module (BR2_PACKAGE_QT_GUI_MODULE [=y]) 
   ?             -> Pixel depths  selected    8/15/16

must I only select 16 ?

thanks for your help !
herv?.





--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/QT-application-display-problem-tp33619p33621.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

^ permalink raw reply

* [Buildroot] [PATCH] efl is now at 1.7.1
From: Evgeni Dobrev @ 2012-10-26 15:41 UTC (permalink / raw)
  To: buildroot

- bumped up revision to 1.7.1
- choose between external and Buildroot built edje_cc and eet when building elemntary
- finer control over building options
---
 package/efl/expedite/expedite.mk           |    2 +-
 package/efl/libecore/libecore.mk           |    2 +-
 package/efl/libedbus/libedbus.mk           |    2 +-
 package/efl/libedje/Config.in              |   60 +++++++++++++++++++++++
 package/efl/libedje/libedje.mk             |   70 ++++++++++++++++++++++++++-
 package/efl/libeet/libeet.mk               |    8 +++-
 package/efl/libefreet/libefreet.mk         |    2 +-
 package/efl/libeina/libeina.mk             |    6 ++-
 package/efl/libelementary/Config.in        |   71 ++++++++++++++++++++++++++++
 package/efl/libelementary/libelementary.mk |   39 +++++++++++++--
 package/efl/libembryo/Config.in            |    7 +++
 package/efl/libembryo/libembryo.mk         |   12 ++++-
 package/efl/libethumb/libethumb.mk         |    4 +-
 package/efl/libevas/libevas.mk             |    4 +-
 14 files changed, 271 insertions(+), 18 deletions(-)

diff --git a/package/efl/expedite/expedite.mk b/package/efl/expedite/expedite.mk
index a841ac9..b58b6ac 100644
--- a/package/efl/expedite/expedite.mk
+++ b/package/efl/expedite/expedite.mk
@@ -4,7 +4,7 @@
 #
 #############################################################
 
-EXPEDITE_VERSION = 1.1.0
+EXPEDITE_VERSION = 1.7.1
 EXPEDITE_SITE = http://download.enlightenment.org/releases/
 EXPEDITE_DEPENDENCIES = libevas libeina libeet
 
diff --git a/package/efl/libecore/libecore.mk b/package/efl/libecore/libecore.mk
index df8db0d..87dcfa3 100644
--- a/package/efl/libecore/libecore.mk
+++ b/package/efl/libecore/libecore.mk
@@ -4,7 +4,7 @@
 #
 #############################################################
 
-LIBECORE_VERSION = 1.1.0
+LIBECORE_VERSION = 1.7.1
 LIBECORE_SOURCE = ecore-$(LIBECORE_VERSION).tar.bz2
 LIBECORE_SITE = http://download.enlightenment.org/releases/
 LIBECORE_INSTALL_STAGING = YES
diff --git a/package/efl/libedbus/libedbus.mk b/package/efl/libedbus/libedbus.mk
index 04c48a4..43e3536 100644
--- a/package/efl/libedbus/libedbus.mk
+++ b/package/efl/libedbus/libedbus.mk
@@ -4,7 +4,7 @@
 #
 #############################################################
 
-LIBEDBUS_VERSION = 1.1.0
+LIBEDBUS_VERSION = 1.7.1
 LIBEDBUS_SOURCE = e_dbus-$(LIBEDBUS_VERSION).tar.bz2
 LIBEDBUS_SITE = http://download.enlightenment.org/releases/
 LIBEDBUS_INSTALL_STAGING = YES
diff --git a/package/efl/libedje/Config.in b/package/efl/libedje/Config.in
index f0985dd..0c6d2a9 100644
--- a/package/efl/libedje/Config.in
+++ b/package/efl/libedje/Config.in
@@ -19,3 +19,63 @@ config BR2_PACKAGE_LIBEDJE_CC
 	help
 	  Build and install the Edje compiler for the target. Normally this
 	  is not required.
+
+config BR2_PACKAGE_LIBEDJE_DECC
+	bool "build edje_decc"
+	depends on BR2_PACKAGE_LIBEDJE
+	help
+	  Build and install the Edje decompiler for the target. Normally this
+	  is not required.
+
+config BR2_PACKAGE_LIBEDJE_RECC
+	bool "build edje_recc"
+	depends on BR2_PACKAGE_LIBEDJE
+	help
+	  Build and install the Edje recompiler for the target. Normally this
+	  is not required.
+
+config BR2_PACKAGE_LIBEDJE_PLAYER
+	bool "build edje_player"
+	depends on BR2_PACKAGE_LIBEDJE
+	help
+	  Build and install the Edje player for the target. Normally this
+	  is not required.
+
+config BR2_PACKAGE_LIBEDJE_INSPECTOR
+	bool "build edje_inspector"
+	depends on BR2_PACKAGE_LIBEDJE
+	help
+	  Build and install the Edje inspector for the target. Normally this
+	  is not required.
+
+config BR2_PACKAGE_LIBEDJE_EXTERNAL_INSPECTOR
+	bool "build edje_external_inspector"
+	depends on BR2_PACKAGE_LIBEDJE
+	help
+	  Build and install the Edje external inspector for the target. Normally this
+	  is not required.
+
+config BR2_PACKAGE_LIBEDJE_WATCH
+	bool "build edje_watch"
+	depends on BR2_PACKAGE_LIBEDJE
+	help
+	  Build and install edje_watch  for the target. Normally this
+	  is not required.
+
+config BR2_PACKAGE_LIBEDJE_PROGRAM_CACHE
+	bool "edje program cache"
+	depends on BR2_PACKAGE_LIBEDJE
+	help
+	  Enable EDJE_PROGRAM_CACHE support.
+
+config BR2_PACKAGE_LIBEDJE_CALC_CACHE
+	bool "edje calc cache"
+	depends on BR2_PACKAGE_LIBEDJE
+	help
+	  Enable EDJE_CALC_CACHE support.
+
+config BR2_PACKAGE_LIBEDJE_FIXED_POINT
+	bool "edje code fixed point"
+	depends on BR2_PACKAGE_LIBEDJE
+	help
+	  Reduce use of FPU by using Fixed Point provided by Eina and Eet.
diff --git a/package/efl/libedje/libedje.mk b/package/efl/libedje/libedje.mk
index e6d9ab3..0bf80ee 100644
--- a/package/efl/libedje/libedje.mk
+++ b/package/efl/libedje/libedje.mk
@@ -4,7 +4,7 @@
 #
 #############################################################
 
-LIBEDJE_VERSION = 1.1.0
+LIBEDJE_VERSION = 1.7.1
 LIBEDJE_SOURCE = edje-$(LIBEDJE_VERSION).tar.bz2
 LIBEDJE_SITE =  http://download.enlightenment.org/releases/
 LIBEDJE_INSTALL_STAGING = YES
@@ -12,13 +12,79 @@ LIBEDJE_INSTALL_STAGING = YES
 LIBEDJE_DEPENDENCIES = host-pkg-config lua libeina libeet libecore libevas \
 			libembryo
 
+LIBEDJE_CONF_OPT += \
+		    --disable-install-examples \
+		    --disable-multisense \
+		    --disable-sndfile \
+		    --disable-remix \
+		    --disable-vorbis \
+		    --disable-alsa \
+		    --disable-flac \
+		    --disable-tests
+
 ifeq ($(BR2_PACKAGE_LIBEDJE_CC),y)
 LIBEDJE_CONF_OPT += --enable-edje-cc
 else
 LIBEDJE_CONF_OPT += --disable-edje-cc
 endif
 
-HOST_LIBEDJE_CONF_OPT = --enable-edje-cc
+ifeq ($(BR2_PACKAGE_LIBEDJE_DECC),y)
+LIBEDJE_CONF_OPT += --enable-edje-decc
+else
+LIBEDJE_CONF_OPT += --disable-edje-decc
+endif
+
+ifeq ($(BR2_PACKAGE_LIBEDJE_RECC),y)
+LIBEDJE_CONF_OPT += --enable-edje-recc
+else
+LIBEDJE_CONF_OPT += --disable-edje-recc
+endif
+
+ifeq ($(BR2_PACKAGE_LIBEDJE_PLAYER),y)
+LIBEDJE_CONF_OPT += --enable-edje-player
+else
+LIBEDJE_CONF_OPT += --disable-edje-player
+endif
+
+ifeq ($(BR2_PACKAGE_LIBEDJE_INSPECTOR),y)
+LIBEDJE_CONF_OPT += --enable-edje-inspector
+else
+LIBEDJE_CONF_OPT += --disable-edje-inspector
+endif
+
+ifeq ($(BR2_PACKAGE_LIBEDJE_EXTERNAL_INSPECTOR),y)
+LIBEDJE_CONF_OPT += --enable-edje-external-inspector
+else
+LIBEDJE_CONF_OPT += --disable-edje-external-inspector
+endif
+
+ifeq ($(BR2_PACKAGE_LIBEDJE_WATCH),y)
+LIBEDJE_CONF_OPT += --enable-edje-watch
+else
+LIBEDJE_CONF_OPT += --disable-edje-watch
+endif
+
+ifeq ($(BR2_PACKAGE_LIBEDJE_PROGRAM_CACHE),y)
+LIBEDJE_CONF_OPT += --enable-edje-program-cache
+else
+LIBEDJE_CONF_OPT += --disable-edje-program-cache
+endif
+
+ifeq ($(BR2_PACKAGE_LIBEDJE_CALC_CACHE),y)
+LIBEDJE_CONF_OPT += --enable-edje-calc-cache
+else
+LIBEDJE_CONF_OPT += --disable-edje-calc-cache
+endif
+
+ifeq ($(BR2_PACKAGE_LIBEDJE_FIXED_POINT),y)
+LIBEDJE_CONF_OPT += --enable-fixed-point
+else
+LIBEDJE_CONF_OPT += --disable-fixed-point
+endif
+
+ifneq ($(BR2_HAVE_DOCUMENTATION),y)
+LIBEDJE_CONF_OPT += --disable-doc
+endif
 
 $(eval $(autotools-package))
 $(eval $(host-autotools-package))
diff --git a/package/efl/libeet/libeet.mk b/package/efl/libeet/libeet.mk
index 3ca12d3..72cf7f8 100644
--- a/package/efl/libeet/libeet.mk
+++ b/package/efl/libeet/libeet.mk
@@ -4,12 +4,18 @@
 #
 #############################################################
 
-LIBEET_VERSION = 1.5.0
+LIBEET_VERSION = 1.7.1
 LIBEET_SOURCE = eet-$(LIBEET_VERSION).tar.bz2
 LIBEET_SITE = http://download.enlightenment.org/releases/
 LIBEET_INSTALL_STAGING = YES
 
 LIBEET_DEPENDENCIES = host-pkg-config zlib jpeg libeina
 
+LIBEEET_CONF_OPT += --disable-install-examples 
+
+ifneq ($(BR2_HAVE_DOCUMENTATION),y)
+LIBEET_CONF_OPT += --disable-doc
+endif
+
 $(eval $(autotools-package))
 $(eval $(host-autotools-package))
diff --git a/package/efl/libefreet/libefreet.mk b/package/efl/libefreet/libefreet.mk
index 2f00bcf..c6762fd 100644
--- a/package/efl/libefreet/libefreet.mk
+++ b/package/efl/libefreet/libefreet.mk
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-LIBEFREET_VERSION = 1.1.0
+LIBEFREET_VERSION = 1.7.1
 LIBEFREET_SOURCE = efreet-$(LIBEFREET_VERSION).tar.bz2
 LIBEFREET_SITE = http://download.enlightenment.org/releases/
 LIBEFREET_INSTALL_STAGING = YES
diff --git a/package/efl/libeina/libeina.mk b/package/efl/libeina/libeina.mk
index 2391379..8aaada9 100644
--- a/package/efl/libeina/libeina.mk
+++ b/package/efl/libeina/libeina.mk
@@ -4,12 +4,16 @@
 #
 #############################################################
 
-LIBEINA_VERSION = 1.1.0
+LIBEINA_VERSION = 1.7.1
 LIBEINA_SOURCE = eina-$(LIBEINA_VERSION).tar.bz2
 LIBEINA_SITE = http://download.enlightenment.org/releases/
 LIBEINA_INSTALL_STAGING = YES
 
 LIBEINA_DEPENDENCIES = host-pkg-config
 
+ifneq ($(BR2_HAVE_DOCUMENTATION),y)
+LIBEINA_CONF_OPT += --disable-doc
+endif
+
 $(eval $(autotools-package))
 $(eval $(host-autotools-package))
diff --git a/package/efl/libelementary/Config.in b/package/efl/libelementary/Config.in
index 59af80e..13d03dc 100644
--- a/package/efl/libelementary/Config.in
+++ b/package/efl/libelementary/Config.in
@@ -10,3 +10,74 @@ config BR2_PACKAGE_LIBELEMENTARY
 	  with less code.
 
 	  http://trac.enlightenment.org/e/wiki/Elementary
+
+choice
+	prompt "edje_cc type"
+	default BR2_PACKAGE_LIBELEMENTARY_EDJE_CC_BUILDROOT
+	depends on BR2_PACKAGE_LIBELEMENTARY
+
+config BR2_PACKAGE_LIBELEMENTARY_EDJE_CC_BUILDROOT
+	bool "Buildroot built"
+	select BR2_PACKAGE_LIBEDJE_CC
+	help
+	  Select this option if you want Buildroot to build edje_cc on your host.
+
+config BR2_PACKAGE_LIBELEMENTARY_EDJE_CC_PREINSTALLED
+	bool "Pre-installed"
+	help
+	  Select this option if you want to use a pre-installed edje_cc
+	  Specify the path to edje_cc in BR2_PACKAGE_LIBELEMENTARY_EDJE_CC_PATH
+
+endchoice 
+
+config BR2_PACKAGE_LIBELEMENTARY_EDJE_CC_PATH
+	string "edje_cc path"
+	default "/path/to/edje_cc"
+	depends on BR2_PACKAGE_LIBELEMENTARY_EDJE_CC_PREINSTALLED
+	help
+	  Path to an externally provided edje_cc
+
+choice
+	prompt "eet type"
+	default BR2_PACKAGE_LIBELEMENTARY_EET_BUILDROOT
+	depends on BR2_PACKAGE_LIBELEMENTARY
+
+config BR2_PACKAGE_LIBELEMENTARY_EET_BUILDROOT
+	bool "Buildroot built"
+	help
+	  Select this option if you want Buildroot to build eet on your host.
+
+config BR2_PACKAGE_LIBELEMENTARY_EET_PREINSTALLED
+	bool "Pre-installed"
+	help
+	  Select this option if you want to use a pre-installed eer.
+	  Specify the path to eet in BR2_PACKAGE_LIBELEMENTARY_EET_PATH
+
+endchoice 
+
+config BR2_PACKAGE_LIBELEMENTARY_EET_PATH
+	string "eet path"
+	default "/path/to/eet"
+	depends on BR2_PACKAGE_LIBELEMENTARY_EET_PREINSTALLED
+	help
+	  Path to an externally provided eet
+
+config BR2_PACKAGE_LIBELEMENTARY_TEST
+	bool "build elementary_test"
+	depends on BR2_PACKAGE_LIBELEMENTARY
+	help
+	  Build and install elementary_test for the target. Normally this
+	  is not required.
+
+config BR2_PACKAGE_LIBELEMENTARY_CONFIG
+	bool "build elementary_config"
+	depends on BR2_PACKAGE_LIBELEMENTARY
+	help
+	  Build and install elementary_config for the target. Normally this
+	  is not required.
+
+config BR2_PACKAGE_LIBELEMENTARY_QUICK_LAUNCH
+	bool "enable quick-launch support"
+	depends on BR2_PACKAGE_LIBELEMENTARY
+	help
+	  Enable quick-launch support.
diff --git a/package/efl/libelementary/libelementary.mk b/package/efl/libelementary/libelementary.mk
index 83c9005..18319d1 100644
--- a/package/efl/libelementary/libelementary.mk
+++ b/package/efl/libelementary/libelementary.mk
@@ -4,15 +4,42 @@
 #
 ################################################################################
 
-LIBELEMENTARY_VERSION = 0.8.0.65643
+LIBELEMENTARY_VERSION = 1.7.1
 LIBELEMENTARY_SOURCE = elementary-$(LIBELEMENTARY_VERSION).tar.bz2
-LIBELEMENTARY_SITE = http://download.enlightenment.org/snapshots/2011-11-28
+LIBELEMENTARY_SITE = http://download.enlightenment.org/releases/
 LIBELEMENTARY_INSTALL_STAGING = YES
 
-LIBELEMENTARY_DEPENDENCIES = libeina libevas libecore libedje host-libedje \
-				host-libeet
+LIBELEMENTARY_DEPENDENCIES = libeina libevas libecore libedje 
 
-LIBELEMENTARY_CONF_OPT = --with-edje-cc=$(HOST_DIR)/usr/bin/edje_cc \
-			 --with-eet-eet=$(HOST_DIR)/usr/bin/eet
+ifneq ($(BR2_PACKAGE_LIBELEMENTARY_TEST),y)
+LIBELEMENTARY_CONF_OPT += --disable-elementary-test
+endif
+
+ifneq ($(BR2_PACKAGE_LIBELEMENTARY_CONFIG),y)
+LIBELEMENTARY_CONF_OPT += --disable-elementary-config
+endif
+
+ifneq ($(BR2_PACKAGE_LIBELEMENTARY_QUICK_LAUNCH),y)
+LIBELEMENTARY_CONF_OPT += --disable-quick-launch
+endif
+
+ifeq ($(BR2_PACKAGE_LIBELEMENTARY_EDJE_CC_PREINSTALLED),y)
+LIBELEMENTARY_CONF_OPT += --with-edje-cc=$(BR2_PACKAGE_LIBELEMENTARY_EDJE_CC_PATH)
+else
+LIBELEMENTARY_DEPENDENCIES += host-libedje
+LIBELEMENTARY_CONF_OPT += --with-edje-cc=$(HOST_DIR)/usr/bin/edje_cc
+endif
+
+ifeq ($(BR2_PACKAGE_LIBELEMENTARY_EET_PREINSTALLED),y)
+LIBELEMENTARY_CONF_OPT += --with-eet-eet=$(BR2_PACKAGE_LIBELEMENTARY_EET_PATH)
+else
+LIBELEMENTARY_DEPENDENCIES += host-libeet
+LIBELEMENTARY_CONF_OPT += --with-eet-eet=$(HOST_DIR)/usr/bin/eet
+endif
+
+
+ifneq ($(BR2_HAVE_DOCUMENTATION),y)
+LIBELEMENTARY_CONF_OPT += --disable-doc
+endif
 
 $(eval $(autotools-package))
diff --git a/package/efl/libembryo/Config.in b/package/efl/libembryo/Config.in
index 63c7064..ee6313d 100644
--- a/package/efl/libembryo/Config.in
+++ b/package/efl/libembryo/Config.in
@@ -7,3 +7,10 @@ config BR2_PACKAGE_LIBEMBRYO
 	  abstract machine bytecode that it understands.
 
 	  http://trac.enlightenment.org/e/wiki/Embryo
+
+config BR2_PACKAGE_LIBEMBRYO_CC
+	bool "build embryo_cc"
+	depends on BR2_PACKAGE_LIBEMBRYO
+	help
+	  Build and install the embryo compiler for the target. Normally this
+	  is not required.
diff --git a/package/efl/libembryo/libembryo.mk b/package/efl/libembryo/libembryo.mk
index db1696d..6b92b24 100644
--- a/package/efl/libembryo/libembryo.mk
+++ b/package/efl/libembryo/libembryo.mk
@@ -4,12 +4,22 @@
 #
 #############################################################
 
-LIBEMBRYO_VERSION = 1.1.0
+LIBEMBRYO_VERSION = 1.7.1
 LIBEMBRYO_SOURCE = embryo-$(LIBEMBRYO_VERSION).tar.bz2
 LIBEMBRYO_SITE = http://download.enlightenment.org/releases/
 LIBEMBRYO_INSTALL_STAGING = YES
 
 LIBEMBRYO_DEPENDENCIES = host-pkg-config libeina
 
+ifeq ($(BR2_PACKAGE_LIBEMBRYO_CC),y)
+LIBEMBRYO_CONF_OPT += --enable-embryo-cc
+else
+LIBEMBRYO_CONF_OPT += --disable-embryo-cc
+endif
+
+ifneq ($(BR2_HAVE_DOCUMENTATION),y)
+LIBEMBRYO_CONF_OPT += --disable-doc
+endif
+
 $(eval $(autotools-package))
 $(eval $(host-autotools-package))
diff --git a/package/efl/libethumb/libethumb.mk b/package/efl/libethumb/libethumb.mk
index 92e4c83..9b7ee1d 100644
--- a/package/efl/libethumb/libethumb.mk
+++ b/package/efl/libethumb/libethumb.mk
@@ -4,9 +4,9 @@
 #
 ################################################################################
 
-LIBETHUMB_VERSION = 0.1.1.65643
+LIBETHUMB_VERSION = 1.7.1
 LIBETHUMB_SOURCE = ethumb-$(LIBETHUMB_VERSION).tar.bz2
-LIBETHUMB_SITE = http://download.enlightenment.org/snapshots/2011-11-28
+LIBETHUMB_SITE = http://download.enlightenment.org/releases/
 LIBETHUMB_INSTALL_STAGING = YES
 
 LIBETHUMB_DEPENDENCIES = libeina libevas libecore libedje host-libedje
diff --git a/package/efl/libevas/libevas.mk b/package/efl/libevas/libevas.mk
index 3baf23b..3b2263e 100644
--- a/package/efl/libevas/libevas.mk
+++ b/package/efl/libevas/libevas.mk
@@ -4,7 +4,7 @@
 #
 #############################################################
 
-LIBEVAS_VERSION = 1.1.0
+LIBEVAS_VERSION = 1.7.1
 LIBEVAS_SOURCE = evas-$(LIBEVAS_VERSION).tar.bz2
 LIBEVAS_SITE = http://download.enlightenment.org/releases/
 LIBEVAS_INSTALL_STAGING = YES
@@ -28,6 +28,8 @@ HOST_LIBEVAS_CONF_OPT += \
 	--enable-software-xcb \
 	--disable-gl-xcb
 
+LIBEVAS_CONF_OPT += --disable-build-examples 
+
 # rendering options
 ifeq ($(BR2_PACKAGE_LIBEVAS_SCALE_SAMPLE),y)
 LIBEVAS_CONF_OPT += --enable-scale-sample
-- 
1.7.2.5

^ permalink raw reply related

* [Buildroot] QT application display problem
From: Zoltan Gyarmati @ 2012-10-26 15:18 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <1351263719950-33619.post@n4.nabble.com>

On 10/26/2012 05:01 PM, herve Bourricaud wrote:
> Hello,
>
> I'am an electronician , trying to use linux ;-)
> I'am almost new to buildroot and linux...
>
> So please tell me if here is not the right place for this kind of questions.
>
> I'am trying to port a QT application to a new board using an AT91SAM9263
> I use buildroot to generate toolchain (GCC 4.6.3 + uclibc) and rootfs
> I prefer generate AT91loader/U-BOOT/kernel directly in each git tree using
> the same compiler !
>
> attach to this board there is 4.3 inch LCD
> I test frame buffer using QT framebuffer test application or fb-test-app
> (https://github.com/prpplague/fb-test-app)
> and it's work OK
>
> THe problem is whith my QT application
> the colors displayed  are really bad !
> and text 'contour' is really not clear like if another color was around text
> (sorry for my english here ;-)
>
> the only thing I've seen are warnings when compiling QT
> something like "invalid cast, use -Wcast-align "
>
> any advice is welcome !
>   herv?.
>
>
>
>
> --
> View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/QT-application-display-problem-tp33619.html
> Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
Hi Herv?,

probably you have some misconfiguration with the color depth of you 
framebuffer, and in your qt config. You can check your framebuffer 
settings probably at the kernel boot command line, and you can check the 
QT color depth setting in the
Location:
   ?     -> Package Selection for the target
   ?       -> Graphic libraries and applications (graphic/text)
   ?         -> Qt (BR2_PACKAGE_QT [=y])
   ?           -> Gui Module (BR2_PACKAGE_QT_GUI_MODULE [=y])
   ?             -> Pixel depths

in your Buildroot menuconfig. Otherwise it's strange it's good with the 
testapp. Did you compiled this framebuffer test app yourself?

^ permalink raw reply

* [Buildroot] QT application display problem
From: herve Bourricaud @ 2012-10-26 15:01 UTC (permalink / raw)
  To: buildroot

Hello,

I'am an electronician , trying to use linux ;-)
I'am almost new to buildroot and linux...

So please tell me if here is not the right place for this kind of questions.

I'am trying to port a QT application to a new board using an AT91SAM9263
I use buildroot to generate toolchain (GCC 4.6.3 + uclibc) and rootfs
I prefer generate AT91loader/U-BOOT/kernel directly in each git tree using
the same compiler !

attach to this board there is 4.3 inch LCD 
I test frame buffer using QT framebuffer test application or fb-test-app
(https://github.com/prpplague/fb-test-app)
and it's work OK

THe problem is whith my QT application
the colors displayed  are really bad !
and text 'contour' is really not clear like if another color was around text
(sorry for my english here ;-)

the only thing I've seen are warnings when compiling QT
something like "invalid cast, use -Wcast-align "

any advice is welcome !
 herv?.




--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/QT-application-display-problem-tp33619.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

^ permalink raw reply

* [Buildroot] [PATCH 1/1] toolchain/uClibc: correct a slip of the pen
From: Peter Korsgaard @ 2012-10-26 11:24 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <1351153843-16204-1-git-send-email-xinglong.liao@gmail.com>

>>>>> "Xinglong" == Xinglong Liao <xinglong.liao@gmail.com> writes:

 Xinglong> UCLIB_EXTRA_CFLAGS -> UCLIBC_EXTRA_CFLAGS
 Xinglong> Signed-off-by: Xinglong Liao <xinglong.liao@gmail.com>

Committed, thanks.

-- 
Bye, Peter Korsgaard

^ permalink raw reply

* [Buildroot] [git commit] toolchain/uClibc: correct a slip of the pen
From: Peter Korsgaard @ 2012-10-26 11:23 UTC (permalink / raw)
  To: buildroot

commit: http://git.buildroot.net/buildroot/commit/?id=d3e7759f85ab07680c7ba412b0c84d0e300fc4bf
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

UCLIB_EXTRA_CFLAGS -> UCLIBC_EXTRA_CFLAGS

Signed-off-by: Xinglong Liao <xinglong.liao@gmail.com>
Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
 toolchain/uClibc/uclibc.mk |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/toolchain/uClibc/uclibc.mk b/toolchain/uClibc/uclibc.mk
index d1cd718..397cdd4 100644
--- a/toolchain/uClibc/uclibc.mk
+++ b/toolchain/uClibc/uclibc.mk
@@ -379,7 +379,7 @@ $(UCLIBC_DIR)/.config: $(UCLIBC_DIR)/.oldconfig
 		DEVEL_PREFIX=/usr/ \
 		RUNTIME_PREFIX=$(TOOLCHAIN_DIR)/uClibc_dev/ \
 		CROSS_COMPILE="$(TARGET_CROSS)" \
-		UCLIB_EXTRA_CFLAGS="$(TARGET_ABI)" \
+		UCLIBC_EXTRA_CFLAGS="$(TARGET_ABI)" \
 		HOSTCC="$(HOSTCC)" \
 		oldconfig
 	touch $@
@@ -398,7 +398,7 @@ $(UCLIBC_DIR)/.configured: $(LINUX_HEADERS_DIR)/.configured $(UCLIBC_DIR)/.confi
 		DEVEL_PREFIX=/usr/ \
 		RUNTIME_PREFIX=$(TOOLCHAIN_DIR)/uClibc_dev/ \
 		CROSS_COMPILE="$(TARGET_CROSS)" \
-		UCLIB_EXTRA_CFLAGS="$(TARGET_ABI)" \
+		UCLIBC_EXTRA_CFLAGS="$(TARGET_ABI)" \
 		HOSTCC="$(HOSTCC)" headers \
 		lib/crt1.o lib/crti.o lib/crtn.o \
 		install_headers
@@ -420,7 +420,7 @@ $(UCLIBC_DIR)/lib/libc.a: $(UCLIBC_DIR)/.configured $(gcc_intermediate) $(LIBFLO
 		DEVEL_PREFIX=/ \
 		RUNTIME_PREFIX=/ \
 		CROSS_COMPILE="$(TARGET_CROSS)" \
-		UCLIB_EXTRA_CFLAGS="$(TARGET_ABI)" \
+		UCLIBC_EXTRA_CFLAGS="$(TARGET_ABI)" \
 		HOSTCC="$(HOSTCC)" \
 		all
 	touch -c $@
@@ -432,7 +432,7 @@ uclibc-menuconfig: dirs $(UCLIBC_DIR)/.config
 		DEVEL_PREFIX=/usr/ \
 		RUNTIME_PREFIX=$(TOOLCHAIN_DIR)/uClibc_dev/ \
 		CROSS_COMPILE="$(TARGET_CROSS)" \
-		UCLIB_EXTRA_CFLAGS="$(TARGET_ABI)" \
+		UCLIBC_EXTRA_CFLAGS="$(TARGET_ABI)" \
 		HOSTCC="$(HOSTCC)" \
 		menuconfig && \
 	touch -c $(UCLIBC_DIR)/.config
@@ -445,7 +445,7 @@ $(STAGING_DIR)/usr/lib/libc.a: $(UCLIBC_DIR)/lib/libc.a
 		DEVEL_PREFIX=/usr/ \
 		RUNTIME_PREFIX=/ \
 		CROSS_COMPILE="$(TARGET_CROSS)" \
-		UCLIB_EXTRA_CFLAGS="$(TARGET_ABI)" \
+		UCLIBC_EXTRA_CFLAGS="$(TARGET_ABI)" \
 		install_runtime install_dev
 	# Install the kernel headers to the staging dir if necessary
 	if [ ! -f $(STAGING_DIR)/usr/include/linux/version.h ]; then \
@@ -475,7 +475,7 @@ $(TARGET_DIR)/lib/libc.so.0: $(STAGING_DIR)/usr/lib/libc.a
 		DEVEL_PREFIX=/usr/ \
 		RUNTIME_PREFIX=/ \
 		CROSS_COMPILE="$(TARGET_CROSS)" \
-		UCLIB_EXTRA_CFLAGS="$(TARGET_ABI)" \
+		UCLIBC_EXTRA_CFLAGS="$(TARGET_ABI)" \
 		install_runtime
 	touch -c $@
 

^ permalink raw reply related

* [Buildroot] [PATCH v2] lcdapi: new package
From: Arnout Vandecappelle @ 2012-10-26 11:13 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <1351166671-16726-1-git-send-email-spdawson@gmail.com>

On 25/10/12 14:04, spdawson at gmail.com wrote:
> From: Simon Dawson<spdawson@gmail.com>
>
> Signed-off-by: Simon Dawson<spdawson@gmail.com>
[snip]
> diff --git a/package/lcdapi/lcdapi.mk b/package/lcdapi/lcdapi.mk
> new file mode 100644
> index 0000000..3b5aaa3
> --- /dev/null
> +++ b/package/lcdapi/lcdapi.mk
> @@ -0,0 +1,41 @@
> +#############################################################
> +#
> +# lcdapi
> +#
> +#############################################################
> +LCDAPI_VERSION = 27e16c37a39c7fab2cf2e912795a730c0e92bcf1
> +LCDAPI_SITE = git://github.com/spdawson/lcdapi.git

  From docs/manual/manual.txt:

How to add package from github
------------------------------

If the package has no release version, or its version cannot be
identified using tag, then the sha1 of the particular commit should be
used to identify the version (the first 7 characters of the sha1 are
enough):

------------------------
FOO_VERSION = 1234567
FOO_SITE = http://github.com/<user>/<package>/tarball/<branch>
------------------------

If the package version matches a tag, then this tag should be used to
identify the version:

------------------------
FOO_VERSION = v1.0
FOO_SITE = http://github.com/<user>/<package>/tarball/$(FOO_VERSION)
------------------------


  Maybe you can just create a tag?

  Regards,
  Arnout

[snip]

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

^ permalink raw reply

* [Buildroot] [PATCH 1/2] toolchain-external: add support for Linaro 2012.10 toolchain
From: Peter Korsgaard @ 2012-10-26 11:13 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <1351239626-16394-1-git-send-email-thomas.petazzoni@free-electrons.com>

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 Thomas> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

Committed both, thanks.

-- 
Bye, Peter Korsgaard

^ permalink raw reply

* [Buildroot] [git commit] toolchain-external: remove support for Linaro 2012.05 toolchain
From: Peter Korsgaard @ 2012-10-26 11:12 UTC (permalink / raw)
  To: buildroot

commit: http://git.buildroot.net/buildroot/commit/?id=c90897b7dba131fc492ef25f3fcf68129df64ef9
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
 toolchain/toolchain-external/Config.in   |   17 -----------------
 toolchain/toolchain-external/ext-tool.mk |    3 ---
 2 files changed, 0 insertions(+), 20 deletions(-)

diff --git a/toolchain/toolchain-external/Config.in b/toolchain/toolchain-external/Config.in
index 7a9ec1d..98d0c0e 100644
--- a/toolchain/toolchain-external/Config.in
+++ b/toolchain/toolchain-external/Config.in
@@ -83,22 +83,6 @@ config BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_06
 
 	  To use this toolchain, you must disable soft float usage.
 
-config BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_05
-	bool "Linaro 2012.05"
-	depends on BR2_arm
-	depends on BR2_cortex_a8 || BR2_cortex_a9
-	select BR2_TOOLCHAIN_EXTERNAL_GLIBC
-	select BR2_INSTALL_LIBSTDCPP
-	help
-	  Linaro toolchain for the ARM architecture. It uses Linaro
-	  GCC 2012.05 (based on gcc 4.7), Linaro GDB 2012.05 (based on
-	  GDB 7.4), eglibc 2.13. It generates code that runs on all
-	  Cortex-A profile devices, but tuned for the Cortex-A9. The
-	  code generated is Thumb 2, with the hard floating point
-	  calling convention, and uses the VFPv3-D16 FPU instructions.
-
-	  To use this toolchain, you must disable soft float usage.
-
 config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203
 	bool "Sourcery CodeBench ARM 2012.03"
 	depends on BR2_arm
@@ -648,7 +632,6 @@ config BR2_TOOLCHAIN_EXTERNAL_CUSTOM_PREFIX
 
 config BR2_TOOLCHAIN_EXTERNAL_PREFIX
 	string
-	default "arm-linux-gnueabihf"	 if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_05
 	default "arm-linux-gnueabihf"	 if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_06
 	default "arm-linux-gnueabihf"	 if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_07
 	default "arm-linux-gnueabihf"	 if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_08
diff --git a/toolchain/toolchain-external/ext-tool.mk b/toolchain/toolchain-external/ext-tool.mk
index a7e4ab6..2c85931 100644
--- a/toolchain/toolchain-external/ext-tool.mk
+++ b/toolchain/toolchain-external/ext-tool.mk
@@ -190,9 +190,6 @@ TOOLCHAIN_EXTERNAL_SOURCE=arm-2011.09-70-arm-none-linux-gnueabi-i686-pc-linux-gn
 else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203),y)
 TOOLCHAIN_EXTERNAL_SITE=http://sourcery.mentor.com/public/gnu_toolchain/arm-none-linux-gnueabi/
 TOOLCHAIN_EXTERNAL_SOURCE=arm-2012.03-57-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
-else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_05),y)
-TOOLCHAIN_EXTERNAL_SITE=https://launchpad.net/linaro-toolchain-binaries/trunk/2012.05/+download/
-TOOLCHAIN_EXTERNAL_SOURCE=gcc-linaro-arm-linux-gnueabihf-2012.05-20120523_linux.tar.bz2
 else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_06),y)
 TOOLCHAIN_EXTERNAL_SITE=https://launchpad.net/linaro-toolchain-binaries/trunk/2012.06/+download/
 TOOLCHAIN_EXTERNAL_SOURCE=gcc-linaro-arm-linux-gnueabihf-2012.06-20120625_linux.tar.bz2

^ permalink raw reply related

* [Buildroot] [git commit] toolchain-external: add support for Linaro 2012.10 toolchain
From: Peter Korsgaard @ 2012-10-26 11:12 UTC (permalink / raw)
  To: buildroot

commit: http://git.buildroot.net/buildroot/commit/?id=94ca09c4725c423cda5f9a97039158fa79329c02
branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
 toolchain/toolchain-external/Config.in   |   17 +++++++++++++++++
 toolchain/toolchain-external/ext-tool.mk |    3 +++
 2 files changed, 20 insertions(+), 0 deletions(-)

diff --git a/toolchain/toolchain-external/Config.in b/toolchain/toolchain-external/Config.in
index 105fb2a..7a9ec1d 100644
--- a/toolchain/toolchain-external/Config.in
+++ b/toolchain/toolchain-external/Config.in
@@ -3,6 +3,22 @@ if BR2_TOOLCHAIN_EXTERNAL
 choice
 	prompt "Toolchain"
 
+config BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_10
+	bool "Linaro 2012.10"
+	depends on BR2_arm
+	depends on BR2_cortex_a8 || BR2_cortex_a9
+	select BR2_TOOLCHAIN_EXTERNAL_GLIBC
+	select BR2_INSTALL_LIBSTDCPP
+	help
+	  Linaro toolchain for the ARM architecture. It uses Linaro
+	  GCC 2012.10 (based on gcc 4.7), Linaro GDB 2012.10 (based on
+	  GDB 7.5), eglibc 2.15. It generates code that runs on all
+	  Cortex-A profile devices, but tuned for the Cortex-A9. The
+	  code generated is Thumb 2, with the hard floating point
+	  calling convention, and uses the VFPv3-D16 FPU instructions.
+
+	  To use this toolchain, you must disable soft float usage.
+
 config BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_09
 	bool "Linaro 2012.09"
 	depends on BR2_arm
@@ -637,6 +653,7 @@ config BR2_TOOLCHAIN_EXTERNAL_PREFIX
 	default "arm-linux-gnueabihf"	 if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_07
 	default "arm-linux-gnueabihf"	 if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_08
 	default "arm-linux-gnueabihf"	 if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_09
+	default "arm-linux-gnueabihf"	 if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_10
 	default "arm-none-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM2010Q1
 	default "arm-none-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201009
 	default "arm-none-linux-gnueabi" if BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201103
diff --git a/toolchain/toolchain-external/ext-tool.mk b/toolchain/toolchain-external/ext-tool.mk
index 43d747c..a7e4ab6 100644
--- a/toolchain/toolchain-external/ext-tool.mk
+++ b/toolchain/toolchain-external/ext-tool.mk
@@ -205,6 +205,9 @@ TOOLCHAIN_EXTERNAL_SOURCE=gcc-linaro-arm-linux-gnueabihf-2012.08-20120827_linux.
 else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_09),y)
 TOOLCHAIN_EXTERNAL_SITE=https://launchpad.net/linaro-toolchain-binaries/trunk/2012.09/+download/
 TOOLCHAIN_EXTERNAL_SOURCE=gcc-linaro-arm-linux-gnueabihf-2012.09-20120921_linux.tar.bz2
+else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_10),y)
+TOOLCHAIN_EXTERNAL_SITE=https://launchpad.net/linaro-toolchain-binaries/trunk/2012.10/+download/
+TOOLCHAIN_EXTERNAL_SOURCE=gcc-linaro-arm-linux-gnueabihf-4.7-2012.10-20121022_linux.tar.bz2
 else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_MIPS44),y)
 TOOLCHAIN_EXTERNAL_SITE=http://sourcery.mentor.com/sgpp/lite/mips/portal/package7401/public/mips-linux-gnu/
 TOOLCHAIN_EXTERNAL_SOURCE=mips-4.4-303-mips-linux-gnu-i686-pc-linux-gnu.tar.bz2

^ permalink raw reply related

* [Buildroot] [PATCH 2/2] toolchain-external: remove support for Linaro 2012.05 toolchain
From: Thomas Petazzoni @ 2012-10-26  8:20 UTC (permalink / raw)
  To: buildroot
In-Reply-To: <1351239626-16394-1-git-send-email-thomas.petazzoni@free-electrons.com>

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
---
 toolchain/toolchain-external/Config.in   |   17 -----------------
 toolchain/toolchain-external/ext-tool.mk |    3 ---
 2 files changed, 20 deletions(-)

diff --git a/toolchain/toolchain-external/Config.in b/toolchain/toolchain-external/Config.in
index 7a9ec1d..98d0c0e 100644
--- a/toolchain/toolchain-external/Config.in
+++ b/toolchain/toolchain-external/Config.in
@@ -83,22 +83,6 @@ config BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_06
 
 	  To use this toolchain, you must disable soft float usage.
 
-config BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_05
-	bool "Linaro 2012.05"
-	depends on BR2_arm
-	depends on BR2_cortex_a8 || BR2_cortex_a9
-	select BR2_TOOLCHAIN_EXTERNAL_GLIBC
-	select BR2_INSTALL_LIBSTDCPP
-	help
-	  Linaro toolchain for the ARM architecture. It uses Linaro
-	  GCC 2012.05 (based on gcc 4.7), Linaro GDB 2012.05 (based on
-	  GDB 7.4), eglibc 2.13. It generates code that runs on all
-	  Cortex-A profile devices, but tuned for the Cortex-A9. The
-	  code generated is Thumb 2, with the hard floating point
-	  calling convention, and uses the VFPv3-D16 FPU instructions.
-
-	  To use this toolchain, you must disable soft float usage.
-
 config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203
 	bool "Sourcery CodeBench ARM 2012.03"
 	depends on BR2_arm
@@ -648,7 +632,6 @@ config BR2_TOOLCHAIN_EXTERNAL_CUSTOM_PREFIX
 
 config BR2_TOOLCHAIN_EXTERNAL_PREFIX
 	string
-	default "arm-linux-gnueabihf"	 if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_05
 	default "arm-linux-gnueabihf"	 if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_06
 	default "arm-linux-gnueabihf"	 if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_07
 	default "arm-linux-gnueabihf"	 if BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_08
diff --git a/toolchain/toolchain-external/ext-tool.mk b/toolchain/toolchain-external/ext-tool.mk
index a7e4ab6..2c85931 100644
--- a/toolchain/toolchain-external/ext-tool.mk
+++ b/toolchain/toolchain-external/ext-tool.mk
@@ -190,9 +190,6 @@ TOOLCHAIN_EXTERNAL_SOURCE=arm-2011.09-70-arm-none-linux-gnueabi-i686-pc-linux-gn
 else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM201203),y)
 TOOLCHAIN_EXTERNAL_SITE=http://sourcery.mentor.com/public/gnu_toolchain/arm-none-linux-gnueabi/
 TOOLCHAIN_EXTERNAL_SOURCE=arm-2012.03-57-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
-else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_05),y)
-TOOLCHAIN_EXTERNAL_SITE=https://launchpad.net/linaro-toolchain-binaries/trunk/2012.05/+download/
-TOOLCHAIN_EXTERNAL_SOURCE=gcc-linaro-arm-linux-gnueabihf-2012.05-20120523_linux.tar.bz2
 else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_LINARO_2012_06),y)
 TOOLCHAIN_EXTERNAL_SITE=https://launchpad.net/linaro-toolchain-binaries/trunk/2012.06/+download/
 TOOLCHAIN_EXTERNAL_SOURCE=gcc-linaro-arm-linux-gnueabihf-2012.06-20120625_linux.tar.bz2
-- 
1.7.9.5

^ permalink raw reply related


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox