There's also a bug that may address this problem: 
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5203

--
Alexandru Georgescu


-----Original Message-----
From: Georgescu, Alexandru C 
Sent: Friday, September 27, 2013 13:03
To: 'Jate Sujjavanich'; 'yocto@yoctoproject.org'
Subject: RE: Yocto Bitbake Commander New Project Bug

Hi Jate,
You can try mentioning in the project name the actual poky directory name (in 
your case: poky) and in the project path the location where "poky" is located 
(your case: ~/workspace/). That should work.

Regards,
--
Alexandru Georgescu


-----Original Message-----
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Jate Sujjavanich
Sent: Thursday, September 26, 2013 21:48
To: 'yocto@yoctoproject.org'
Subject: [yocto] Yocto Bitbake Commander New Project Bug

Creating a Yocto Bitbake Commander project using an existing poky directory is 
a little buggy. I usually do this to avoid downloading poky from the Internet.

The plugin wizard implies that you can use a poky directory in your workspace 
with its clone from yocto repository option.

Attempting to use a cloned poky in workspace/poky results in the wizard 
reporting that ".../workspace/poky overlaps the location of another project: 
poky." Changing the name of the project merely results in the error "Directory 
...workspace/poky2 does not exist, please select git clone".

The workaround is to open a separate dummy workspace, and then run the wizard 
with Project Location pointing to your desired Project Location. You will then 
be able to hit Finish. Eclipse will create the .metadata and .eclipse-data 
files.

You can then switch to your desired workspace and use "Import an Existing 
Project."

Is this a bug?


-Jate S.
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to