On Tue, Mar 26, 2013 at 7:57 PM, Flanagan, Elizabeth
wrote:
> 1.4_M5.rc2 is currently building and will be available in a few hours at:
>
> http://autobuilder.yoctoproject.org/pub/nightly/20130326-2
All,
I've found an error in the autobuilder code that caused the creation
of bb
1.4_M5.rc2 is currently building and will be available in a few hours at:
http://autobuilder.yoctoproject.org/pub/nightly/20130326-2
meta-intel: 2e8760d272aa2c62b41cbf768445c99569604c5e
meta-qt3: 4c27cce6688aa39852f3cba5e7b80ec279019605
poky: bdca49274173153b1b0a72887de6321b4756b684
meta-fsl-ppc
Thanks Mark!
That information has been very useful. Looks like some python code will be
the way we need to go.
>I think it's a good idea to have some standard tunes with functionality that
>is
>reasonable for a testable demo environment. If the developers want to tailor
>it
>further, they s
Attendees:
MichaelH, Sean, KevinS, Corneliu, TomZ, BruceA, DaveST, JeffP, MarkH, Belen,
Paul, Nitin, ScottR, Björn Stenberg, RP, CristianI, Ioana, AlexG, FahadU, SongL
Agenda:
* Opens collection - 5 min (Song)
* 1.3.1:
. We had a build and passed QA full pass testing. Got approval from
On Tue, Mar 26, 2013 at 2:37 PM, Burton, Ross wrote:
> Danni would be a terrible name
Of course it would be a terrible name, that's why I suggested it; I
figured it'd fit in with the others :-D
(don't forget my earlier statement about this being done in jest)
On 3/26/13 9:25 AM, Paul Eggleton wrote:
Hi Simon,
On Tuesday 26 March 2013 14:37:36 Vanveerdeghem, Simon wrote:
We are using Yocto with a couple of users, to prevent that our build
server has duplicates of downloads, we share the DL_DIR.
But we have problems with permissions. When a user run
On 3/26/13 7:53 AM, Jerrod Peach wrote:
As part of my company's firmware builds, we have to build some code that only a
handful of developers are allowed to view. We call this restricted source code.
Getting our official "system" builds to build this code isn't a problem. What
is a problem is
On 3/26/13 1:12 AM, Sipke Vriend wrote:
Hi all,
With help from Khem's email we have been able to perform 'some' sanity
checking against the microblaze architecture.
The TUNECONFLICTS assist us in ensuring conflicting features are flagged during
the bitbake sanity check, however because Microbla
On 26 March 2013 17:28, Trevor Woerner wrote:
> [the following is meant to be humourous, please take it as such]
>
> What I'm hoping to see in the next release is a better release name.
> Male first names was the best suggestion? I recommend the next release
> be named "Dani", a female version of
[the following is meant to be humourous, please take it as such]
What I'm hoping to see in the next release is a better release name.
Male first names was the best suggestion? I recommend the next release
be named "Dani", a female version of "Danny", just to keep things
equal.
There have been some concerns raised at the TSC recently about how
transparent the Yocto Project development process is and how and where
it connects to OpenEmbedded. When you're dealing with companies and
engineers there does need to be a process with things like schedules and
in the interests of
We're now in the planning stages for the 1.5 release scheduled for about
6 months time. The process hasn't changed, if there are things you'd
like to see worked on in this timeframe, please ensure there are entries
for them in the bugzilla. Usually these are "enhancement" requests.
https://bugzill
Hi Simon,
On Tuesday 26 March 2013 14:37:36 Vanveerdeghem, Simon wrote:
> We are using Yocto with a couple of users, to prevent that our build
> server has duplicates of downloads, we share the DL_DIR.
>
> But we have problems with permissions. When a user run yocto, it will
> checkout sources, o
Hi,
We are using Yocto with a couple of users, to prevent that our build
server has duplicates of downloads, we share the DL_DIR.
But we have problems with permissions. When a user run yocto, it will
checkout sources, or download tar files with permissions 644 with the
username of the user who
i've managed to solve the qmake problem i did this:
sudo rm /usr/bin/qmake sudo ln -s /usr/bin/qmake-qt4 /usr/bin/qmake
After that: qmake -o Makefile myproject.pro
make
It made me an executable, then i've copied the whole project folder on a
USB stick, mount it on my target and the
As part of my company's firmware builds, we have to build some code that
only a handful of developers are allowed to view. We call this restricted
source code. Getting our official "system" builds to build this code isn't
a problem. What is a problem is a regular developer's build of this code.
ok, so i've uninstalled all the programs ralated to qt4 and qt5, i wanted
to start a fresh install of qt4 SDK, i've found QtSDK v 1.2.1 wich i think
is Qt4 related, I downloaded it from nokia website, installed it, and
creted a simple hello world window...it build and ran succesfuly. But when
i go
Can you please tell me where can i download Qt4SDK? I've searched it but i
did not find it
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Hi,
Le Tue, 26 Mar 2013 08:33:43 +0200,
Florin Cristian Dan a écrit :
> Hi...
> I've tried adding this
>
> CORE_IMAGE_EXTRA_INSTALL += "qt4-tools"
>
> in order to have the qt4 tools, and now, i made a simple qt4 form
> aplication with a label ana a test box, nothing special, just for
> test..
19 matches
Mail list logo
