[eclipse-poky] Eclipse plugin development on timo/maven

[Lewis, ScottX]

Hi Paul,

<stuff deleted>
Hi Scott,

On Thursday, 25 January 2018 6:58:13 AM NZDT Lewis, ScottX wrote:
> There *is* a poky.launch configuration already in org.yocto.sdk.releng/
> launches/poky.launch.   If you open Run/Debug... you will see poky as one of
> the Eclipse applications.   On linux you can simply run/debug this launch
> config and it will start a baby eclipse (Brian's term) with the Yocto 
> plugins running.

Yep that does indeed work - the missing piece was using the "releng" project rather than any other project (such as the main eclipse-poky-contrib one), thanks. One thing I did notice is that there seem to be two apparently identical "poky" launch configurations under there, is that expected?

[Scott]  Yes.  This is a strangeness due to the fact that two projects actually refer to the same launch config...because the top-level project contains all the other projects.

A couple of other things I noticed:

1) We have a yocto-bsp tool available in the Yocto Project Tools menu provided by the plugin - I suspect we should just drop this since the underlying yocto- bsp tool this will be calling is now gone.

[Scott]  I agree.

2) If I try to create a new project, there don't seem to be any project templates available that look like they are provided by the plugin, is that expected? I know we used to have these in much older versions of the plugin.

[Scott] If I do New Project... -> C/C++ Project -> Next -> C or C++ Managed Build Project

There is a category on the lower left for Yocto Project SDK Autotools Project.   These are provided by our plugin.   We may want to make them more prominent in the wizard...something for discussion.

I'm [Scott] not feeling very well today, and seem to be feeling worse, so I'm going to miss our call this afternoon.   My current status:   

1) I think we are ready to move what's now on timo/maven to master.   We have to send notice about our plans to yocto mailing list...and get feedback before doing so...I suggest we also send our plans for 2.5 and 2.6 and ongoing eclipse-poky development...along with notice about eclipse-poky mailing list.

2) Once on master my plan is to remove RSE references.   This should be easy now that bb commander is going.

3) Once in master I'm also going to introduce the new plugin that uses org.eclipse.remote to redirect autotools makefile gen to docker container.

I guess another question is can we get commit rights for direct-to-master commits (?)  

Sorry about the no-show today.

> One thing I realized, however, is that this launch config won't work on
> windows.   This is not an immediate concern, but we will need to deal with
> it.   In fact, the target definitions that we have also won't work on
> windows.    One question for discussion:  do we want to have separate target
> definition files for OS/archs...e.g. linux/x86_64, win32/x86_64?    Along
> those lines...do we need/want to support all of mac, linux, win X 
> x86_32, x86_64?

I would say let's start small - Linux and Windows 64-bit and then go from there. At minimum we should have a bug open for Windows support if we don't already.

[Scott]  Starting with these two makes sense to me.   I'll start working on the target platform needed for win64, as I have a win64 machine in my possession now.

Scott