Re: [yocto] [PATCH 0/3][eclipse-poky][branch:windows-build]

2013-01-10 Thread Zhang, Jessica
Hi Ioana,

I'm still seeing problems:

1. seems the reinstate OEFilesystem etc. changes is not taking effect, I'm 
still running into heap space error with my metadata directory with huge build 
data.  So can you create such a metadata directory and run toolchain, and 
sato-sdk build and see whether you can create the project against it?
2. Ran into another issue while playing with these patch set, if I leave the 
clone box checked, even though I do see the error message telling me the 
directory/project already a clone directory, I was still able to click on 
finish and all process continue on instead of being blocked by the error 
message.

Thanks,
Jessica

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Ioana Grigoropol
Sent: Thursday, January 10, 2013 7:25 AM
To: yocto@yoctoproject.org
Subject: [yocto] [PATCH 0/3][eclipse-poky][branch:windows-build]

*** BLURB HERE ***

Ioana Grigoropol (1):
  Fix variables hoover & remote file system detection

yocto (2):
  Allow '-' in project names Signed-off-by: yocto

  Reinstate OEFileSystem, OEFile and Ignored Paths for Linux

 plugins/org.yocto.bc.ui/META-INF/MANIFEST.MF   |2 +-
 plugins/org.yocto.bc.ui/plugin.xml |3 +-
 .../src/org/yocto/bc/bitbake/BBSession.java|4 +
 .../org/yocto/bc/bitbake/ProjectInfoHelper.java|   24 ++--
 .../src/org/yocto/bc/bitbake/ShellSession.java |   13 ++-
 .../org/yocto/bc/remote/utils/RemoteHelper.java|7 +-
 .../org/yocto/bc/remote/utils/RemoteMachine.java   |8 +-
 .../src/org/yocto/bc/ui/Activator.java |   45 +---
 .../org/yocto/bc/ui/BCResourceChangeListener.java  |1 -
 .../bc/ui/editors/bitbake/BBVariableTextHover.java |   12 +-
 .../src/org/yocto/bc/ui/filesystem/OEFile.java |  120 
 .../org/yocto/bc/ui/filesystem/OEFileSystem.java   |   50 ++--
 .../bc/ui/filesystem/OEFileSystemContributor.java  |7 +-
 .../org/yocto/bc/ui/filesystem/OEIgnoreFile.java   |   31 -
 .../src/org/yocto/bc/ui/model/ProjectInfo.java |   21 +++-
 .../src/org/yocto/bc/ui/model/YoctoHostFile.java   |  100 
 .../yocto/bc/ui/wizards/install/OptionsPage.java   |3 +-
 .../newproject/CreateBBCProjectOperation.java  |   23 ++--
 18 files changed, 281 insertions(+), 193 deletions(-)

--
1.7.9.5

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


Re: [yocto] Shouldn't linux/version.h appear in the SDK's host sysroot?

2013-01-10 Thread Zhang, Jessica
Hi Patrick,

The toolchain and sysroot are behaving correctly,  the x86_64-pokysdk-linux 
contains the cross tools for your development host, whereas 
armv7a-vfp-neon-poky-linux-gnueabi contains your target sysroot, and all your 
target programs should be using files against that sysroot.  By not knowing how 
your compile your package, but if you look at our ADT manual, you should source 
the environment setup script before you try to use the toolchain and you also 
need to pass sysroot option to your compiler and linker for them to go to the 
target sysroot location for headers and libraries.

Thanks,
Jessica

-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Patrick Turley
Sent: Thursday, January 10, 2013 2:46 PM
To: yocto@yoctoproject.org
Subject: [yocto] Shouldn't linux/version.h appear in the SDK's host sysroot?

I'm using a Yocto-based SDK, produced by:

bitbake meta-toolchain-sdk

This creates the file

poky-eglibc-x86_64-arm-toolchain-gmae-1.3.sh

in the directory

build/tmp/deploy/sdk

I ran the installation script to install the SDK on my build system. Within the 
SDK installation directory, under "sysroots", I have the following two 
directories:

armv7a-vfp-neon-poky-linux-gnueabi
x86_64-pokysdk-linux

Unless I'm mistaken, the first one reflects the target environment, and the 
second one contains what I need to do cross-compilation. Thus, the latter 
contains the cross-compilation tools, and that's the sysroot to which all my 
builds are directed.

I'm compiling the lm_sensors package for my target. As part of its work, it 
tries to discover the version of the target linux kernel. To do this, it 
compiles a very small file (etc/config.c) that includes the header file 
.

As it happens,  does *not* appear in the cross-compilation 
sysroot, so this simple task fails. That header file *does* appear in the 
target sysroot, but that's of no use to me in the cross-compilation process.

I believe one of the following is true:

1) The lm_sensors package is doing something entirely legitimate, and the file 
 *should* appear in the cross-compilation sysroot to support 
this. The Yocto SDK build target needs a small fix so that  is 
properly added to the cross-compilation sys root. In the meantime, I can work 
around this oversight by creating a symbolic link.

2) I've made a mistake in setting up my build environment because I don't 
understand how cross-compilation *should* be done. If done properly, the 
cross-compilation process will have access to *both* sysroots and get what it 
needs from each. If this is the case, please tell me what I appear to have done 
wrong.

3) Something else.

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


[yocto] Shouldn't linux/version.h appear in the SDK's host sysroot?

2013-01-10 Thread Patrick Turley
I'm using a Yocto-based SDK, produced by:

bitbake meta-toolchain-sdk

This creates the file 

poky-eglibc-x86_64-arm-toolchain-gmae-1.3.sh

in the directory

build/tmp/deploy/sdk

I ran the installation script to install the SDK on my build system. Within the 
SDK installation directory, under "sysroots", I have the following two 
directories:

armv7a-vfp-neon-poky-linux-gnueabi
x86_64-pokysdk-linux

Unless I'm mistaken, the first one reflects the target environment, and the 
second one contains what I need to do cross-compilation. Thus, the latter 
contains the cross-compilation tools, and that's the sysroot to which all my 
builds are directed.

I'm compiling the lm_sensors package for my target. As part of its work, it 
tries to discover the version of the target linux kernel. To do this, it 
compiles a very small file (etc/config.c) that includes the header file 
.

As it happens,  does *not* appear in the cross-compilation 
sysroot, so this simple task fails. That header file *does* appear in the 
target sysroot, but that's of no use to me in the cross-compilation process.

I believe one of the following is true:

1) The lm_sensors package is doing something entirely legitimate, and the file 
 *should* appear in the cross-compilation sysroot to support 
this. The Yocto SDK build target needs a small fix so that  is 
properly added to the cross-compilation sys root. In the meantime, I can work 
around this oversight by creating a symbolic link.

2) I've made a mistake in setting up my build environment because I don't 
understand how cross-compilation *should* be done. If done properly, the 
cross-compilation process will have access to *both* sysroots and get what it 
needs from each. If this is the case, please tell me what I appear to have done 
wrong.

3) Something else.

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


[yocto] recipes for git gfortran java

2013-01-10 Thread Edward Vidal
All,
what is the best way to install git gfortran and  java to beagleboards and
pandaboards.
With angstrom builds you use opkg.  Since Yocto is rpm base are there repo
that have compiled software.
Any and all help will be appreciated.
Thanks
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] meta-cedartrail - where is grub configured for 'install' option?

2013-01-10 Thread Darren Hart


On 01/10/2013 12:09 AM, Chris Tapp wrote:
> Hi Darren,
> 
> On 7 Jan 2013, at 16:44, Darren Hart wrote:
> 
>> On 12/09/2012 01:39 PM, Chris Tapp wrote:
>>> I am trying to change the 'install' behaviour for the meta-cedartrail image 
>>> so that the installed system has a different grub.cfg file. Is there a file 
>>> I can bbappend to achieve this?
>>>
>>> image_live.bbclass refers to the 'install' syslinux label that triggers the 
>>> install, but I've not been able to get from this to how/where grub.cfg is 
>>> created.
>>>
>>
>> This is currently rather crudely implemented here:
>>
>> meta/recipes-core/initrdscripts/files/init-install.sh
>>
>> A better deployment mechanism is something being discussed and which
>> should make this more configurable.
>>
>> For now, you could bbappend initramfs-live-install_1.0.bb and replace the
>> init-install.sh script with your own.
> 
> Thanks. I've already got to look at that script anyway as it fails to
> install to an internal USB drive on a DN2800-MT board as (I think) it
> isn't waiting long enough for it to enumerate when booting the
> 'install' image.

Hrm, I thought it waited indefinitely for the device to appear. Or is it
finding something else and bailing out of the loop? Where is the failure?

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [PATCH] Send output from bitbake environment parsing in the background

2013-01-10 Thread Ioana Grigoropol
- after creating the project, the wizard should not block waiting for the 
environment to be populated and instead should be ran in the background

Signed-off-by: Ioana Grigoropol 
---
 .../src/org/yocto/bc/bitbake/BBSession.java|   83 
 .../src/org/yocto/bc/bitbake/ShellSession.java |3 +-
 .../org/yocto/bc/remote/utils/RemoteHelper.java|3 +-
 .../org/yocto/bc/remote/utils/RemoteMachine.java   |3 -
 .../remote/utils/YoctoHostShellProcessAdapter.java |   16 +++-
 .../org/yocto/bc/ui/filesystem/OEFileSystem.java   |6 --
 .../yocto/bc/ui/wizards/FiniteStateWizardPage.java |   54 +++--
 .../bc/ui/wizards/NewBitBakeFileRecipeWizard.java  |   58 +++---
 .../yocto/bc/ui/wizards/install/InstallWizard.java |   63 +--
 .../yocto/bc/ui/wizards/install/OptionsPage.java   |   10 ++-
 10 files changed, 174 insertions(+), 125 deletions(-)

diff --git a/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/BBSession.java 
b/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/BBSession.java
index 66a6083..124b9a2 100644
--- a/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/BBSession.java
+++ b/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/BBSession.java
@@ -13,8 +13,8 @@ package org.yocto.bc.bitbake;
 import java.io.BufferedReader;
 import java.io.File;
 import java.io.FileFilter;
+import java.io.FileReader;
 import java.io.IOException;
-import java.io.StringReader;
 import java.net.URI;
 import java.util.ArrayList;
 import java.util.Arrays;
@@ -48,7 +48,7 @@ import org.yocto.bc.ui.model.ProjectInfo;
 /**
  * BBSession encapsulates a global bitbake configuration and is the primary 
interface
  * for actions against a BitBake installation.
- * 
+ *
  * @author kgilmer
  *
  */
@@ -57,7 +57,9 @@ public class BBSession implements IBBSessionListener, 
IModelElement, Map {
public static final int TYPE_UNKNOWN = 2;
public static final int TYPE_STATEMENT = 3;
public static final int TYPE_FLAG = 4;
-   
+
+   public static final String BB_ENV_FILE = "bitbake.env";
+
public static final String BUILDDIR_INDICATORS [] = {
"/conf/local.conf",
"/conf/bblayers.conf",
@@ -74,20 +76,20 @@ public class BBSession implements IBBSessionListener, 
IModelElement, Map {
private final Lock wlock = rwlock.writeLock();
protected String parsingCmd;
private boolean silent = false;
-   
+
public BBSession(ShellSession ssession, URI projectRoot) throws 
IOException {
shell = ssession;
this.pinfo = new ProjectInfo();
pinfo.setLocation(projectRoot);

pinfo.setInitScriptPath(ProjectInfoHelper.getInitScriptPath(projectRoot));
-   this.parsingCmd = "DISABLE_SANITY_CHECKS=\"1\" bitbake -e";
+   this.parsingCmd = "sh -c 'DISABLE_SANITY_CHECKS=\"1\" bitbake 
-e >& " + BB_ENV_FILE + "  '" ;
}
 
public BBSession(ShellSession ssession, URI projectRoot, boolean 
silent) throws IOException {
this(ssession, projectRoot);
this.silent = silent;
}
-   
+
private Collection adapttoIPath(List asList, IProject project) {
 
List pathList = new ArrayList();
@@ -102,7 +104,7 @@ public class BBSession implements IBBSessionListener, 
IModelElement, Map {
 
return pathList;
}
-   
+
private String appendAll(String[] elems, int st) {
StringBuffer sb = new StringBuffer();
 
@@ -112,7 +114,7 @@ public class BBSession implements IBBSessionListener, 
IModelElement, Map {
 
return sb.toString();
}
-   
+
private int charCount(String trimmed, char c) {
int i = 0;
int p = 0;
@@ -124,11 +126,13 @@ public class BBSession implements IBBSessionListener, 
IModelElement, Map {
 
return i;
}
-   
+
+   @Override
public void clear() {
throw new RuntimeException("BB configuration is read-only.");
}
 
+   @Override
public boolean containsKey(Object arg0) {
try {
checkValidAndLock(true);
@@ -141,6 +145,7 @@ public class BBSession implements IBBSessionListener, 
IModelElement, Map {
}
}
 
+   @Override
public boolean containsValue(Object arg0) {
try {
checkValidAndLock(true);
@@ -153,6 +158,7 @@ public class BBSession implements IBBSessionListener, 
IModelElement, Map {
}
}
 
+   @Override
public Set entrySet() {
try {
checkValidAndLock(true);
@@ -188,7 +194,7 @@ public class BBSession implements IBBSessionListener, 
IModelElement, Map {
 
/**
 * Recursively generate list of Recipe files from a root directory.
-* 
+*
 * @param r

[yocto] [PATCH v2 3/3] Reinstate OEFileSystem, OEFile and Ignored Paths for Linux

2013-01-10 Thread Ioana Grigoropol
- OEFileSystem and OEFile were dropped due to the use of hardcoded scheme 
"oefs://" that stopped remote connection from working. There is a need to have 
a custom file system in order to skip indexing large directories (such as 
build, tmp) and ignore some paths--was not tested under Windows

Signed-off-by: Ioana Grigoropol 
---
 plugins/org.yocto.bc.ui/META-INF/MANIFEST.MF   |2 +-
 plugins/org.yocto.bc.ui/plugin.xml |3 +-
 .../org/yocto/bc/bitbake/ProjectInfoHelper.java|   24 ++--
 .../src/org/yocto/bc/ui/Activator.java |   45 +---
 .../org/yocto/bc/ui/BCResourceChangeListener.java  |1 -
 .../src/org/yocto/bc/ui/filesystem/OEFile.java |  120 
 .../org/yocto/bc/ui/filesystem/OEFileSystem.java   |   50 ++--
 .../bc/ui/filesystem/OEFileSystemContributor.java  |7 +-
 .../org/yocto/bc/ui/filesystem/OEIgnoreFile.java   |   31 -
 .../src/org/yocto/bc/ui/model/ProjectInfo.java |   21 +++-
 .../src/org/yocto/bc/ui/model/YoctoHostFile.java   |  100 
 .../yocto/bc/ui/wizards/install/OptionsPage.java   |1 -
 .../newproject/CreateBBCProjectOperation.java  |   23 ++--
 13 files changed, 248 insertions(+), 180 deletions(-)

diff --git a/plugins/org.yocto.bc.ui/META-INF/MANIFEST.MF 
b/plugins/org.yocto.bc.ui/META-INF/MANIFEST.MF
index 9e8c523..1f0e63e 100644
--- a/plugins/org.yocto.bc.ui/META-INF/MANIFEST.MF
+++ b/plugins/org.yocto.bc.ui/META-INF/MANIFEST.MF
@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: %Bundle-Name
 Bundle-SymbolicName: org.yocto.bc.ui;singleton:=true
-Bundle-Version: 1.4.0.qualifier
+Bundle-Version: 1.2.0.qualifier
 Bundle-Activator: org.yocto.bc.ui.Activator
 Bundle-Vendor: %Bundle-Vendor
 Require-Bundle: org.eclipse.ui,
diff --git a/plugins/org.yocto.bc.ui/plugin.xml 
b/plugins/org.yocto.bc.ui/plugin.xml
index cb0561c..6ba9b5f 100644
--- a/plugins/org.yocto.bc.ui/plugin.xml
+++ b/plugins/org.yocto.bc.ui/plugin.xml
@@ -180,8 +180,7 @@


-  
+  
  
  
diff --git 
a/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/ProjectInfoHelper.java 
b/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/ProjectInfoHelper.java
index 2938c95..f5259e5 100644
--- a/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/ProjectInfoHelper.java
+++ b/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/ProjectInfoHelper.java
@@ -10,27 +10,25 @@
  
***/
 package org.yocto.bc.bitbake;
 
-import java.io.BufferedReader;
-import java.io.File;
-import java.io.FileReader;
 import java.io.IOException;
 import java.net.URI;
-import java.net.URISyntaxException;
 
 import org.eclipse.core.resources.IProject;
 import org.eclipse.core.resources.ResourcesPlugin;
 import org.eclipse.core.runtime.IProgressMonitor;
 import org.eclipse.rse.core.model.IHost;
-import org.yocto.bc.remote.utils.RemoteHelper;
 import org.yocto.bc.ui.model.ProjectInfo;
 
 /**
  * A helper class for ProjectInfo related tasks.
- * 
+ *
  * @author kgilmer
- * 
+ *
  */
 public class ProjectInfoHelper {
+   public static final String OEFS_SCHEME = "OEFS://";
+   public static final String FILE_SCHEME = "file";
+   public static final String RSE_SCHEME = "rse";
 
protected static final String DEFAULT_INIT_SCRIPT = "oe-init-build-env";
/**
@@ -54,17 +52,17 @@ public class ProjectInfoHelper {
 // }
return val;
}
-   
+
 // public static String getInitScript(String path) throws IOException {
 // File inFile = new File(path);
 // BufferedReader br = new BufferedReader(new FileReader(inFile));
 // StringBuffer sb = new StringBuffer();
 // String line = null;
-// 
+//
 // while ((line = br.readLine()) != null) {
 // sb.append(line);
 // }
-// 
+//
 // br.close();
 //
 // return sb.toString();
@@ -89,7 +87,7 @@ public class ProjectInfoHelper {
/**
 * This method will store the path to the bitbake init script for future
 * reference.
-* 
+*
 * @param path
 * @param projInfo
 * @throws IOException
@@ -121,8 +119,8 @@ public class ProjectInfoHelper {
} catch (Exception e) {
e.printStackTrace();
}
-   
-   
+
+
}
 
 }
diff --git a/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/Activator.java 
b/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/Activator.java
index 48c59d5..188efe6 100644
--- a/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/Activator.java
+++ b/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/Activator.java
@@ -14,6 +14,7 @@ import java.io.IOException;
 import java.io.Writer;
 import java.lang.reflect.InvocationTargetException;
 import java.net.URI;
+import java.net.URISyntaxExcept

[yocto] [PATCH v2 2/3] Allow '-' in project names

2013-01-10 Thread Ioana Grigoropol
Signed-off-by: Ioana Grigoropol 
---
 .../yocto/bc/ui/wizards/install/OptionsPage.java   |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/install/OptionsPage.java 
b/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/install/OptionsPage.java
index 72aeec2..97d1ad0 100644
--- 
a/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/install/OptionsPage.java
+++ 
b/plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/wizards/install/OptionsPage.java
@@ -313,7 +313,7 @@ public class OptionsPage extends FiniteStateWizardPage {
if (!Character.isJavaIdentifierStart(chars[0]))
return false;
for (int i = 1; i < chars.length; i++)
-   if (!Character.isJavaIdentifierPart(chars[i]))
+   if (!Character.isJavaIdentifierPart(chars[i]) && 
chars[i] != '-')
return false;
return true;
}
-- 
1.7.9.5

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


[yocto] [PATCH v2 1/3] Fix variables hoover & remote file system detection

2013-01-10 Thread Ioana Grigoropol
- initialize bitbake session for recipe:
- when starting a new project, the session environment variables are 
obtained by calling "bitbake -e"
- when a new recipe is created and edited, the session variables should 
be updated with the values obtained from "bitbake -e -b package" => overwrite 
the session with the new one
- if we try to retrive a "remote" file (local file system, remote host) using 
RSE protocol before the system is initialized, null will be returned causing 
every remote operation to fail:
- add exception handling
- make sure that the "remote" FileSystem gets initialized, as well as 
the project connection

Signed-off-by: Ioana Grigoropol 
---
 .../src/org/yocto/bc/bitbake/BBSession.java|4 
 .../src/org/yocto/bc/bitbake/ShellSession.java |   13 -
 .../org/yocto/bc/remote/utils/RemoteHelper.java|7 ++-
 .../org/yocto/bc/remote/utils/RemoteMachine.java   |8 +---
 .../bc/ui/editors/bitbake/BBVariableTextHover.java |   12 +---
 5 files changed, 32 insertions(+), 12 deletions(-)

diff --git a/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/BBSession.java 
b/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/BBSession.java
index 3aa4efe..66a6083 100644
--- a/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/BBSession.java
+++ b/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/BBSession.java
@@ -746,4 +746,8 @@ public class BBSession implements IBBSessionListener, 
IModelElement, Map {
wlock.unlock();
}
}
+
+   public Map getProperties() {
+   return (Map) properties;
+   }
 }
diff --git a/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/ShellSession.java 
b/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/ShellSession.java
index c127c25..38e2557 100644
--- a/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/ShellSession.java
+++ b/plugins/org.yocto.bc.ui/src/org/yocto/bc/bitbake/ShellSession.java
@@ -86,8 +86,12 @@ public class ShellSession {
 
private void initializeShell(IProgressMonitor monitor) throws 
IOException {
try {
-   
RemoteHelper.runCommandRemote(projectInfo.getConnection(), new 
YoctoCommand("source " + initCmd, root.getAbsolutePath(), ""));
-   
RemoteHelper.runCommandRemote(projectInfo.getConnection(), new 
YoctoCommand(exportCmd, root.getAbsolutePath(), ""));
+   if (root != null) {
+   
RemoteHelper.runCommandRemote(projectInfo.getConnection(), new 
YoctoCommand("source " + initCmd, root.getAbsolutePath(), ""));
+   
RemoteHelper.runCommandRemote(projectInfo.getConnection(), new 
YoctoCommand(exportCmd, root.getAbsolutePath(), ""));
+   } else {
+   throw new Exception("Root file not found!");
+   }
} catch (Exception e) {
e.printStackTrace();
}
@@ -103,9 +107,8 @@ public class ShellSession {
 
try {
if (projectInfo.getConnection() != null) {
-   IHost connection = 
RemoteHelper.getRemoteConnectionByName(projectInfo.getConnection().getName());
-   hasErrors = 
RemoteHelper.runCommandRemote(connection, new YoctoCommand(command, 
root.getAbsolutePath() + "/build/", ""));
-   return 
RemoteHelper.getProcessBuffer(connection).getMergedOutputLines();
+   hasErrors = 
RemoteHelper.runCommandRemote(projectInfo.getConnection(), new 
YoctoCommand(command, root.getAbsolutePath() + "/build/", ""));
+   return 
RemoteHelper.getProcessBuffer(projectInfo.getConnection()).getMergedOutputLines();
}
return null;
} catch (Exception e) {
diff --git 
a/plugins/org.yocto.bc.ui/src/org/yocto/bc/remote/utils/RemoteHelper.java 
b/plugins/org.yocto.bc.ui/src/org/yocto/bc/remote/utils/RemoteHelper.java
index c230fd6..e511e06 100644
--- a/plugins/org.yocto.bc.ui/src/org/yocto/bc/remote/utils/RemoteHelper.java
+++ b/plugins/org.yocto.bc.ui/src/org/yocto/bc/remote/utils/RemoteHelper.java
@@ -99,7 +99,11 @@ public class RemoteHelper {
if (host == null) {
// this is a local connection
ISystemRegistry sr = 
RSECorePlugin.getTheSystemRegistry();
-   return sr.getLocalHost();
+   IHost local = null;
+   while (local == null) {
+   local = sr.getLocalHost();
+   }
+   return local;
}
ISystemRegistry sr = RSECorePlugin.getTheSystemRegistry();
IHost[] connections = sr.getHosts();
@@ -237,6 +241,7 @@ public class RemoteHelper

[yocto] [PATCH v2 0/3][eclipse-poky][branch:windows-build]Multiple fixes for windows-build branch

2013-01-10 Thread Ioana Grigoropol
Ioana Grigoropol (3):
  Fix variables hoover & remote file system detection
  Allow '-' in project names
  Reinstate OEFileSystem, OEFile and Ignored Paths for Linux

 plugins/org.yocto.bc.ui/META-INF/MANIFEST.MF   |2 +-
 plugins/org.yocto.bc.ui/plugin.xml |3 +-
 .../src/org/yocto/bc/bitbake/BBSession.java|4 +
 .../org/yocto/bc/bitbake/ProjectInfoHelper.java|   24 ++--
 .../src/org/yocto/bc/bitbake/ShellSession.java |   13 ++-
 .../org/yocto/bc/remote/utils/RemoteHelper.java|7 +-
 .../org/yocto/bc/remote/utils/RemoteMachine.java   |8 +-
 .../src/org/yocto/bc/ui/Activator.java |   45 +---
 .../org/yocto/bc/ui/BCResourceChangeListener.java  |1 -
 .../bc/ui/editors/bitbake/BBVariableTextHover.java |   12 +-
 .../src/org/yocto/bc/ui/filesystem/OEFile.java |  120 
 .../org/yocto/bc/ui/filesystem/OEFileSystem.java   |   50 ++--
 .../bc/ui/filesystem/OEFileSystemContributor.java  |7 +-
 .../org/yocto/bc/ui/filesystem/OEIgnoreFile.java   |   31 -
 .../src/org/yocto/bc/ui/model/ProjectInfo.java |   21 +++-
 .../src/org/yocto/bc/ui/model/YoctoHostFile.java   |  100 
 .../yocto/bc/ui/wizards/install/OptionsPage.java   |3 +-
 .../newproject/CreateBBCProjectOperation.java  |   23 ++--
 18 files changed, 281 insertions(+), 193 deletions(-)

-- 
1.7.9.5

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


[yocto] [PATCH 0/3][eclipse-poky][branch:windows-build]

2013-01-10 Thread Ioana Grigoropol
*** BLURB HERE ***

Ioana Grigoropol (1):
  Fix variables hoover & remote file system detection

yocto (2):
  Allow '-' in project names Signed-off-by: yocto

  Reinstate OEFileSystem, OEFile and Ignored Paths for Linux

 plugins/org.yocto.bc.ui/META-INF/MANIFEST.MF   |2 +-
 plugins/org.yocto.bc.ui/plugin.xml |3 +-
 .../src/org/yocto/bc/bitbake/BBSession.java|4 +
 .../org/yocto/bc/bitbake/ProjectInfoHelper.java|   24 ++--
 .../src/org/yocto/bc/bitbake/ShellSession.java |   13 ++-
 .../org/yocto/bc/remote/utils/RemoteHelper.java|7 +-
 .../org/yocto/bc/remote/utils/RemoteMachine.java   |8 +-
 .../src/org/yocto/bc/ui/Activator.java |   45 +---
 .../org/yocto/bc/ui/BCResourceChangeListener.java  |1 -
 .../bc/ui/editors/bitbake/BBVariableTextHover.java |   12 +-
 .../src/org/yocto/bc/ui/filesystem/OEFile.java |  120 
 .../org/yocto/bc/ui/filesystem/OEFileSystem.java   |   50 ++--
 .../bc/ui/filesystem/OEFileSystemContributor.java  |7 +-
 .../org/yocto/bc/ui/filesystem/OEIgnoreFile.java   |   31 -
 .../src/org/yocto/bc/ui/model/ProjectInfo.java |   21 +++-
 .../src/org/yocto/bc/ui/model/YoctoHostFile.java   |  100 
 .../yocto/bc/ui/wizards/install/OptionsPage.java   |3 +-
 .../newproject/CreateBBCProjectOperation.java  |   23 ++--
 18 files changed, 281 insertions(+), 193 deletions(-)

-- 
1.7.9.5

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


Re: [yocto] Recipes for Xilinx ZC706 (Zynq 7045) and Avnet Zedboard

2013-01-10 Thread Andreas Schweigstill
Dear Philip,

I just checked the Xilinx Linux kernel and found out that all configuration
items for Zynq development boards have been removed, so we can already use a
unified kernel for ZC702/706/770 and Zedboard. DTS files for all flavours are
located in arch/arm/boot/dts.

We just received the first ZC706 board a few days ago.

With best regards,
Andreas Schweigstill

Am Do, 01/10/2013 14:43, hat Philip Balister  geschrieben:
> On 01/10/2013 05:26 AM, Andreas Schweigstill wrote:
> > Hello,
> > 
> > after successfully using the recipe for the ZC702 development board I would
> > like to know if anybody is working on recipes for the Xilinx ZC706 (Zynq 
> > 7045)
> > and Avnet Zedboard.
> 
> 
> Trying 
> 
> I am looking at the best way to do this. My goal is to get one kernel in
> meta-zynq that is pretty good across the public boards and do the board
> selection via the device tree.
> 
> In the meantime, you can build a rootfs for the zc702 and use a kernel
> built outside OE. Do you know if there is support for the zc706 in the
> code on the public Xilnx git repo.
> 
> Philip
> 
> 
> > 
> > Thank you very much in advance!
> > 
> > With best regards,
> > Andreas Schweigstill
> > 
> > ​-- 
> > Dipl.-Phys. Andreas Schweigstill 
> > Schweigstill IT | Embedded Systems 
> > Schauenburgerstraße 116, D-24118 Kiel, Germany 
> > Phone: (+49) 431 530354-35, Fax: (+49) 431 530354-36 
> > Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/ 
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Recipes for Xilinx ZC706 (Zynq 7045) and Avnet Zedboard

2013-01-10 Thread Philip Balister
On 01/10/2013 05:26 AM, Andreas Schweigstill wrote:
> Hello,
> 
> after successfully using the recipe for the ZC702 development board I would
> like to know if anybody is working on recipes for the Xilinx ZC706 (Zynq 7045)
> and Avnet Zedboard.


Trying 

I am looking at the best way to do this. My goal is to get one kernel in
meta-zynq that is pretty good across the public boards and do the board
selection via the device tree.

In the meantime, you can build a rootfs for the zc702 and use a kernel
built outside OE. Do you know if there is support for the zc706 in the
code on the public Xilnx git repo.

Philip


> 
> Thank you very much in advance!
> 
> With best regards,
> Andreas Schweigstill
> 
> ​-- 
> Dipl.-Phys. Andreas Schweigstill 
> Schweigstill IT | Embedded Systems 
> Schauenburgerstraße 116, D-24118 Kiel, Germany 
> Phone: (+49) 431 530354-35, Fax: (+49) 431 530354-36 
> Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/ 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
> 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-ivi][PATCH] consolekit: Remove bbappend as gnome-common is not GPLv3

2013-01-10 Thread Andrei Gherzan
gnome-common's LICENSE fixed with this oe-core commit:
commit 97469db0cba6d21ab1290238225d3fe365931a5c
Author: Ross Burton 
Date:   Tue Oct 30 12:02:45 2012 +

gnome-common: Fix license
gnome-common 2.28 is GPLv2+.  From Christian Persch, upstream:
The licence is presumed GPL2+, although it's not there explicitly. GPL2+
because as far as I could figure out when I tried to, gnome-autogen started in
gnome-core which had a GPL2 COPYING file.

Signed-off-by: Andrei Gherzan 
---
 .../consolekit/consolekit_0.4.5.bbappend   |8 
 1 file changed, 8 deletions(-)
 delete mode 100644 recipes-support-ivi/consolekit/consolekit_0.4.5.bbappend

diff --git a/recipes-support-ivi/consolekit/consolekit_0.4.5.bbappend 
b/recipes-support-ivi/consolekit/consolekit_0.4.5.bbappend
deleted file mode 100644
index 1dccee5..000
--- a/recipes-support-ivi/consolekit/consolekit_0.4.5.bbappend
+++ /dev/null
@@ -1,8 +0,0 @@
-PRINC := "${@int(PRINC) + 1}"
-
-# gnome-common is GPLv3 so we drop this dependency
-# if INCOMPATIBLE_LICENSE contains GPLv3
-python () {
-if (d.getVar("INCOMPATIBLE_LICENSE", True) or "").find("GPLv3") != -1:
-d.setVar("DEPENDS", " ".join(i for i in d.getVar("DEPENDS").split() if 
i != "gnome-common" and i != "gconf" and i != "gconf-native"))
-}
-- 
1.7.9.5

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


[yocto] Recipes for Xilinx ZC706 (Zynq 7045) and Avnet Zedboard

2013-01-10 Thread Andreas Schweigstill
Hello,

after successfully using the recipe for the ZC702 development board I would
like to know if anybody is working on recipes for the Xilinx ZC706 (Zynq 7045)
and Avnet Zedboard.

Thank you very much in advance!

With best regards,
Andreas Schweigstill

​-- 
Dipl.-Phys. Andreas Schweigstill 
Schweigstill IT | Embedded Systems 
Schauenburgerstraße 116, D-24118 Kiel, Germany 
Phone: (+49) 431 530354-35, Fax: (+49) 431 530354-36 
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/ 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] Yocto Bug Trend

2013-01-10 Thread Serban, Laurentiu
Hello,

The dotted line is an inherited artifact from 1.3. It had a relevance at some 
point as far as I know. I will remove it in the next versions.

Br,
Laurentiu

From: Stewart, David C
Sent: Thursday, January 10, 2013 2:55 AM
To: Serban, Laurentiu; yocto@yoctoproject.org
Cc: Wold, Saul; Liu, Song
Subject: Re: Yocto Bug Trend

Thanks - what's the new dotted line in the Weekly Open Bug Trend chart?

From: , Laurentiu Serban 
mailto:laurentiu.ser...@intel.com>>
Date: Tuesday, January 8, 2013 9:08 AM
To: "yocto@yoctoproject.org" 
mailto:yocto@yoctoproject.org>>
Cc: "Wold, Saul" mailto:saul.w...@intel.com>>, David 
Stewart mailto:david.c.stew...@intel.com>>, "Liu, 
Song" mailto:song@intel.com>>
Subject: Yocto Bug Trend

Hello,

The Yocto Bug Trend was updated for ww01.
https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend

Best regards and a happy new year :)

Laurentiu Serban
QA Engineer
Open Source Technology Center
System Software Division Romania
Desk: +40 31 8604742
iNET: 88451042

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


Re: [yocto] I think my kernel image just went back in time...

2013-01-10 Thread Chris Tapp

On 7 Jan 2013, at 16:26, Darren Hart wrote:

> 
> 
> On 12/21/2012 10:17 AM, Tomas Frydrych wrote:
>> On 09/12/12 23:17, Chris Tapp wrote:
>>> In tmp/deploy/images:
>>> 
>>> 1) bzImage had a timestamp of 2012-12-09 21:49 and the file ended
>>> -20121209214459.bin
>>> 
>>> 2) Cleaned the image and the task it contained (to pick up some
>>> changes on rebuild) and deleted the image files (.hddimg, etc.) in
>>> tmp/deploy/images making sure to leave the kernel files intact.
>> 
>> Did you cleansstate it? I find that without cleaning the state kernel
>> image gets always pulled out of sstate rather than properly rebuilt.

It was a while back now and I can't recall for sure. I'm 99.9% certain I used 
-c cleanall on the image.

>> Tomas
> 
> Do you still experience this on the master branch?

I've not had a chance to try and I can't remember the exact steps to reproduce 
it. I've only seen this happen once for the same work-flow.

> -- 
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Technical Lead - Linux Kernel
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Chris Tapp

opensou...@keylevel.com
www.keylevel.com



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


Re: [yocto] meta-cedartrail - where is grub configured for 'install' option?

2013-01-10 Thread Chris Tapp
Hi Darren,

On 7 Jan 2013, at 16:44, Darren Hart wrote:

> On 12/09/2012 01:39 PM, Chris Tapp wrote:
>> I am trying to change the 'install' behaviour for the meta-cedartrail image 
>> so that the installed system has a different grub.cfg file. Is there a file 
>> I can bbappend to achieve this?
>> 
>> image_live.bbclass refers to the 'install' syslinux label that triggers the 
>> install, but I've not been able to get from this to how/where grub.cfg is 
>> created.
>> 
> 
> This is currently rather crudely implemented here:
> 
> meta/recipes-core/initrdscripts/files/init-install.sh
> 
> A better deployment mechanism is something being discussed and which
> should make this more configurable.
> 
> For now, you could bbappend initramfs-live-install_1.0.bb and replace the
> init-install.sh script with your own.

Thanks. I've already got to look at that script anyway as it fails to install 
to an internal USB drive on a DN2800-MT board as (I think) it isn't waiting 
long enough for it to enumerate when booting the 'install' image.

> -- 
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Technical Lead - Linux Kernel

Chris Tapp

opensou...@keylevel.com
www.keylevel.com



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