The remote tools related changes are merged to eclipse-poky master plus the
following patch:
http://git.yoctoproject.org/cgit/cgit.cgi/eclipse-poky/commit/?id=ff4ccb4d65243f2a28eb89c72e9b425702b6c3aa
For headless build.
Thanks,
Jessica
-Original Message-
From: yocto-boun...@yoctoprojec
Hi Atanas,
All the cmake related patches have been merged to eclipse-poky master. Also,
can you provide some detailed information regarding how to test the feature so
QA can add adequate test cases in the existing eclipse plug-in testing.
Thanks,
Jessica
-Original Message-
From: yoct
merged. Thanks!
-b
On Fri, May 24, 2013 at 8:52 AM, Stefan Stanacar
wrote:
> RunSanityTests and RunPreamble weren't passing kwargs to
> ShellCommand so timeout was ignored.
> For RunSanityTests I've changed the default to 1200 which should be
> enough in most cases, but I've updated one build wh
RunSanityTests and RunPreamble weren't passing kwargs to
ShellCommand so timeout was ignored.
For RunSanityTests I've changed the default to 1200 which should be
enough in most cases, but I've updated one build where
two images are actually tested (btrfs and ext4)
Signed-off-by: Stefan Stanacar
-
From: Atanas Gegov
Simplified the calling of the addNatures(...)
method. Variables describing the nature of the
project are not more local for the process(...)
method, but private object members.
---
.../ide/wizard/NewYoctoProjectTemplateProcess.java | 29 ++--
1 file changed,
From: Atanas Gegov
Resolved whitespace issues which popped up while
renaming the NewYoctoProjectTemplateProcess. Also
added some missing "//$NON-NLS-1$" declarations.
---
.../ide/wizard/NewYoctoProjectTemplateProcess.java | 37 +++-
1 file changed, 21 insertions(+), 16 deletion
From: Atanas Gegov
The original name of the class had two drawbacks:
firstly, it suggested that it applies only for C
projects and secondly, it did not state that this
is a process.
---
plugins/org.yocto.sdk.ide/plugin.xml |2 +-
.../sdk/ide/wizard/NewYoctoCProjectTemplate.java
From: Atanas Gegov
CMake projects will use additional variables in
the environment. They have to be set if the Yocto
settings are changed.
---
.../src/org/yocto/sdk/ide/utils/YoctoSDKUtils.java |7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git
a/plugins/org.yocto.sdk.id
From: Atanas Gegov
This enables creating projects with the introduced
CMake nature. What is still upcoming are the
template projects and a corresponfig CMake
ManagedBuilder (CMake build toolchain for
Eclipse).
---
.../ide/natures/YoctoSDKCMakeProjectNature.java| 72
..
From: Atanas Gegov
This nature is intended for Yocto projects that
use CMake as a build system. It requires the
YoctoSDKProjectNature and can be used by upcoming
CMake project templates. It excludes the
YoctoSDKAutotoolsProjectNature, e.g. their
relation in plugin.xml is declared as
"one-of-natur
From: Atanas Gegov
Added an extra variable to the templates and the
creating process to prepare them for the new CMake
nature.
---
plugins/org.yocto.sdk.ide/plugin.xml |4
.../sdk/ide/wizard/NewYoctoCProjectTemplate.java |2 ++
.../EmptyCAutotoolsProject/template.xml
From: Atanas Gegov
Hi,
This patch series introduces a YoctoSDKCMakeProjectNature as a new
nature for CMake-based Yocto Projects in the IDE. It requires the
basic YoctoSDKProjectNature and is an alternative to the
YoctoSDKAutotoolsProjectNature.
This does not affect the currently existing Autoto
Hi Jessica,
Yes, this patch series indeed relies on the previous RFC patches: [yocto]
[eclipse-poky][RFCv2 0/7] Introducing a YoctoSDKCMakeProjectNature. I will
resend the series as PATCH.
Best regards,
Atanas
On Thu, May 23, 2013 at 11:50 PM, Zhang, Jessica wrote:
> Hi Atanas,
>
> Seems this
On Friday 24 May 2013 10:27:43 Paul Eggleton wrote:
> On Thursday 23 May 2013 21:55:13 Hartmut Behrens wrote:
> > On Thu, May 23, 2013 at 6:53 PM, Hartmut Behrens
> >
> > wrote:
> > > I also tried INSANE_SKIP_${PN} += "dev-so" without any luck.
> > >
> > > Might you know how to solve this?
> >
On Thursday 23 May 2013 21:55:13 Hartmut Behrens wrote:
> On Thu, May 23, 2013 at 6:53 PM, Hartmut Behrens
> wrote:
> > I also tried INSANE_SKIP_${PN} += "dev-so" without any luck.
> >
> > Might you know how to solve this?
>
> So including INSANE_SKIP_${PN} = "dev-deps" does the trick.
>
> I tr
On 23 May 2013 19:51, Hans Beckérus wrote:
> However, I have completely changed path now ;) I think the root cause
> of this entire problem is that the package is constructed wrong. Since
> these .so files are modules, we need to tell libtool so it does not
> create the regular versioned lib file
- removed all plugin dependencies to the RSE API & kept only the ones needed
for GUI actions and Terminal views
Signed-off-by: Ioana Grigoropol
---
.../org.yocto.sdk.remotetools/META-INF/MANIFEST.MF | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/plugins/org.yoc
- org.yocto.sdk.ide clean up - remove unused classes
Ioana Grigoropol (2):
Remove unused TCFTerminalConnectors
Remove all plugin dependencies to RSE APi from remote tools plugin
.../org.yocto.sdk.remotetools/META-INF/MANIFEST.MF | 10 +-
.../remotetools/views/TCFTerminalConnector.java|
- removed TCFTerminalConnector and TCFTerminalConnectorImpl since there are no
usages of this classes
Signed-off-by: Ioana Grigoropol
---
.../remotetools/views/TCFTerminalConnector.java| 49 --
.../views/TCFTerminalConnectorImpl.java| 98
2 files
- move TerminalHandler to separate plugin since it performs actions that are
best suited for remote utilities
- remove TerminalHandler from remotetools plugin
- modify org.yocto.sdk.remotetools to use implementation from
org.yocto.remote.utils
Signed-off-by: Ioana Grigoropol
---
.../org.yocto.
- common helper is better suited to org.yocto.remote.utils since it is used for:
- running commands
- displaying error dialogs
- remove common helper from remote tools plugin and add it to a separated plugin
- modify org.yocto.sdk.remotetools to use implementation from
org.yocto.remote.utils
- ShellSession is used as a wrapper for a remote shell used for running
commands on a remote machine with bitbake environment
- move ShellSession org.yocto.remote.plugin since it is part of remote utilities
- remove shell session class from remotetools plugin
- modify org.yocto.sdk.remotetools to
- move RSEHelper to newly created separate plugin org.yocto.remote.utils
- clean-up RSEHelper code by removing all unused methods
- moved message strings that are relevant for this plugin to the corresponding
class
- modify remotetools plugin to use RSEHelper from org.yocto.remote.utils
- add plug
- RemoteShellExec is a wrapper over a remote executiong of a command in a shell
and it belongs to org.yocto.remote.utils plugin
- remove RemoteShellExec from remotetools plugin and add it to
org.yocto.remote.utils
- modify org.yocto.sdk.remotetools to use implementation from
org.yocto.remote.uti
Signed-off-by: Ioana Grigoropol
---
plugins/org.yocto.remote.utils/.classpath |7 +++
plugins/org.yocto.remote.utils/.project| 28 +
.../.settings/org.eclipse.jdt.core.prefs |7 +++
.../org.yocto.remote.utils/META-INF/MANIFEST.MF| 10
pl
- initial commit & populate for remote utils common plugin
Ioana Grigoropol (6):
Initial commit for separate remote utilities plugin
Move RSEHelper to a separate plugin
Move RemoteShellExec to separate plugin
Move ShellSession to org.yocto.remote.utils separate plugin
Move CommonHelper t
On Thursday 23 May 2013 23:20:06 Nicolas Dechesne wrote:
> On Thu, May 23, 2013 at 10:51 PM, LIU Yang (MM) > wrote:
> >
> > I am first time coming here for help on Yocto project with Qt5, I have two
> > questions/problems when I tried to bitbake a recipe in our layer.
>
> sorry to hijack (sl
Hi Jessica,
These changes can be applied independently on the windows-build branch, and I
have sent the patches to make sure that this part works properly before merging
them to a common remote plugin assuming that everything works.
Since I will porting these utilities to the remote plugin, I th
28 matches
Mail list logo
