Age | Commit message (Collapse) | Author |
|
[YOCTO #5409]
Signed-off-by: Jessica Zhang <jessica.zhang@intel.com>
|
|
Signed-off-by: Jessica Zhang <jessica.zhang@intel.com>
|
|
Signed-off-by: Johann Draschwandtner <johann.draschwandtner@windriver.com>
Signed-off-by: Jessica Zhang <jessica.zhang@intel.com>
|
|
[yocto#5378]
Signed-off-by: Jessica Zhang <jessica.zhang@intel.com>
|
|
setting. e.g. LatencyTopHandler [yocto #5328]
Signed-off-by: Jessica Zhang <jessica.zhang@intel.com>
|
|
environment is correct [yocto #5330]
Signed-off-by: Jessica Zhang <jessica.zhang@intel.com>
|
|
If the system is not able to run the command
"cmake", the user is prompted with a MessageDialog
to check the correctness of the cmake
installation.
|
|
Signed-off-by: Jessica Zhang <jessica.zhang@intel.com>
|
|
[Yocto #4223]
Signed-off-by: Adrian Dudau <adrian.dudau@enea.com>
|
|
Signed-off-by: Jessica Zhang <jessica.zhang@intel.com>
|
|
- the parameters for runnin crosstap are populated before the window is actually open so they remain null
-> retrieve them after the window has closed & run the script
Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@intel.com>
|
|
- powertop package has been updated from 1.13 to 2.3 and the command line options have changed
- option '-d' no longer exists -> option --debug seems to its successor
- option '-t' is not documented, but still works -> changed to --time, which is documented
[Yocto #4830]
Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@intel.com>
|
|
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 <timo.mueller@bmw-carit.de>
|
|
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 will also contain
the project specific profile.
If the project specific profile is not yet defined for the selected
project, the button will be greyed out.
Signed-off-by: Timo Mueller <timo.mueller@bmw-carit.de>
|
|
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 <timo.mueller@bmw-carit.de>
|
|
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 <timo.mueller@bmw-carit.de>
|
|
Move project specific methods to the new util class to allow public
usage of theses methods.
Signed-off-by: Timo Mueller <timo.mueller@bmw-carit.de>
|
|
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 <timo.mueller@bmw-carit.de>
|
|
Signed-off-by: Timo Mueller <timo.mueller@bmw-carit.de>
|
|
On initial setup the profile form is populated with the values from
the previously selected target profile. This allows the user to
quickly make project specific adaptions of an existing profile.
Signed-off-by: Timo Mueller <timo.mueller@bmw-carit.de>
|
|
- when ok is pressed, the system tap window is resized in stead of running the script
- this is caused by the fact that the window is opened twice and only the second call is taken into consideration
[Yocto #4598]
Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@intel.com>
|
|
Signed-off-by: Jessica Zhang <jessica.zhang@intel.com>
|
|
Moved public methods from the YoctoSDKUtils
class that are used locally in just one other
class. This should reduce the complexity of the
YoctoSDKUtils class and decrease unneeded coupling
between classes.
|
|
Removed methods from the YoctoSDKUtils class that
are not used.
|
|
Declared some methods, that are only privately
used, as private. This simplifies the public API
of the YoctoSDKUtils class.
|
|
The method splitString(...) is used only locally.
Removed from the YoctoSDKUtils in order to
simplify the overpopulated YoctoSDKUtils
class.
|
|
The creation of the remote debug and qemu
launchers is now decoupled from the method
setEnvironmentVariables(...). This also fixes a
bug where the remote debug launcher is not
correctly created because at the time of the call
not all relevant Yocto natures are added to the
project.
|
|
The creation of the RemoteDebug launcher and the
Qemu launcher is extracted in an own method. The
creation of both launchers should be decoupled
from the setting of the project environment. This
is done in the next patch.
|
|
Extracted a method that gets the full path of the
environment-setup-* file.
|
|
- when displaying MessageDialogs an error occurs due to illegal thread accessing GUI classes
- in order to fix this, a new DialogRunnable is used, that will use invoke synchronous to display the message dialog
[Yocto #4585]
Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@intel.com>
|
|
Signed-off-by: Jessica Zhang <jessica.zhang@intel.com>
|
|
- removed all plugin dependencies to the RSE API & kept only the ones needed for GUI actions and Terminal views
Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@intel.com>
|
|
- removed TCFTerminalConnector and TCFTerminalConnectorImpl since there are no usages of this classes
Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@intel.com>
|
|
- 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 <ioanax.grigoropol@intel.com>
|
|
- 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
Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@intel.com>
|
|
- 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 use implementation from org.yocto.remote.utils
Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@intel.com>
|
|
- 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.utils
Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@intel.com>
|
|
- 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 plugin resources need for RSEHelper
Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@intel.com>
|
|
Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@intel.com>
|
|
Made the CMake extension plugin a part of the
Yocto sdk feature.
|
|
The Yocto CMake projects are built for more
clarity in a Debug folder and not in the source
tree. The binary is therefore not inside the src
folder but in the Debug folder.
|
|
Added a C and C++ HelloWorld template projects for
CMake. The both have the new CMake project type
and are therefore built with the CMake toolchain.
|
|
Defined a projectType that uses the new project
category. It takes the CMake toolchain to build
the project in a debug configuration. It is
possible to add further configurations (e.g.
"Release" with other option settings for the
configure tool).
|
|
Yocto CMake template projects should use this
category. It appears in the new project wizard
additionally to the existing category "Yocto
Project ADT CMake Project".
|
|
The CMake build toolchain uses the previously
defined builder and the cmake configure tool. The
rest of the tools are the standard gnu compiler/
linker for C and C++.
|
|
The generation of the toolchain.cmake file happens
just before the exectuion of the configure job.
The current environment of the project is used to
set the values in the toolchain.cmake file.
|
|
Defined a ManagedBuilder and a corresponding
Makefile generator class. In order to create
Makefiles the cmake configure job is run. By now
it is assumed that the required toolchain.cmake
file is provided by the user. The next patch adds
the toolchain.cmake generation.
|
|
The job executes the configure step of the project
using the "cmake" command. The output is
presented in a new console.
|
|
This job will execute the configure step for the
CMake projects. It uses the command defined by the
CMake tool ("cmake") and gets the provided options
from the user to assemble the command line.
|
|
This methods creates a key-value map from the
project environment. It can be used to provide
this environment to new processes.
|