summaryrefslogtreecommitdiffstats
path: root/bitbake
Commit message (Collapse)AuthorAgeFilesLines
* bitbake: build/siggen.py: Avoid removing too many stamps when cleaningRichard Purdie2012-11-282-6/+7
| | | | | | | | | | | | | | | | The "*" part of the mask is to ensure we clean both any stamp, and any setscene varient. It turns out we would also trample other tasks, e.g. do_package_write could trample do_package_write_rpm. do_package also tramples do_package_write_* but this is less of an issue since the other tasks depend on it. Rather than use the wildcard, we can just use a list instead. [YOCTO #3484] (Bitbake rev: c14d831ea3f625e9a47266a0c4e6deefc924ca5a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: when BBLAYERS_NON_REMOVABLE is not set hob shows an errorCristiana Voicu2012-11-281-1/+1
| | | | | | | (Bitbake rev: a40ceda3b349c4461f4b7bc0e18cd966fff5e3cf) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2/wget: Fix for mixed-up wget commandsCristian Iorga2012-11-261-2/+2
| | | | | | | | | | | | | | | | | | wget commands for check and resume were mixed-up, leading to the following issues: 1. long running "NOTE: Preparing runqueue" reason: objects were downloaded, not spidered on the mirror 2. Failing network test in Build Appliance, because wget 1.14 (in use in BA) will fail if a file already exists. During the network connectivity test, index.php file was actually downloaded, not spidered (checked for existence on yoctoproject.org website), leading to wget failure. (Bitbake rev: d7a5185cae975eaca50a9785c6605e895dc7bb51) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2/local: Fix bug introduced by expression ambiguityRichard Purdie2012-11-261-1/+1
| | | | | | | | | The last changes introduced an error in some of the logic. Add brackets to clarify the meaning of the expression and fix certain build failures. (Bitbake rev: 87aea65bd5d553bd0495b0f1efe6d41d0bb2810f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: make some layers non removableCristiana Voicu2012-11-263-10/+10
| | | | | | | | | | | | | | - there are some layers which cannot be removed; so ,I have used a new variable called BBLAYERS_NON_REMOVABLE located in bblayers.conf, which contains those layers which cannot be deleted - "meta-hob" layer is added to this variable in hob code, like it's added to BBLAYERS var [YOCTO #3176] (Bitbake rev: 05da1621eed4c6201cd65372d229f63ea8a44b6e) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Update version to 1.17.0Richard Purdie2012-11-262-2/+2
| | | | | | (Bitbake rev: cc7fdbdc607df530f5539b162831bf9998eb48d8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2: Avoid using FILESDIR in unpackRichard Purdie2012-11-262-7/+11
| | | | | | | | | | | | | Currently there is code which uses FILESDIR in unpack to ensure parent directories are created, leading to differing behaviour depending on which search path is used to locate the directory. This change standardises the code and takes the data from the fetcher in question meaning we can standardise the code and deprecate FILESDIR. (Bitbake rev: 1cccb3bd01ed82e4978acfef0fda1bd797eef72a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2/local: Improve handling of wildcard matchesRichard Purdie2012-11-261-1/+6
| | | | | | | | | | | | Currently wildcard matches end up working by FILESDIR being defined in the metadata to a default of "." in FILESPATH which is hacky at best. This patch adds the behaviour into the fetcher so its at least slightly more explicit. (Bitbake rev: 07b5f84133ac79aac4e939ea5f24390ad7f940a5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: knotty/msg: Avoid usage of curses initscr/endwin to avoid terminal ↵Richard Purdie2012-11-252-15/+5
| | | | | | | | | | | | corruption Using curses initscr/endwin causes screen corruption if for example you suspend bitbake and resume it. This changes the code to use a less invasive approach to determining colour availability on the terminal. (Bitbake rev: 4548a8f037eaf8d47a77052acc3e9ec264ac41e0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob/builder: Don't rerun sanity checksConstantin Musca2012-11-251-2/+8
| | | | | | | | | | | Run the sanity check only once [YOCTO #3377] (Bitbake rev: 0db80d57d4d2b1bb97375444c439827450ff33d1) Signed-off-by: Constantin Musca <constantinx.musca@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: showing when build fails because out of disk spaceCristiana Voicu2012-11-254-7/+43
| | | | | | | | | | | | -to enable this in hob, first you have to enable this in bitbake using BB_DISKMON_DIRS and/or BB_DISKMON_WARNINTERVAL vars -created "restart the build" action on the build_fail_top_bar [YOCTO #3357] (Bitbake rev: 964ac25d153ff4da144963289a32066db0e28b89) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: server/process.py: Change timeout error handlingRichard Purdie2012-11-211-2/+2
| | | | | | | | | | | | | | | | | | | In normal usage, we never hit the timeout issue. If we do, it becomes obvious that the current error handling is not good enough. The request may have made it to the server and the answer will get queued. This means the next command may get the return value from the previous command with suitably puzzling results. Without rewriting large sections of code, its not possible to avoid this problem. It is better to increase the timeout to several seconds giving the server a chance to respond and if it does timeout, hard exit since recovery is not possible with the code base today. I'd be happy to see the structure of this code improved but this quick fix at least stops corrupted builds from happening which has to be a good thing. (Bitbake rev: 410c11dd10736873f2dc587fbe9119c38831e693) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: knotty: Colorize knotty interactive console outputSeth Bollinger2012-11-202-1/+48
| | | | | | | | | | | | | | | Add bold color output to log level name and standard color output to log msg when bitbake is run from an iteractive console. Color output is only enabled if the terminal supports color. Used Jason Wessel's recommendation for transparency on verbose, note and plain. (Bitbake rev: 2734240da2cc150f811129a6adf6eb4b2161b204) Signed-off-by: Seth Bollinger <seth.boll@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: warnings during the build should be displayed in the Issues tabCristiana Voicu2012-11-202-2/+7
| | | | | | | | | | | Any issues encountered during the build (fatal or not) is displayed in the Issues tab, and the total number of issues is changed. [YOCTO #3376] (Bitbake rev: 64c662ab7f09c2e867445e8ba21ea63ae014d45b) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: runqueue: Allow partial setscene task coverageRichard Purdie2012-11-201-11/+72
| | | | | | | | | | | | | | | | | | | | | | | | When the setscene code was originally written it was thought that we'd allow "partial" coverage. For example, if we just want to build the target "bash:do_populate_sysroot" and its available from sstate, it makes no sense to install gcc-cross's sstate package as its simply not needed. Due to various other issues in the codebase, this functionality was disabled/removed to allow the setscene code and sstate to stabilise and allow us to concentrate on other problems. The time has now come to enable "partial" coverage. There are two major changes in this patch: a) Creation of an unskippable list. This lists direct dependencies of build targets and hence things that cannot be skipped. b) Addition of a handler which looks at a given setscene target and what depends on it and then decides whether its necessary. (Bitbake rev: 2a937cd6a6c3110030b40bc4d85e349b85cb4db7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: parse/cache/cooker: Preserve order in the file inclusion listRichard Purdie2012-11-203-8/+7
| | | | | | | | | | | | The data returned by get_file_depends() may me used in contexts like checksums where order is important. The current usage of sets means that some of the checksums can change in circumstances they should not. This patch changes to use lists, thereby removing the problem. (Bitbake rev: a44285fc4109236ab89f7aad0a1fc9220eec19b6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: knotty: kill duplicated import of 'time'Christopher Larson2012-11-141-1/+0
| | | | | | | | | The duplicated import could result in an UnboundLocalError. (Bitbake rev: a098cebd5c33ebd704efd35d9e655262283cbe1f) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: print clear message for "bitbake -e ASSUME_PROVIDED"Robert Yang2012-11-131-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | "bitbake -e ASSUME_PROVIDED" should fail, but the error message wasn't clear enough in the past: $ bitbake -e bzip2-native [snip] ERROR: Command execution failed: Traceback (most recent call last): File "/buildarea/lyang1/poky/bitbake/lib/bb/command.py", line 94, in runAsyncCommand commandmethod(self.cmds_async, self, options) File "/buildarea/lyang1/poky/bitbake/lib/bb/command.py", line 323, in showEnvironmentTarget command.cooker.showEnvironment(None, pkg) File "/buildarea/lyang1/poky/bitbake/lib/bb/cooker.py", line 325, in showEnvironment fnid = taskdata.build_targets[targetid][0] KeyError: 0 [snip] With this patch, the massage will be: [snip] ERROR: bzip2-native is in ASSUME_PROVIDED ERROR: Command execution failed: Exited with 1 Summary: There were 2 ERROR messages shown, returning a non-zero exit code. [YOCTO #3392] (Bitbake rev: f31447dac92454c822d4ebb7dd48e96c6c69dde4) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: hob was freezing because it doesn't receives well the log fileCristiana Voicu2012-11-131-1/+1
| | | | | | | | | | | -after pressing "build image" button, hob was freezing because it didn't receive well the log file [YOCTO #3398] (Bitbake rev: e3619e34d43c3f7725fc83c362d8cbd07e153ebe) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: command: add error to return of runCommandChristopher Larson2012-11-017-65/+112
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, command.py can return an error message from runCommand, due to being unable to run the command, yet few of our UIs (just hob) can handle it today. This can result in seeing a TypeError with traceback in certain rare circumstances. To resolve this, we need a clean way to get errors back from runCommand, without having to isinstance() the return value. This implements such a thing by making runCommand also return an error (or None if no error occurred). As runCommand now has a method of returning errors, we can also alter the getCmdLineAction bits such that the returned value is just the action, not an additional message. If a sync command wants to return an error, it raises CommandError(message), and the message will be passed to the caller appropriately. Example Usage: result, error = server.runCommand(...) if error: log.error('Unable to run command: %s' % error) return 1 (Bitbake rev: 717831b8315cb3904d9b590e633000bc897e8fb6) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: providing details about process state through porgress barCristiana Voicu2012-11-013-14/+9
| | | | | | | | | | -small changes to the text of the progress bar when parsing recipes [YOCTO #3282] (Bitbake rev: 90c0dfc39c3ce13e53c7c91168dc3401f7df476b) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake/server: Remove dead console log codeRichard Purdie2012-11-014-10/+6
| | | | | | | | This code is dead and doesn't do anything so lets remove it. (Bitbake rev: 8d45739f49618757a5d7d79782deda355e3981ec) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: cooker.py: Don't dump the environment into the console log fileRichard Purdie2012-11-011-0/+2
| | | | | | | | | | | | | Dumping the environment data into the console log files directory is invariably not what the user wants or expects and leads to confusion when looking at the log directory. This change forces the logs to be disabled by default when using the -e option. (Bitbake rev: 5d825b31d1133e41d3982db1b94f6a30a6fb99f7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: uihelper: Set update flag when start event encounteredRichard Purdie2012-10-301-0/+1
| | | | | | | | | Its a minor correctness detail but the update flag should be set when Start events are encountered. (Bitbake rev: 96683ed68e11672ff22fb4a291d2628676c136f0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: knotty: Ensure last tasks are disaplyed correctly in the footerRichard Purdie2012-10-301-1/+1
| | | | | | | | | | | There was an issue where the last tasks run by bitbake would not correctly get displayed in the knotty footer. This was due to the total count including active tasks. This change ensures the footer is displayed if the are any running tasks. (Bitbake rev: d787e4efc106589811651bc18ca48d5223443b95) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: reordering the layers in the Hob Layers dialogCristiana Voicu2012-10-271-1/+41
| | | | | | | | | | | | | -since the order of the layers can potentially impact the build outcome, users should be able to reorder the layers within the layers dialog; -used TreeView Drag and Drop [YOCTO #3270] (Bitbake rev: 2bd9a00facb90f7d76a9bdaa86ca765fb2159e71) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob/hig: Hob doesn't save properly proxy settingsCristian Iorga2012-10-271-16/+1
| | | | | | | | | | | | | | | | | | | User introduced proxy settings were not saved when a proxy details input dialog was opened. The proxy settings were lost upon return, and restored from the previously stored one. Also: Code cleanup: details_cb() function duplicate definition removed Fixes [YOCTO #3240] (Bitbake rev: aa64b2e472f8a9713e3dc25647aa2cae474e2622) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: during recipe parsing, progress bar text provides details ↵Cristiana Voicu2012-10-271-2/+8
| | | | | | | | | | | | | | | about the process state - indicating on progress bar that hob has gone from parsing recipes to "Generating dependency tree"; this will provide some visibility of what has caused the "stop" button state to change [YOCTO #3282] (Bitbake rev: d964d04ff1f59a590bd3ab5430517d79e92536d0) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: add a progress indicator when you select 'view log'Cristiana Voicu2012-10-275-3/+136
| | | | | | | | | | | | | | | | | | | | - created a new file named "hobthreads.py", defining a thread for opening the log file in a subprocess using subprocess module; in the future I think we will add some other threads here, to implement some other performance issues - on "builddetailspage", "packageselectionpage" and "imagedetailspage" I have changed the manner for opening the log file; it uses the thread to open the file, and on main thread it creates a dialog to show a progress bar, which pulses till the file is open - this was added because when the log file is big, it takes time to be opened; on the dialog you can use "Cancel" button to terminate the process initiated to open the file [YOCTO #2997] (Bitbake rev: 165362a63f085991b6bab63ab90a0c7b9bf6b784) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: hob/builder: Hob crashes because of bad initCristian Iorga2012-10-251-0/+1
| | | | | | | | | | | | | | | Image selection is not properly initialized to none, and it used before having a chance to have a value. Due to dynamic nature of Python, variable is used before it exists, in this case. This causes a crash. Bug introduced during the fix of [YOCTO #3228] Fixes [YOCTO #3334] (Bitbake rev: 1c540541c5397c38dca880a79df9ebfcda576d4c) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob/settings: add a scroll bar for the box with mirrorsCristiana Voicu2012-10-241-3/+10
| | | | | | | | | | | | - added a scroll bar in the shared state tab from settings - added a signal on it, so when you add a new mirror, it will auto-scroll to the end of the list [YOCTO #3229] (Bitbake rev: 00afd6a25c0cc0a4fcddd9f7c26a17ef6c47cbd2) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: hob/builder: Image selection is remembered while changing ↵Cristian Iorga2012-10-241-1/+0
| | | | | | | | | | | | | | | adv settings Image selection is remembered correctly even after advanced settings have been changed. Selected image was reset even when it was not the case. Fixes [YOCTO #3228] (Bitbake rev: 93fb0a2c56100b2bbc8769af9ae2343c05e72193) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob/builddetailspage: set "Log" page as defaultCristiana Voicu2012-10-241-0/+1
| | | | | | | | | | | | - when you do a build you should see "Log" page, not "Build configuration" page [YOCTO #2569] (Bitbake rev: 431cb80d4d5222f832f6141b8578291f2f14a131) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob/imageconfigurationpage: progress bar shows when recipe parsing ↵Cristiana Voicu2012-10-241-3/+9
| | | | | | | | | | | | | is stopped -when the recipe parsing process is stopped, the progress bar shows "Stopping recipe parsing" [YOCTO #3259] (Bitbake rev: d20626bd717bb8f5cfd73b91337af880198db247) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: hob/hobwidget: "Brought in by" column is now displayed ↵Cristian Iorga2012-10-243-4/+10
| | | | | | | | | | | | | | | correctly In "Edit Recipes" and "Edit packages" pages, the "Brought in by" column is displayed correctly, with the right number of additional packages and a proper title. Fixes [YOCTO #2195]. (Bitbake rev: 4d1d3e5a54eb718e2eee02f734d929f15ccf99ce) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: stop build without percentage shownAndrei Dinu2012-10-242-1/+6
| | | | | | | | | | | | added a method in progressbar.py that doesn't update the percentage in the progress bar shown in hob. the call of the method is done in builder.py. (Bitbake rev: 7ab5775fceda1055b86bdc3313fc4bf928bf5155) Signed-off-by: Andrei Dinu <andrei.adrianx.dinu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: change behavior for "cancel" button from the Recipe selection pageCristiana Voicu2012-10-243-0/+5
| | | | | | | | | | | -when returned to the Image configuration page, after canceling on the Recipe selection page, the image selected previously is now shown corectly [YOCTO #3205} (Bitbake rev: 0a755026661a18ae386eb64b807e9e9e8f0dfe4c) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: image size displayed wrong size in edit packages screenAndrei Dinu2012-10-241-2/+2
| | | | | | | | | | | | | size_str = '%.1f' % (size*1.0/(1024*1024)) + ' MB' from /bitbake/lib/bb/ui/crumbs/hobpages.py file transformed the size in MB. In our file it was again multiplied by 1024 instead of doing a division by 1024, which brought a faulty size on the edit packages screen. (Bitbake rev: 7dcea3884a45973ae332695dc8a53814b701151f) Signed-off-by: Andrei Dinu <andrei.adrianx.dinu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: event/hob: Add a button for network tests in the proxy settingsBogdan Marinescu2012-10-244-71/+273
| | | | | | | | | | | | | | | | | This patch allows the user to check the network connectivity in the "Proxy" page ("Settings" dialog) by adding a button which provides this functionality. It also disables retrigerring sanity checks if the proxy values are changed, since now the proxy checks are explicit. Note that this patch depends on a patch in oe-core ("sanity.bbclass: trigger network tests explicitly"). It will not work properly if the patch in oe-core is not merged. [YOCTO #3026] (Bitbake rev: cb1354d29c0be27aee57b9783c724457ef6725fb) Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob-toolchain: task-core-standalone-sdk-target renamed to ↵Andrei Dinu2012-10-101-1/+1
| | | | | | | | | | | | packagegroup-core-standalone-sdk-target This change also applies to task-core-standalone-sdk-target-dbg and resolves build failures caused by the missing packages. (Bitbake rev: 4cd0200e96fb282980a945b80af641a6e022e0b4) Signed-off-by: Andrei Dinu <andrei.adrianx.dinu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob/imageconfigurationpage: a 'hob-image' appears listed in the ↵Cristiana Voicu2012-10-081-0/+1
| | | | | | | | | | | | | base image combo box -remove this image from image combo box [YOCTO #3230] (Bitbake rev: 90fd57ee3cb2856c10bda1f5af4879d2b7cf2668) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob/hobeventhandler: Describe the runCommand failure exceptionConstantin Musca2012-10-081-1/+3
| | | | | | | | | [YOCTO #1245] (Bitbake rev: 17f28f09452f70dfb67fce9a397a99deec84dfe5) Signed-off-by: Constantin Musca <constantinx.musca@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob/hobeventhandler: Throw an exception if runCommand failsConstantin Musca2012-10-041-1/+6
| | | | | | | | | | | | - throw a Hob exception if runCommand returns 'Busy' or 'No such command' [YOCTO #1245] (Bitbake rev: 5a8e3baa66f845599a616f080a7efce81ecda631) Signed-off-by: Constantin Musca <constantinx.musca@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob/imagedetailspage: disable the deploy tool for qemu machinesConstantin Musca2012-10-031-0/+2
| | | | | | | | | | | | - qemu images cannot be deployed to hardware, even if live images (hddimg and iso) files are created [YOCTO #3196] (Bitbake rev: 001b1c439ffa450cb8728b0fa9469fed63ae9bed) Signed-off-by: Constantin Musca <constantinx.musca@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob/settings: alignment and spacing fixes on "Shared state" tabCristiana Voicu2012-10-031-29/+43
| | | | | | | | | | | -alignment and separation on vertical and horizontal axis -change controls width [YOCTO #3188] (Bitbake rev: a84c466eae7c2616c041faf930163f23834f0685) Signed-off-by: Cristiana Voicu <cristiana.voicu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob/image_details/run_image: Kernel must be setIoana Grigoropol2012-10-031-2/+2
| | | | | | | | - when displaying image details, even if the kernel information is not shown, the kernel value must be set (if dealing with qemu) otherwise running the image will throw an error (Bitbake rev: 334125a98ecb8a938aee4bc530205ad75099361c) Signed-off-by: Ioana Grigoropol <ioanax.grigoropol@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2: raise an exception if user specifies protocol=git with http://Paul Eggleton2012-10-031-0/+3
| | | | | | | | | | | | It is a common mistake to use http:// and protocol=git when attempting to fetch from a git repository using the http protocol; if this is detected then throw an error explaining that you need to use git:// with protocol=http instead. (Bitbake rev: 5bc4930c1638db16bcd5f9c8cfc4081f9ffc192b) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: providers.py: Fix PREFERRED_VERSION containing epochsRichard Purdie2012-10-031-1/+1
| | | | | | | | | | | | | For some reason the code calls int() on the epoch component of any PREFERRED_VERSION. Since this is compared against strings, the comparison would always fail. This removes the stray cast and allows epochs in preferred_version to work correctly. [YOCTO #3187] (Bitbake rev: 117b47553970fc5307374cbf500744b7c302efb4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob/hobpages: Generate the title label every timeConstantin Musca2012-10-021-0/+1
| | | | | | | | | | | | - the title label is destroyed at page switching (that's why we need to generate it every time) [YOCTO #3195] (Bitbake rev: d6d991c08f66cf9ab27c53075109212ea9129380) Signed-off-by: Constantin Musca <constantinx.musca@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: Improved behavior for error reporting windowCristian Iorga2012-10-021-0/+1
| | | | | | | | | | | | Scrollbars have now an automatic behavior, depending on the error's text size and error window size. Fixes [YOCTO #2983] (Bitbake rev: 0c0a25672498520fb2c46164f08959dda83c61e0) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>