Bug 9616 - yocto-bsp wizard sources the Build location folder every time the field loses focus
Summary: yocto-bsp wizard sources the Build location folder every time the field loses...
Status: RESOLVED WONTFIX
Alias: None
Product: Eclipse Plugin
Classification: Yocto Project Subprojects
Component: eclipse-plugin (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium normal
Target Milestone: 2.2
Assignee: Tim Orling
QA Contact: Libertad
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-05-10 19:15 UTC by Humberto Ibarra
Modified: 2016-09-27 17:23 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Humberto Ibarra 2016-05-10 19:15:05 UTC
This seemed out of place for me and not sure if it was designed this way. Every time I change the folder in the Build location field for the new yocto-bsp wizard, the folder for the build is created with all its required conf files. I imagined this would be something done at the very end, currently I can end up with a ton of garbage of different build folders even before I have clicked Next in the first window. The user could decide to cancel and he/she gets the build directory created either way.

I was even able to put the same folder for the Build Location and the BSP output directory by playing with this behavior a bit.

This should be changed to be done after clicking Finish. If this is not possible we need an explanation and this documented somewhere. I didn't saw any mention to this behavior in the docs, neither I saw a message to the user telling that these directories were going to be created.
Comment 1 brian avery 2016-09-27 17:21:58 UTC
Yocto tools are no longer being actively supported. We plan to replace most, but not all, of the functionality in the CROPS Eclipse plugin by leveraging Linux Tools, provided by Eclipse.

In this instance, the future plugin will leverage devtool directly.