[yocto] matchbox-terminal automake-1.13 fix (retry)

2013-02-05 Thread Marko Lindqvist
[PATCH 1/2] configure.ac: fix autoreconf with automake-1.13

Seems that this bounced.
(2/2 was INSTALL removal already committed)


 - ML
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] pulseaudio madness

2013-02-05 Thread Gary Thomas

I have a multi-media application/system (built with Poky/Yocto of course)
that is currently using ALSA for the sound.  This works great but now
I'd like to be able to share some of the sound resources, in particular
the audio output (speakers).  To satisfy this, I looked at pulseaudio,
but I'm overwhelmed by the package choices (there are 120 packages),
not to mention what to do about configuration.

I don't see any examples (images, etc) that use pulseaudio.

Does anyone have any recommendations on what I might need to install,
how to configure it, etc, to take over from my simple ALSA setup?

Thanks

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] pulseaudio madness

2013-02-05 Thread Burton, Ross
Hi Gary,

On 5 February 2013 12:44, Gary Thomas  wrote:
> I have a multi-media application/system (built with Poky/Yocto of course)
> that is currently using ALSA for the sound.  This works great but now
> I'd like to be able to share some of the sound resources, in particular
> the audio output (speakers).  To satisfy this, I looked at pulseaudio,
> but I'm overwhelmed by the package choices (there are 120 packages),
> not to mention what to do about configuration.
>
> I don't see any examples (images, etc) that use pulseaudio.
>
> Does anyone have any recommendations on what I might need to install,
> how to configure it, etc, to take over from my simple ALSA setup?

The top tip is the PulseAudio documentation on the web site, that
lists all the plugins and what they do.  The pulseaudio-server package
depends on all of the important plugins, so that gives you a working
PA setup once you've started it.

You might want to have a look at Guacamayo's use of PA, that uses it
and will automatically switch output when new speakers are plugged in
too.https://github.com/Guacamayo

Ross
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-ivi][PATCH 1/3] systemd: Remove bbappend as xz si not GPLv3

2013-02-05 Thread Andrei Gherzan
Signed-off-by: Andrei Gherzan 
---
 recipes-core-ivi/systemd/systemd_git.bbappend |6 --
 1 files changed, 0 insertions(+), 6 deletions(-)
 delete mode 100644 recipes-core-ivi/systemd/systemd_git.bbappend

diff --git a/recipes-core-ivi/systemd/systemd_git.bbappend 
b/recipes-core-ivi/systemd/systemd_git.bbappend
deleted file mode 100644
index f881b7f..000
--- a/recipes-core-ivi/systemd/systemd_git.bbappend
+++ /dev/null
@@ -1,6 +0,0 @@
-PRINC := "${@int(PRINC) + 1}"
-
-# xz is GPLv3
-# Remove this package from depends and configure
-DEPENDS := "${@oe_filter_out('xz', '${DEPENDS}', d)}"
-EXTRA_OECONF := "${@oe_filter_out('--enable-xz', '${EXTRA_OECONF}', d)}"
-- 
1.7.5.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-ivi][PATCH 2/3] nfs-utils: Sync with oe-core version

2013-02-05 Thread Andrei Gherzan
Signed-off-by: Andrei Gherzan 
---
 ...ils_1.2.3.bbappend => nfs-utils_1.2.7.bbappend} |0
 1 files changed, 0 insertions(+), 0 deletions(-)
 rename recipes-connectivity/nfs-utils/{nfs-utils_1.2.3.bbappend => 
nfs-utils_1.2.7.bbappend} (100%)

diff --git a/recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bbappend 
b/recipes-connectivity/nfs-utils/nfs-utils_1.2.7.bbappend
similarity index 100%
rename from recipes-connectivity/nfs-utils/nfs-utils_1.2.3.bbappend
rename to recipes-connectivity/nfs-utils/nfs-utils_1.2.7.bbappend
-- 
1.7.5.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-ivi][PATCH 3/3] eglibc: Sync with oe-core version

2013-02-05 Thread Andrei Gherzan
Signed-off-by: Andrei Gherzan 
---
 .../{eglibc_2.16.bbappend => eglibc_2.17.bbappend} |0
 1 files changed, 0 insertions(+), 0 deletions(-)
 rename recipes-core-ivi/eglibc/{eglibc_2.16.bbappend => eglibc_2.17.bbappend} 
(100%)

diff --git a/recipes-core-ivi/eglibc/eglibc_2.16.bbappend 
b/recipes-core-ivi/eglibc/eglibc_2.17.bbappend
similarity index 100%
rename from recipes-core-ivi/eglibc/eglibc_2.16.bbappend
rename to recipes-core-ivi/eglibc/eglibc_2.17.bbappend
-- 
1.7.5.4

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Matchbox keyboard

2013-02-05 Thread Gary Thomas

Sorry if this isn't the best place to ask...

I have a GUI application running on Poky/Yocto with Sato using
only a touch screen.  My application window takes up the whole
display which is *very* small (320x240).  If I try and accept
text input, I can see the matchbox keyboard try to pop up, but
it immediately ends up behind my application window and thus
is of little use :-(

Is there some way to get the keyboard window to sit above my
application window while it is active?  I've experimented a bit
and I can use the terminal window in this environment but its
window gets sized very small - probably too small for my application.
Is that the only way for the matchbox keyboard and the application
that's using it for input to coexist?

Thanks for any ideas or pointers

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi][PATCH 2/2] Add RPROVIDES for OpenGL libraries

2013-02-05 Thread Tomas Frydrych
On 30/01/13 21:51, Philipp Wagner wrote:
> https://github.com/djwillis/meta-raspberrypi/issues/55
>
>  PROVIDES = "virtual/libgl virtual/libgles2 virtual/egl"
> +RPROVIDES = "virtual/libgl virtual/libgles2 virtual/egl"

As I noted in the above issue, this really is wrong; there is *no* libgl
provided by the RPi firmware.

Tomas


-- 
http://sleepfive.com
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi][PATCH 2/2] Add RPROVIDES for OpenGL libraries

2013-02-05 Thread Philipp Wagner
Am 05.02.2013 19:50, schrieb Tomas Frydrych:
> On 30/01/13 21:51, Philipp Wagner wrote:
>> https://github.com/djwillis/meta-raspberrypi/issues/55
>>
>>  PROVIDES = "virtual/libgl virtual/libgles2 virtual/egl"
>> +RPROVIDES = "virtual/libgl virtual/libgles2 virtual/egl"
> 
> As I noted in the above issue, this really is wrong; there is *no* libgl
> provided by the RPi firmware.

In the bug report, Andrei also mentions that it is required for some
reason, but I don't know exactly what the reason is.

Andrei, could you explain that in more detail?

Philipp
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Matchbox keyboard

2013-02-05 Thread Tomas Frydrych
On 05/02/13 18:47, Gary Thomas wrote:
> Sorry if this isn't the best place to ask...
> 
> I have a GUI application running on Poky/Yocto with Sato using
> only a touch screen.  My application window takes up the whole
> display which is *very* small (320x240).  If I try and accept
> text input, I can see the matchbox keyboard try to pop up, but
> it immediately ends up behind my application window and thus
> is of little use :-(

This should not be too small, I am pretty sure I have used it on a
device of that size, but it assumes the GUI application is well behaved
and obeys the window manager -- you have to make it respect the size the
WM allocates.

Tomas

-- 
http://sleepfive.com
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Matchbox keyboard

2013-02-05 Thread Gary Thomas

On 2013-02-05 12:00, Tomas Frydrych wrote:

On 05/02/13 18:47, Gary Thomas wrote:

Sorry if this isn't the best place to ask...

I have a GUI application running on Poky/Yocto with Sato using
only a touch screen.  My application window takes up the whole
display which is *very* small (320x240).  If I try and accept
text input, I can see the matchbox keyboard try to pop up, but
it immediately ends up behind my application window and thus
is of little use :-(


This should not be too small, I am pretty sure I have used it on a
device of that size, but it assumes the GUI application is well behaved
and obeys the window manager -- you have to make it respect the size the
WM allocates.


Does the window manager attempt to resize my window when the keyboard
pops up?  I have a simple dialog and I don't see it being resized (if
that's even possible)

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Matchbox keyboard

2013-02-05 Thread Tomas Frydrych
On 05/02/13 19:19, Gary Thomas wrote:
> On 2013-02-05 12:00, Tomas Frydrych wrote:
>> On 05/02/13 18:47, Gary Thomas wrote:
>>> Sorry if this isn't the best place to ask...
>>>
>>> I have a GUI application running on Poky/Yocto with Sato using
>>> only a touch screen.  My application window takes up the whole
>>> display which is *very* small (320x240).  If I try and accept
>>> text input, I can see the matchbox keyboard try to pop up, but
>>> it immediately ends up behind my application window and thus
>>> is of little use :-(
>>
>> This should not be too small, I am pretty sure I have used it on a
>> device of that size, but it assumes the GUI application is well behaved
>> and obeys the window manager -- you have to make it respect the size the
>> WM allocates.
> 
> Does the window manager attempt to resize my window when the keyboard
> pops up?  I have a simple dialog and I don't see it being resized (if
> that's even possible)

In the matchbox case it works through the window stack and works out the
size that is taken up by DOCKS and TOOLBARS (the kbd is a toolbar,
iirc); whatever is left is then given to the other windows (applications
and dialogs). Simplest way to verify if the WM is trying to resize the
dialog is to listen for the ConfigureNotify event and see what sizes are
coming through there (how you do that would depend on the toolkit).

Tomas

-- 
http://sleepfive.com
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [RFC v3 00/18][eclipse-poky] Storing yocto settings as target profiles

2013-02-05 Thread Zhang, Jessica
Hi Timo,

The patch series looks much better.  Here're few things we probably need to 
refine or explore a little bit more:
1. when I remove a profile, I'll get the following warning "Do you really want 
to the remove the target profile "profile-ide"?Projects using this target 
profile will be reconfigured to use the standard profile".  But the reality is 
the project that is configured using the deleted profile won't be affected at 
all.  You can go to the project->properties->Yocto Project Setting to check.  
So the message really should be: The standard profile will be used for Yocto 
Project ADT preference.

2.  As to the "Save as.." button style consistency concern, yeah I can see it's 
a little bit unconventional.  But my issue with new button is it gives the 
impression a separate wizard will show up to guide through the creation instead 
of just using the content on the page.  Probably an "Add" button is less 
confusing and I've seen it's used on some pages and put it up besides the 
combobox?

3. The whole profile idea is applicable to per project ADT setting as well. By 
default it inherits what is set for the whole ADT plug-in in the preference 
window.  But it can be something different aka. A different profile.  Any plan 
to extend the capability here?

Any further thoughts?

Thanks,
Jessica

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Timo Mueller
Sent: Sunday, February 03, 2013 11:36 PM
To: yocto@yoctoproject.org
Cc: Timo Mueller
Subject: [yocto] [RFC v3 00/18][eclipse-poky] Storing yocto settings as target 
profiles

From: Timo Mueller 

Hi,

thanks for the feedback, I did some changes to the patch series accordingly.

First of all I've fixed the issues with the patches (duplicate method, missing 
fix for NewYoctoCProjectTemplate.java).

I also changed the functionality of the "new" button according to Jessica's 
feedback. The logic is changed to a "Save as ..."
approach. If the button is clicked the current values of the form are checked. 
If these are valid, the user can enter a name to store them as a new profile.

The last patch moves the "Save as ..." button to the bottom of the preference 
page alongside with the "perform defaults" and the "apply"
button. I created this patch as a proof of concept because I thought it would 
be a good idea to move it.
I used the contributeButtons hook of the preference page to achieve this, but 
this only allows adding the "Save as ..." button left to the "perform defaults" 
button. So the order of the buttons is a bit confusing.
I further checked several other preference pages of eclipse and it seems like 
none of them is using this hook to add new buttons. Instead all have a new 
button next to the comboboxes (e.g. Formatter for CDT and JDT).
So I would plead against moving it to the bottom to have a more consistent and 
less confusing ui.

>From the original cover letter:

currently the yocto settings can be changed globally through eclipse's 
preferences or locally in the project properties. But the standard 
configuration stored in the global preferences sometimes changes, e.g. if a new 
version of the toolchain or the sysroot is released.
If you change the global settings to the updated toolchain or sysroot your old 
working configuration is gone. If you want to reuse this configuration at a 
later point in time you have to (remember and) re-enter everthing.
This patch set introduces the possiblity to store a configuration under a 
unique name, a so called target profile, and be able to select the default 
target profile that is used for new projects.
Building upon this change the target profiles could later also be used in the 
project settings and be able to quickly build and debug your software for 
different hard- and software combinations.


Best regards,
Timo


Atanas Gegov (4):
  plugins/sdk.ide: Extract labels to private members
  plugins/sdk.ide: Add method to enable and disable form
  plugins/sdk.ide: Set value of target array on input change
  plugins/sdk.ide: Create UI element for managing target profiles.

Timo Mueller (14):
  plugins/sdk.ide: Removed unused message
  plugins/sdk.ide: Changed method signature to be more consistent
  plugins/sdk.ide: Modified preferences storage to support profiles.
  plugins/sdk.ide: Set profile on selection change
  plugins/sdk.ide: Add method to allow storing the current settings
  plugins/sdk.ide: Add UI method to create a new profile
  plugins/sdk.ide: Add UI method to delete a profile
  plugins/sdk.ide: Add UI method to rename a profile
  plugins/sdk.ide: Add method to change values of the preference page
  plugins/sdk.ide: Add method to rename a profile and its preference
store
  plugins/sdk.ide: Add method to delete a profile
  plugins/sdk.ide: Use profiles for the preference page
  plugins/sdk.ide: Added profile UI to the preference page
  plugins/sdk.ide: Moved save as button to bottom of preference page

 .../src

[yocto] [meta-yocto][PATCH] poky.conf: Add Ubuntu 12.04.2 to sanity tested distros

2013-02-05 Thread Khem Raj
I have been running poky master on this distro for some time
now, this fix will avoid the warning about validated distros
during bitbake parse phase.

Signed-off-by: Khem Raj 
---
 meta-yocto/conf/distro/poky.conf |1 +
 1 file changed, 1 insertion(+)

diff --git a/meta-yocto/conf/distro/poky.conf b/meta-yocto/conf/distro/poky.conf
index 1d4e6f2..cb54d3f 100644
--- a/meta-yocto/conf/distro/poky.conf
+++ b/meta-yocto/conf/distro/poky.conf
@@ -76,6 +76,7 @@ SANITY_TESTED_DISTROS ?= " \
 Ubuntu 10.04.4 LTS \n \
 Ubuntu 11.10 \n \
 Ubuntu 12.04 LTS \n \
+Ubuntu 12.04.2 LTS \n \
 Ubuntu 12.04.1 LTS \n \
 Ubuntu 12.10 \n \
 Fedora release 16 (Verne) \n \
-- 
1.7.9.5

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, February 05, 2013 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).

2013-02-05 Thread Liu, Song
Attendees:
ScottR, BruceA, Jessica, TomZ, PaulE, BjörnS, JeffP, DarrenH, Richard, Belen, 
KevinS, ChrisL, LaurentiuP, DaveST, CristianI, NitinK, Corneliu, RossB, AlexG, 
ChrisK, SaulW, AlexD, SeanH, SongL

Agenda:

* Opens collection - 5 min (Song)
* Yocto Project 1.3.1 status - 10 min (Ross)
  - Ross: planning to kicking off the build today.
* Yocto 1.4 status - 10 min (Song/team)
  https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.4_Status
  . M4 date: 17th, cutoff for features, we still have M5 as a development 
milestone before stabilization in M6.
  . AlexG: a little bit of delay due to late M3 RC2, RC2 was out last Friday, 
test report will be out this Thursday.
  . Master: Saul, looking pretty green now. Next build for RP. We will run 
1.3.1 build next. Then we will be back to weekly test cycle.
  .RP: we put a lot of effort into getting autobuilder green. We are good now. 
We still have two issues. Freescale arm build. There are also the Cedar Trail 
problems. Matthew is looking at the fix, should be sometime today (3717).

* SWAT team rotation: Laurentiu Palcu -> Nitin Kamble
  - Saul: thanks for everyone doing SWAT. We are getting traction. You don't 
need to file bugs on master-next build. It sends email. But will talk to Beth. 
We may not need to send emails for master-next build errors. When you find 
problems, it would be better to look into it, describe the issue more a little 
more clearly rather than copy and paste while opening bugs.

* Opens - 10 min
  - Corneliu: what the test result will look on wiki. Working with Michael, 
showing an example: 
https://wiki.yoctoproject.org/wiki/Sample_-_1.4_M3.rc2_status
Would like to have feedback. Michael: thanks for Corneliu, he fixed some bugs 
in media wiki extension in the process of setting this up.
  - Chris/Tobia: user test result. A couple of weeks we completed first round 
on phase I. we got some outstanding feedback. Very helpful. We come up with 
another round of design. Creating and running build, working with projects, 
etc. Review the new design next week. If anyone who could do a remote session 
about 30 minutes, provide feedback, it will be super helpful. Get in touch with 
me if you are interested: 
chris.kamin...@tobias.tv. The result we got is 
on the HOB wiki: https://wiki.yoctoproject.org/wiki/Web_UI, 
https://lists.yoctoproject.org/listinfo/webhob
 Stage 3: refine metrics. Doing this at the same as stage 2.
* Team Sharing - 20 min
  - Daren: last night, send a post about updating proxy, a number of changes 
there. Some pluming, there is a new script handling proxy over socks, https. 
Anyone who can review and testing, would be great. Welcome feedback
  - CristianI: working on package update on multi-media. New release for 
connman, 1.11. bluez 5. would like to have suggestion how we would like to have 
this kind of upgrades, mainly on how to test these packages. Not sure how to 
test some package. Suggestion will be good. Bjorn: there is a test suite in one 
of the package, could be a candidate for ptest.
  - Sean: my presentation is accepted for ELC. "Building a distribution with 
Yocto". 13 YP related presentation including Dave's keynote.
  - LaurentiuP: chasing down postinstall issues. Last batch of patches 
submitted to the mailing list, would like people to test it. Issue with 
testmode? Some issues with using sstate from a building machine, build on your 
own machine should be fine. Saul: building now, will test it out. RP: 
appreciate getting these postinstall fixes. This is critical.
  - Michael: last week created RC2, had a 4 hour donwtime, updated some stable 
kernel versions. First time AB down and brought up again automatically. AB 1, 
2, 4, 5, 6, 10. Darren: had some issue with qemu, causing some segfault and 
sanity test issue. Saul is running some test. Upgrading kernel may help. 
Prospect of getting newer kernel? Michael: possible to do that. We are trying 
to run stable kernels. Saul: thanks to Michael for doing all these work. LF 
recommend all projects to require one time pin to elevate authority. It affects 
people using 'su' to root. Hopefully releasing M3 RC2 this Friday. Song: will 
schedule release review meeting once we have the test result.


___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto