Hi Timo,
So what's the purpose of "Project Specific Settings", my understanding is it's
something that only local to project instead of global name space, e.g.
profile? OK, I've played a little bit of toggling between profiles, and
project specific setting and notice the following behaviors th
OK more info. It seems if the project is remote, first we'll get the project
description failure since we haven't restored the remote connection, after we
dismiss the error and double click on the project and restore the RSE
connection, the project will be able to restore. We should change the
Hi Ioana,
With the latest changes, now with a remote project if I want to restore the
project, I'm getting following errors:
Failed to read the project description file (.project) for 'poky'. The file
has been changed on disk, and it now contains invalid information. The project
will not fu
Hi Ioana,
Unfortunately we have to introduce the API getReader in IHostShell interface,
otherwise, when I applied the patch to my clean upstream RSE master and open a
project I'm getting:
An internal error occurred during "Open Project"
Unresolved compilation problems:
The method getReader(Bool
> From: Tomas Frydrych
>
> On 20/06/13 20:40, Paul D. DeRocco wrote:
> > My question is this: why was I able to build core-image base without
> > complaint in the first place? The kernel recipes it has available
> > (linux-yocto_*) also set COMPATIBLE_MACHINE to a list of
> qemu machines.
>
> It
Thanks Paul / Elizabeth,
On 21 Jun 2013, at 17:53, Paul Eggleton wrote:
> On Friday 21 June 2013 17:47:13 Chris Tapp wrote:
>> Simple question - Is openembedded-core included in one of the Yocto meta
>> layers, or do I need to download it from the OE git repository?
>
> It comes as part of the p
On Friday 21 June 2013 17:47:13 Chris Tapp wrote:
> Simple question - Is openembedded-core included in one of the Yocto meta
> layers, or do I need to download it from the OE git repository?
It comes as part of the poky repository if you're using that. The alternative
is to use bitbake and OE-Cor
Simple question - Is openembedded-core included in one of the Yocto meta
layers, or do I need to download it from the OE git repository?
Chris Tapp
opensou...@keylevel.com
www.keylevel.com
___
yocto mailing list
yocto@yoctoproject.org
https://lists.
- when browsing to pick the project location, if "My Home" or "Root" get picked
the project location remains empty
- this is caused by the RSEUIFileManager browseDirectory method
- the selection made in the SystemRemoteFolderDialog is an
SystemFilterReference, and thus not a instance of IRemot
- add a plain getter in the AbstractHostShell class:
- the compilation is not broken for subclasses of this class since it
always returns null
- the targeted classes (local and remote) can implement the getter
(local implementation is already there)
- the reader can be acc
- when browsing to pick the project location, if "My Home" or "Root" get picked
the project location remains empty
- this is caused by the RSEUIFileManager browseDirectory method
- the selection made in the SystemRemoteFolderDialog is an
SystemFilterReference, and thus not a instance of IRemot
From: Ioana Grigoropol
- add a plain getter in the AbstractHostShell class:
- the compilation is not broken for subclasses of this class since it
always returns null
- the targeted classes (local and remote) can implement the getter
(local implementation is already there)
From: Ioana Grigoropol
- when creating a new bitbake commander project, a bunch of information
relevant for the project is set in the project information map
- when closing & restarting Eclipse, having a Bitbake commander project in the
workspace an deadlock occurs due to the following:
I'm trying to create a meta-layer for a third-party GCC-based proprietary
tool-chain. I need to be able to select this tool-chain on a per-recipe
basis while other recipes may either the standard Yocto
native/cross-tool-chain. This proprietary tool chain is divided into a
host-tool part (where all
From: Timo Mueller
If a project with a yocto nature is selected, the toolbar will show a
target profile menu which allows the user to switch the used target
profile of the project.
The content of this menu is dynamically created using the list of
globally defined target profiles. Additionally it
From: Timo Mueller
The command can be used in a radio group to switch the target profile
of a selected project.
Radio items should call this command handing over the name of the
target profile as the command's parameter.
Signed-off-by: Timo Mueller
---
.../OSGI-INF/l10n/bundle.properties
From: Timo Mueller
Move project specific methods to the new util class to allow public
usage of theses methods.
Signed-off-by: Timo Mueller
---
.../preferences/YoctoSDKProjectPropertyPage.java | 121 ++---
.../sdk/ide/utils/ProjectPreferenceUtils.java | 102 +
From: Timo Mueller
This changes the behaviour of the project specific profile button. If
the project specific profile is not yet defined for the selected
project, the list will contain a button to open the project
preferences instead of the greying out the button.
Signed-off-by: Timo Mueller
--
From: Timo Mueller
If a project with a yocto nature is selected, the project menu will
show a target profile menu which allows the user to switch the used
target profile of the project.
Signed-off-by: Timo Mueller
---
plugins/org.yocto.sdk.ide/plugin.xml | 25 +
1 file
From: Timo Mueller
Signed-off-by: Timo Mueller
---
plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoUISetting.java | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
a/plugins/org.yocto.sdk.ide/src/org/yocto/sdk/ide/YoctoUISetting.java
b/plugins/org.yocto.sdk.ide/src/org
From: Timo Mueller
Through the context of the ProjectPreferenceUtil class we can infer
that all methods act on project preferences. Having this context
information duplicated in the method name is not needed anymore and
can be removed to get a cleaner API.
Signed-off-by: Timo Mueller
---
.../s
From: Timo Mueller
Changes in v2:
Handle error when project specific profile is not configured more
gracefully. Instead of showing an error message the button is now
greyed out.
Patches 01..07 contain the implementation with the greyed out menu
button.
After playing around with the two options
From: Timo Mueller
Project specific util methods are moved to a separate util class. This
way the general util class will get more concise and other project
specific methods can be move to this new util class later.
Signed-off-by: Timo Mueller
---
.../natures/YoctoSDKAutotoolsProjectNature.jav
On Fri, Jun 21, 2013 at 9:26 AM, Thanassis Silis wrote:
...
> In the end it was some problem with the packages_deb. There seem to be some
> bug related to deb packaging. I only set deb packaging because it seems more
> compatible as I am on a Ubuntu system.
> rpm packagin on the other hand worked
Hi Anna,
yes it was an OpenSSL dependency, but it seems weird to bump into such a
problem. I mean This seems to have been rectified or more ppl would bump into
it.
In the end it was some problem with the packages_deb. There seem to be some bug
related to deb packaging. I only set deb packaging b
Hi,
I need to compile Qt Code for Yocto image.
I have installed meta toolchain using
bitbake meta-toolchain-qte
It has created the SDK in
../meta-toolchain-qte-1.0-r7/sdk/image/poky/1.3.2/sysroots .
Now i am trying to build qt code for my Yocto image as :
source /poky/1.3.2/environmen
Then how should I go about adding a --sysroots statement in the generated
meta-toolchain, of the generated image?
From: jessica.zh...@intel.com
To: djnass...@hotmail.com; yocto@yoctoproject.org
Subject: RE: [yocto] toolchain's environment-setup file that includes the image
generated rootfs
Dat
Hi Paul,
On 20/06/13 20:40, Paul D. DeRocco wrote:
> My question is this: why was I able to build core-image base without
> complaint in the first place? The kernel recipes it has available
> (linux-yocto_*) also set COMPATIBLE_MACHINE to a list of qemu machines.
It probably built the linux-dummy
Hi,
If I am not wrong the file mount.sh in udev already does this but I dont
know if it different for a live image ...
On Fri, Jun 21, 2013 at 10:37 AM, Paul D. DeRocco wrote:
> My image is a live image that is booted from a flash drive. The drive
> actually has two partitions on it, and I'd li
My image is a live image that is booted from a flash drive. The drive
actually has two partitions on it, and I'd like the second partition to get
mounted on startup. I believe that what I need is to create a mount point in
the image's file system, and also append a line to /etc/fstab. How do I
writ
30 matches
Mail list logo
