Skip to contentSkip to conversation

dependency gui problem

DISCUSSION NiQingliang 4 participants 15 messages Jun 30, 2011 – Jul 5, 2011

lore
Share & tools
lore
#0 lore raw

help!!!!!!!! thanks!

after make build dir, and set env, follow cmd works normally. bitbake -g -u depexp core-image-minimal

but once builded, the cmd works abnormal, the symptom like that:
the "loading cache" window goes 100% quickly, but after that, the window always be there, and the parent window "dependency explorer" become no-response. I have waited half an hour, and it still there.

environment:
SW: archlinux
HW: dell optiplex 980

Signature · 4 lines
倪庆亮
TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com
#1 lore raw
Quoted 4 lines · NiQingliang

after make build dir, and set env, follow cmd works normally. bitbake -g -u depexp core-image-minimal

but once builded, the cmd works abnormal, the symptom like that:

What does "once builded" mean?

Quoted 4 lines

the "loading cache" window goes 100% quickly, but after that, the window always be there, and the parent window "dependency explorer" become no-response. I have waited half an hour, and it still there.

Thanks,
-- Dexuan

#2 lore raw

once builded, is after executed "bitbake core-image-minimal" and generated the final image.

Quoted 5 lines · Dexuan

, and set env, follow cmd works normally.

Quoted 3 lines

bitbake -g -u depexp core-image-minimal

but once builded, the cmd works abnormal, the symptom like that:

What does "once builded" mean?

Signature · 4 lines
倪庆亮
TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com
#3 lore raw
Quoted 2 lines · NiQingliang

once builded, is after executed "bitbake core-image-minimal" and generated the final image.

I tried that just now on recent poky.git's master branch but can't reproduce the issue. :-( You may need to dig out where it hangs...

Quoted 6 lines · Dexuan
Quoted 5 lines

, and set env, follow cmd works normally.

Quoted 4 lines

bitbake -g -u depexp core-image-minimal

but once builded, the cmd works abnormal, the symptom like that:
What does "once builded" mean?

Thanks,
-- Dexuan

#4 lore raw

I have added "-DDD -v", after close window "loading cache" manually, the bitbake exited, and then I can see some DEBUG info on shell, but there is no clue.

how to dig out where it hangs:-(

Quoted 15 lines · Dexuan
Quoted 2 lines · NiQingliang

once builded, is after executed "bitbake core-image-minimal" and generated the final image.

I tried that just now on recent poky.git's master branch but can't reproduce the issue. :-( You may need to dig out where it hangs...

Quoted 6 lines · Dexuan
Quoted 5 lines

, and set env, follow cmd works normally.

Quoted 4 lines

bitbake -g -u depexp core-image-minimal

but once builded, the cmd works abnormal, the symptom like that:
What does "once builded" mean?

Thanks,
-- Dexuan

Signature · 4 lines
倪庆亮
TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com
#5 lore raw
Quoted 6 lines · NiQingliang

I have added "-DDD -v", after close window "loading cache" manually, the bitbake exited, and then I can see some DEBUG info on shell, but there is no clue.

how to dig out where it hangs:-(

Can you capture the log and send it. I noticed you are running on ArchLinux, can you confirm which version of Python you are using and which version of Poky you have?

You have to be using 2.6 or 2.7 Python.

Sau!

Quoted 17 lines · Dexuan
Quoted 15 lines
Quoted 2 lines · NiQingliang

once builded, is after executed "bitbake core-image-minimal" and generated the final image.

I tried that just now on recent poky.git's master branch but can't reproduce the issue. :-( You may need to dig out where it hangs...

Quoted 6 lines · Dexuan
Quoted 5 lines

, and set env, follow cmd works normally.

Quoted 4 lines

bitbake -g -u depexp core-image-minimal

but once builded, the cmd works abnormal, the symptom like that:
What does "once builded" mean?

Thanks,
-- Dexuan

#6 lore raw

I'm using python2.7

I have setup a new file named "python" in build dir, whose content like that:
#!/bin/bash
/usr/bin/env python2 $@

and add the build dir in env var "PATH".

If the python version error, I don't think I can see the GUI of bitbake.

after manually closed gui, the shell output is like attachement.

and I tried like this:
if I change some file in poky's recipes for the conf file, the "loading cache" window will work normally, and I can see the progress bar rolling.

but if I issue the cmd second time, it will hang.

Quoted 33 lines · Saul Wold
Quoted 6 lines · NiQingliang

I have added "-DDD -v", after close window "loading cache" manually, the bitbake exited, and then I can see some DEBUG info on shell, but there is no clue.

how to dig out where it hangs:-(

Can you capture the log and send it. I noticed you are running on ArchLinux, can you confirm which version of Python you are using and which version of Poky you have?

You have to be using 2.6 or 2.7 Python.

Sau!

Quoted 17 lines · Dexuan
Quoted 15 lines
Quoted 2 lines · NiQingliang

once builded, is after executed "bitbake core-image-minimal" and generated the final image.

I tried that just now on recent poky.git's master branch but can't reproduce the issue. :-( You may need to dig out where it hangs...

Quoted 6 lines · Dexuan
Quoted 5 lines

, and set env, follow cmd works normally.

Quoted 4 lines

bitbake -g -u depexp core-image-minimal

but once builded, the cmd works abnormal, the symptom like that:
What does "once builded" mean?

Thanks,
-- Dexuan

Signature · 4 lines
倪庆亮
TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com

DEBUG: Using cache in '/media/Datum/yocto/build_sa735/tmp/cache/bb_codeparser.dat' for codeparser cache
DEBUG: Clearing SRCREV cache due to cache policy of: clear
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/sanity.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/sanity.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/sanity.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/license.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/license.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/license.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/sstate.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/sstate.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/sstate.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/devshell.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/devshell.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/devshell.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/debian.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/debian.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/debian.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/insane.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/insane.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/insane.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/image-prelink.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/image-prelink.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/image-prelink.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/image-mklibs.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/image-mklibs.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/image-mklibs.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/package_ipk.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/package_ipk.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/package_ipk.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/prserv.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/prserv.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/prserv.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/packagedata.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/packagedata.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/packagedata.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/package.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/package.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/package.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/package_rpm.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/package_rpm.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/package_rpm.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/rm_work.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/rm_work.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/rm_work.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/logging.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/logging.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/logging.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/buildstats.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/buildstats.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/buildstats.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/metadata_scm.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/metadata_scm.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/metadata_scm.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/utility-tasks.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/utility-tasks.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/utility-tasks.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/utils.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/utils.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/utils.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/mirrors.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/mirrors.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/mirrors.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/staging.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/staging.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/staging.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/patch.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/patch.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/patch.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/classes/base.bbclass
DEBUG: BB /media/Datum/yocto/poky/meta/classes/base.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/base.bbclass
DEBUG: LOAD /media/Datum/yocto/poky/meta/conf/abi_version.conf
DEBUG: CONF conf/bitbake.conf:654: including conf/abi_version.conf
DEBUG: LOAD /media/Datum/yocto/poky/meta/conf/sanity.conf
DEBUG: CONF conf/bitbake.conf:653: including conf/sanity.conf
DEBUG: LOAD /media/Datum/yocto/poky/meta/conf/documentation.conf
DEBUG: CONF conf/bitbake.conf:652: including conf/documentation.conf
DEBUG: LOAD /media/Datum/yocto/poky/meta/conf/distro/include/tclibc-eglibc.inc
DEBUG: BB /media/Datum/yocto/poky/meta/conf/distro/include/tclibc-eglibc.inc: handle(data, include)
DEBUG: CONF /media/Datum/yocto/poky/meta/conf/distro/defaultsetup.conf:13: including conf/distro/include/tclibc-eglibc.inc
DEBUG: LOAD /media/Datum/yocto/poky/meta/conf/distro/include/as-needed.inc
DEBUG: BB /media/Datum/yocto/poky/meta/conf/distro/include/as-needed.inc: handle(data, include)
DEBUG: CONF /media/Datum/yocto/poky/meta/conf/distro/include/tcmode-default.inc:66: including conf/distro/include/as-needed.inc
DEBUG: LOAD /media/Datum/yocto/poky/meta/conf/distro/include/tcmode-default.inc
DEBUG: BB /media/Datum/yocto/poky/meta/conf/distro/include/tcmode-default.inc: handle(data, include)
DEBUG: CONF /media/Datum/yocto/poky/meta/conf/distro/defaultsetup.conf:10: including conf/distro/include/tcmode-default.inc
DEBUG: LOAD /media/Datum/yocto/poky/meta/conf/distro/include/world-broken.inc
DEBUG: BB /media/Datum/yocto/poky/meta/conf/distro/include/world-broken.inc: handle(data, include)
DEBUG: CONF /media/Datum/yocto/poky/meta/conf/distro/defaultsetup.conf:4: including conf/distro/include/world-broken.inc
DEBUG: LOAD /media/Datum/yocto/poky/meta/conf/distro/include/default-distrovars.inc
DEBUG: BB /media/Datum/yocto/poky/meta/conf/distro/include/default-distrovars.inc: handle(data, include)
DEBUG: CONF /media/Datum/yocto/poky/meta/conf/distro/defaultsetup.conf:3: including conf/distro/include/default-distrovars.inc
DEBUG: LOAD /media/Datum/yocto/poky/meta/conf/distro/include/default-versions.inc
DEBUG: BB /media/Datum/yocto/poky/meta/conf/distro/include/default-versions.inc: handle(data, include)
DEBUG: CONF /media/Datum/yocto/poky/meta/conf/distro/defaultsetup.conf:2: including conf/distro/include/default-versions.inc
DEBUG: LOAD /media/Datum/yocto/poky/meta/conf/distro/include/default-providers.inc
DEBUG: BB /media/Datum/yocto/poky/meta/conf/distro/include/default-providers.inc: handle(data, include)
DEBUG: CONF /media/Datum/yocto/poky/meta/conf/distro/defaultsetup.conf:1: including conf/distro/include/default-providers.inc
DEBUG: LOAD /media/Datum/yocto/poky/meta/conf/distro/defaultsetup.conf
DEBUG: CONF conf/bitbake.conf:651: including conf/distro/defaultsetup.conf
DEBUG: LOAD /media/Datum/yocto/poky/meta-sa735/conf/distro/sa735.conf
DEBUG: CONF conf/bitbake.conf:650: including conf/distro/sa735.conf
DEBUG: CONF file 'conf/machine-sdk/${SDKMACHINE}.conf' not found
DEBUG: CONF conf/bitbake.conf:649: including conf/machine-sdk/${SDKMACHINE}.conf
DEBUG: LOAD /media/Datum/yocto/poky/meta/conf/machine/include/tune-ppce300c3.inc
DEBUG: BB /media/Datum/yocto/poky/meta/conf/machine/include/tune-ppce300c3.inc: handle(data, include)
DEBUG: CONF /media/Datum/yocto/poky/meta-sa735/conf/machine/mpc8314-sa735.conf:7: including conf/machine/include/tune-ppce300c3.inc
DEBUG: LOAD /media/Datum/yocto/poky/meta-sa735/conf/machine/mpc8314-sa735.conf
DEBUG: CONF conf/bitbake.conf:648: including conf/machine/mpc8314-sa735.conf
DEBUG: CONF file 'conf/target/INVALID-oe-INVALID.conf' not found
DEBUG: CONF conf/bitbake.conf:647: including conf/target/INVALID-oe-INVALID.conf
DEBUG: CONF file 'conf/build/x86_64-linux.conf' not found
DEBUG: CONF conf/bitbake.conf:646: including conf/build/x86_64-linux.conf
DEBUG: LOAD conf/local.conf
DEBUG: CONF conf/bitbake.conf:645: including conf/local.conf
DEBUG: CONF file 'conf/auto.conf' not found
DEBUG: CONF conf/bitbake.conf:644: including conf/auto.conf
DEBUG: CONF file 'conf/site.conf' not found
DEBUG: CONF conf/bitbake.conf:643: including conf/site.conf
DEBUG: LOAD /media/Datum/yocto/poky/meta/conf/bitbake.conf
DEBUG: LOAD /media/Datum/yocto/poky/meta-sa735/conf/layer.conf
DEBUG: Adding layer /media/Datum/yocto/poky/meta-sa735
DEBUG: LOAD /media/Datum/yocto/poky/meta/conf/layer.conf
DEBUG: Adding layer /media/Datum/yocto/poky/meta
DEBUG: LOAD /media/Datum/yocto/build_sa735/conf/bblayers.conf
DEBUG: Found bblayers.conf (/media/Datum/yocto/build_sa735/conf/bblayers.conf)
DEBUG: UI 'depexp' does not require extra cache!
DEBUG: Removed the following variables from the environment: GNOME_DESKTOP_SESSION_ID, XDG_DATA_HOME, WINDOWPATH, PROMPT_COMMAND, GNOME_KEYRING_CONTROL, PS3, HG, PS4, SHLVL, G_BROKEN_FILENAMES, WINDOWID, ORBIT_SOCKETDIR, BBFETCH2, XDG_CONFIG_HOME, XDG_CACHE_HOME, J2SDKDIR, QT_XFT, GDMSESSION, PKG_CONFIG_PATH, MOZ_PLUGIN_PATH, JAVA_HOME, XDG_CONFIG_DIRS, GTK_MODULES, GDM_LANG, BUILDDIR, J2REDIR, QTDIR

#7 lore raw

Oh, sorry, I have fixed some bug in my description:-)

I'm using python2.7

I have setup a new file named "python" in build dir, whose content like that:
#!/bin/bash
/usr/bin/env python2 $@

and add the build dir in env var "PATH".

If the python version error, I don't think I can see the GUI of bitbake.

after manually closed gui, the shell output is like attachement.

and I tried like this:
if I change some file in poky's recipes for the conf file, the "processing recipes" window will work normally, and I can see the progress bar
rolling.

but if I issue the cmd second time, "loading cache" window will hang.

Quoted 62 lines · NiQingliang

I'm using python2.7

I have setup a new file named "python" in build dir, whose content like that:
#!/bin/bash
/usr/bin/env python2 $@

and add the build dir in env var "PATH".

If the python version error, I don't think I can see the GUI of bitbake.

after manually closed gui, the shell output is like attachement.

and I tried like this:
if I change some file in poky's recipes for the conf file, the "loading cache" window will work normally, and I can see the progress bar rolling.

but if I issue the cmd second time, it will hang.

Quoted 8 lines · Saul Wold
Quoted 6 lines · NiQingliang

I have added "-DDD -v", after close window "loading cache" manually, the bitbake exited, and then I can see some DEBUG info on shell, but there is no clue.

how to dig out where it hangs:-(

Quoted 25 lines

Can you capture the log and send it. I noticed you are running on ArchLinux, can you confirm which version of Python you are using and which version of Poky you have?

You have to be using 2.6 or 2.7 Python.

Sau!

Quoted 17 lines · Dexuan
Quoted 15 lines
Quoted 2 lines · NiQingliang

once builded, is after executed "bitbake core-image-minimal" and generated the final image.

I tried that just now on recent poky.git's master branch but can't reproduce the issue. :-( You may need to dig out where it hangs...

Quoted 6 lines · Dexuan
Quoted 5 lines

, and set env, follow cmd works normally.

Quoted 4 lines

bitbake -g -u depexp core-image-minimal

but once builded, the cmd works abnormal, the symptom like that:
What does "once builded" mean?

Thanks,
-- Dexuan

--
倪庆亮

TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com
Signature · 4 lines
倪庆亮
TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com
#8 lore raw

I have looked the fiel depexp.py, and have some doubt:

why in "ParseCompleted", the progress bar will hide, but in "CacheLoadCompleted", it will not???????

I don't think these two events need different process.

if isinstance(event, bb.event.CacheLoadCompleted):
gtk.gdk.threads_enter() pbar.update(progress_total, progress_total) gtk.gdk.threads_leave()
continue
.......
if isinstance(event, bb.event.ParseCompleted):
pbar.hide()
continue

Quoted 99 lines · NiQingliang

Oh, sorry, I have fixed some bug in my description:-)

I'm using python2.7

I have setup a new file named "python" in build dir, whose content like that:
#!/bin/bash
/usr/bin/env python2 $@

and add the build dir in env var "PATH".

If the python version error, I don't think I can see the GUI of bitbake.

after manually closed gui, the shell output is like attachement.

and I tried like this:
if I change some file in poky's recipes for the conf file, the "processing recipes" window will work normally, and I can see the progress bar
rolling.

but if I issue the cmd second time, "loading cache" window will hang.

Quoted 56 lines · NiQingliang

I'm using python2.7

I have setup a new file named "python" in build dir, whose content like that:
#!/bin/bash
/usr/bin/env python2 $@

and add the build dir in env var "PATH".

If the python version error, I don't think I can see the GUI of bitbake.

after manually closed gui, the shell output is like attachement.

and I tried like this:
if I change some file in poky's recipes for the conf file, the "loading cache" window will work normally, and I can see the progress bar rolling.

but if I issue the cmd second time, it will hang.

Quoted 8 lines · Saul Wold
Quoted 6 lines · NiQingliang

I have added "-DDD -v", after close window "loading cache" manually, the bitbake exited, and then I can see some DEBUG info on shell, but there is no clue.

how to dig out where it hangs:-(

Quoted 25 lines

Can you capture the log and send it. I noticed you are running on ArchLinux, can you confirm which version of Python you are using and which version of Poky you have?

You have to be using 2.6 or 2.7 Python.

Sau!

Quoted 17 lines · Dexuan
Quoted 15 lines
Quoted 2 lines · NiQingliang

once builded, is after executed "bitbake core-image-minimal" and generated the final image.

I tried that just now on recent poky.git's master branch but can't reproduce the issue. :-( You may need to dig out where it hangs...

Quoted 6 lines · Dexuan
Quoted 5 lines

, and set env, follow cmd works normally.

Quoted 4 lines

bitbake -g -u depexp core-image-minimal

but once builded, the cmd works abnormal, the symptom like that:
What does "once builded" mean?

Thanks,
-- Dexuan

Quoted 6 lines

--
倪庆亮

TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com

--
倪庆亮

TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Signature · 4 lines
倪庆亮
TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com
#9 lore raw

I have changed that code section, and solved my problem, but I don't know if it is the right way.

            if isinstance(event, bb.event.CacheLoadCompleted):
                 pbar.hide()
                 continue
            .......
            if isinstance(event, bb.event.ParseCompleted):
                 pbar.hide()
                 continue
Quoted 129 lines · NiQingliang

I have looked the fiel depexp.py, and have some doubt:

why in "ParseCompleted", the progress bar will hide, but in "CacheLoadCompleted", it will not???????

I don't think these two events need different process.

if isinstance(event, bb.event.CacheLoadCompleted):
gtk.gdk.threads_enter() pbar.update(progress_total, progress_total) gtk.gdk.threads_leave()
continue
.......
if isinstance(event, bb.event.ParseCompleted):
pbar.hide()
continue

Quoted 95 lines · NiQingliang

Oh, sorry, I have fixed some bug in my description:-)

I'm using python2.7

I have setup a new file named "python" in build dir, whose content like that:
#!/bin/bash
/usr/bin/env python2 $@

and add the build dir in env var "PATH".

If the python version error, I don't think I can see the GUI of bitbake.

after manually closed gui, the shell output is like attachement.

and I tried like this:
if I change some file in poky's recipes for the conf file, the "processing recipes" window will work normally, and I can see the progress bar
rolling.

but if I issue the cmd second time, "loading cache" window will hang.

Quoted 56 lines · NiQingliang

I'm using python2.7

I have setup a new file named "python" in build dir, whose content like that:
#!/bin/bash
/usr/bin/env python2 $@

and add the build dir in env var "PATH".

If the python version error, I don't think I can see the GUI of bitbake.

after manually closed gui, the shell output is like attachement.

and I tried like this:
if I change some file in poky's recipes for the conf file, the "loading cache" window will work normally, and I can see the progress bar rolling.

but if I issue the cmd second time, it will hang.

Quoted 8 lines · Saul Wold
Quoted 6 lines · NiQingliang

I have added "-DDD -v", after close window "loading cache" manually, the bitbake exited, and then I can see some DEBUG info on shell, but there is no clue.

how to dig out where it hangs:-(

Quoted 25 lines

Can you capture the log and send it. I noticed you are running on ArchLinux, can you confirm which version of Python you are using and which version of Poky you have?

You have to be using 2.6 or 2.7 Python.

Sau!

Quoted 17 lines · Dexuan
Quoted 15 lines
Quoted 2 lines · NiQingliang

once builded, is after executed "bitbake core-image-minimal" and generated the final image.

I tried that just now on recent poky.git's master branch but can't reproduce the issue. :-( You may need to dig out where it hangs...

Quoted 6 lines · Dexuan
Quoted 5 lines

, and set env, follow cmd works normally.

Quoted 4 lines

bitbake -g -u depexp core-image-minimal

but once builded, the cmd works abnormal, the symptom like that:
What does "once builded" mean?

Thanks,
-- Dexuan

Quoted 6 lines

--
倪庆亮

TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com

--
倪庆亮

TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com
Quoted 4 lines

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

--
倪庆亮

TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Signature · 4 lines
倪庆亮
TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com
#10 lore raw

I have not found the email adress of bitbake's developer, does anyone know?

Quoted 153 lines · NiQingliang

I have changed that code section, and solved my problem, but I don't know if it is the right way.

            if isinstance(event, bb.event.CacheLoadCompleted):
                 pbar.hide()
                 continue
            .......
            if isinstance(event, bb.event.ParseCompleted):
                 pbar.hide()
                 continue
Quoted 125 lines · NiQingliang

I have looked the fiel depexp.py, and have some doubt:

why in "ParseCompleted", the progress bar will hide, but in "CacheLoadCompleted", it will not???????

I don't think these two events need different process.

if isinstance(event, bb.event.CacheLoadCompleted):
gtk.gdk.threads_enter() pbar.update(progress_total, progress_total) gtk.gdk.threads_leave()
continue
.......
if isinstance(event, bb.event.ParseCompleted):
pbar.hide()
continue

Quoted 95 lines · NiQingliang

Oh, sorry, I have fixed some bug in my description:-)

I'm using python2.7

I have setup a new file named "python" in build dir, whose content like that:
#!/bin/bash
/usr/bin/env python2 $@

and add the build dir in env var "PATH".

If the python version error, I don't think I can see the GUI of bitbake.

after manually closed gui, the shell output is like attachement.

and I tried like this:
if I change some file in poky's recipes for the conf file, the "processing recipes" window will work normally, and I can see the progress bar
rolling.

but if I issue the cmd second time, "loading cache" window will hang.

Quoted 56 lines · NiQingliang

I'm using python2.7

I have setup a new file named "python" in build dir, whose content like that:
#!/bin/bash
/usr/bin/env python2 $@

and add the build dir in env var "PATH".

If the python version error, I don't think I can see the GUI of bitbake.

after manually closed gui, the shell output is like attachement.

and I tried like this:
if I change some file in poky's recipes for the conf file, the "loading cache" window will work normally, and I can see the progress bar rolling.

but if I issue the cmd second time, it will hang.

Quoted 8 lines · Saul Wold
Quoted 6 lines · NiQingliang

I have added "-DDD -v", after close window "loading cache" manually, the bitbake exited, and then I can see some DEBUG info on shell, but there is no clue.

how to dig out where it hangs:-(

Quoted 25 lines

Can you capture the log and send it. I noticed you are running on ArchLinux, can you confirm which version of Python you are using and which version of Poky you have?

You have to be using 2.6 or 2.7 Python.

Sau!

Quoted 17 lines · Dexuan
Quoted 15 lines
Quoted 2 lines · NiQingliang

once builded, is after executed "bitbake core-image-minimal" and generated the final image.

I tried that just now on recent poky.git's master branch but can't reproduce the issue. :-( You may need to dig out where it hangs...

Quoted 6 lines · Dexuan
Quoted 5 lines

, and set env, follow cmd works normally.

Quoted 4 lines

bitbake -g -u depexp core-image-minimal

but once builded, the cmd works abnormal, the symptom like that:
What does "once builded" mean?

Thanks,
-- Dexuan

Quoted 6 lines

--
倪庆亮

TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com

--
倪庆亮

TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com
Quoted 4 lines

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

--
倪庆亮

TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com
Quoted 4 lines

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

--
倪庆亮

TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Signature · 4 lines
倪庆亮
TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com
#12 lore raw
In reply to NiQingliang
Quoted 11 lines · NiQingliang

I have changed that code section, and solved my problem, but I don't know if it is the right way.

            if isinstance(event, bb.event.CacheLoadCompleted):
                 pbar.hide()
                 continue
            .......
            if isinstance(event, bb.event.ParseCompleted):
                 pbar.hide()
                 continue
Quoted 5 lines
Quoted 4 lines · NiQingliang

I have looked the fiel depexp.py, and have some doubt:

why in "ParseCompleted", the progress bar will hide, but in "CacheLoadCompleted", it will not???????

I guess there should be a ParseCompleted event after the CacheLoadCompleted event(?), but on your host, the ParseCompleted doesn't happen somehow?

I'm not sure your change is ok, because if it's a generic issue, why can't I reproduce the issue?

Quoted 11 lines
Quoted 11 lines

I don't think these two events need different process.

if isinstance(event, bb.event.CacheLoadCompleted):
gtk.gdk.threads_enter() pbar.update(progress_total, progress_total) gtk.gdk.threads_leave()
continue
.......
if isinstance(event, bb.event.ParseCompleted):
pbar.hide() continue

Thanks,
-- Dexuan

#13 lore raw

according my understanding, the parseXX serials events is used for "parsing recipes" window, and the cacheXX serials events is used for "loading cache" window. The two windows is mutual-excluded.

thanks!!!

I will ask the bitbake developer, and will show you if I got the answer.

Quoted 35 lines · Dexuan
Quoted 11 lines · NiQingliang

I have changed that code section, and solved my problem, but I don't know if it is the right way.

            if isinstance(event, bb.event.CacheLoadCompleted):
                 pbar.hide()
                 continue
            .......
            if isinstance(event, bb.event.ParseCompleted):
                 pbar.hide()
                 continue
Quoted 5 lines
Quoted 4 lines · NiQingliang

I have looked the fiel depexp.py, and have some doubt:

why in "ParseCompleted", the progress bar will hide, but in "CacheLoadCompleted", it will not???????

I guess there should be a ParseCompleted event after the CacheLoadCompleted event(?), but on your host, the ParseCompleted doesn't happen somehow?

I'm not sure your change is ok, because if it's a generic issue, why can't I reproduce the issue?

Quoted 11 lines
Quoted 11 lines

I don't think these two events need different process.

if isinstance(event, bb.event.CacheLoadCompleted):
gtk.gdk.threads_enter() pbar.update(progress_total, progress_total) gtk.gdk.threads_leave()
continue
.......
if isinstance(event, bb.event.ParseCompleted):
pbar.hide() continue

Thanks,
-- Dexuan

Signature · 4 lines
倪庆亮
TEL:    13588371863
E-MAIL: [email protected]
BLOG:   http://niqingliang2003.wordpress.com
#14 lore raw
In reply to Cui, Dexuan
Quoted 12 lines · Dexuan
Quoted 11 lines · NiQingliang

I have changed that code section, and solved my problem, but I don't know if it is the right way.

            if isinstance(event, bb.event.CacheLoadCompleted):
                 pbar.hide()
                 continue
            .......
            if isinstance(event, bb.event.ParseCompleted):
                 pbar.hide()
                 continue
Quoted 8 lines
Quoted 5 lines · NiQingliang
Quoted 4 lines

I have looked the fiel depexp.py, and have some doubt:

why in "ParseCompleted", the progress bar will hide, but in "CacheLoadCompleted", it will not???????

I guess there should be a ParseCompleted event after the CacheLoadCompleted event(?), but on your host, the ParseCompleted doesn't happen somehow?

I'm not sure your change is ok, because if it's a generic issue, why can't I reproduce the issue?

I suspect you were always parsing at least one file because you were using linux-yocto. I have a "fix" pending for that issue as well as the fix I've added to bitbake to address this specific problem.

Cheers,

Richard