Bug 8386

Summary: [Eclipse] cannot build a Hello World GTK C Autotols Project with toolchain build with meta-ide-support
Product: [Yocto Project Subprojects] ADT Reporter: Valentin Hangan <valentinx.hangan>
Component: adtAssignee: Alexandru Georgescu <alexandru.c.georgescu>
Status: VERIFIED NOTABUG QA Contact: Valentin Hangan <valentinx.hangan>
Severity: normal    
Priority: Medium CC: alexandru.c.georgescu, bogdanx.a.voiculescu, ioanax.grigoropol, poky.adt.watcher, poky.watcher, richard.purdie, yp.ep.watcher, yp.watcher
Version: 1.9   
Target Milestone: 2.0   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
Error
none
Preferences Yocto Project ADT none

Description Valentin Hangan 2015-09-24 07:58:25 UTC
Created attachment 2766 [details]
Error

Eclipse version: kepler, luna, mars
commit: cf60ac293629fc8ecd6c4eb3709a6f334b499d0
Os: Fedora-21

Steps to reproduce:

1.Clone poky with commit : ea562de57590c966cd5a75fda8defecd397e6436
2.Build the toolchain--->run $ bitbake meta-ide-support
3.Open Window->Preferences->Yocto Project ADT and set up Toolchain Root Location, Sysroot Location and Kernel according to the SDK installation from the Yocto Project ADT menu:
   - Cross Compiler Options:  Build system derived toolchain
   - Toolchain Root Location : $PATH/poky/build
   - Sysroot Location: $PATH/poky/build
   - Kernel : $PATH/adt-installer/download_image/bzImage-qemux86.bin
4.Create a Hello World GTK C Project
5.Reconfigure Project
6.Build Project

Actual result: configure:error: Package requirements (glib-2.0 gtk+-2.0) were not met

Result from console: 
"make all
make: *** No rule to make target 'all'. Stop."

Expected result: Build Finished - no errors 

When i set up Yocto Project ADT using ADT or Cross-Toolchain Tarball Installation everything is fine.
Comment 1 Valentin Hangan 2015-09-24 07:58:57 UTC
Created attachment 2767 [details]
Preferences Yocto Project ADT
Comment 2 Valentin Hangan 2015-09-24 08:52:20 UTC
commit eclipse-kepler: cf60ac293629fc8ecd6c4eb3709a6f334b499d0
commit poky: ea562de57590c966cd5a75fda8defecd397e6436
Comment 3 Alexandru Georgescu 2015-09-24 08:53:09 UTC
(In reply to comment #2)
> commit eclipse-kepler: cf60ac293629fc8ecd6c4eb3709a6f334b499d0
> commit poky: ea562de57590c966cd5a75fda8defecd397e6436

Vali,
Can you try compiling sudokusavant from console using your build?
Comment 4 Alexandru Georgescu 2015-09-24 12:16:58 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > commit eclipse-kepler: cf60ac293629fc8ecd6c4eb3709a6f334b499d0
> > commit poky: ea562de57590c966cd5a75fda8defecd397e6436
> 
> Vali,
> Can you try compiling sudokusavant from console using your build?

Late update:

Seems that sudokusavant don't work when having built just "meta-ide-support", it gives the same error, but it works after running $ bitbake core-image-sato-sdk -c populate_sdk

I would like to get a confirmation if the "-c populate_sdk" command is REQUIRED in order to be able to build sudokusavant
Comment 5 Richard Purdie 2015-09-24 15:07:29 UTC
Alex, could you confirm that it you simply "bitbake core-image-sato" *without* the -c populate_sdk that this test would still work?

Its expected that "bitbake meta-ide-support" would not trigger gtk or glib to build. "bitbake core-image-sato" would cause them to get built though.
Comment 6 Valentin Hangan 2015-10-20 06:19:29 UTC
I build only meta-ide-support at that time. I try with bitbake core-image-sato and everything it's ok.
I will change status in Resolved - Notabug
Comment 7 Bogdan Alexandru Voiculescu 2015-10-26 08:52:03 UTC
verified - not a bug