Hi Thomas, > Hi Peter, >> Hi, >> >> whenever I run 'make distclean', some files/paths are not removed (although >> they should) >> >> When looking into the impl.mk I see several things I don't understand. >> I've attached the files I'm talking about as image, so we are talking about >> the >> same line numbers and the text is not "corrupted" by any line-wrapping. >> >> 1. Why do I still have the following files/paths in my working copy after >> running 'make distclean'? >> >> * qooxdoo\frontend\framework\.cache >> > > This is indeed strange.
Yes it is. Currently this problem is vanished although the changes I've made in our make-process should not be the reason for that. But I'm sure everybody knows what it means when someone says "I didn't do anything" ;) Whenever the problem re-occurs I will dig deeper into it. > >> * qooxdoo\frontend\framework\tool\*.pyo [including subfolder 'modules'] >> * qooxdoo\frontend\framework\tool\*.pyc [including subfolder 'modules'] >> > > Well, your concept of "distclean" might differ, but obviously the tool > chain was not considered to "get in the way", so you don't have to clean > it out, in order to be confident your installation is vanilla. Maybe > that was a misconception?! No problem anymore. I just thought that the same amount of cleaning is done on the framework source path that is done on the application path. I just duplicated the according line in our makefile so that the application path is cleansed of all temporary file types as well. >> This is more the "result" than a question, but the next two should be >> "real >> questions". >> >> 2. Why are the two lines that should do the job (1) are issued twice in >> impl.mk? (lines 65,66 and 70,71) >> > > I came across this once, too. Development cruft, IMHO. Yeah, and I don't think it would hurt. I was just so desperate at the time that anything unusual came into view... > >> 3. Currently I added a 'mrpropper' target to my application's makefile (see >> 2nd >> attachment) which does the job. But the mystery is that both information >> lines I added report the same: >> * FRAMEWORK_CACHE_PATH : ../qooxdoo/frontend/framework/.cache >> * My PATH : ../qooxdoo/frontend/framework/.cache >> > > Well, they *are* the same (doing a little re-writing here...): > > FRAMEWORK_CACHE_PATH = $(FRAMEWORK_PATH)/.cache (impl.mk) > with FRAMEWORK_PATH = $(QOOXDOO_PATH)/frontend/framework (impl.mk) > => FRAMEWORK_CACHE_PATH = $(QOOXDOO_PATH)/frontend/framework/.cache > = "My Path" (q.e.d.;) > > Why would you expect something else?! No, I did not expect something else! I was just surprised, that the remove operation did work on our makefile, although the remove operation in the impl.mk should have done it. Nevertheless, currently it seems that we have a working solution here, so this topic is settled for me. I suspect any background process (virus-scan,...) was accessing the .cache path when it should be removed and somehow that prevented the removal. Until this problem shows up again, I can live with our currently working solution. But when I have time, I'll try to recreate the situation again and take a closer look at it. 'till than it keeps to be a mystery for me ;) > > Cheers, > Thomas Cheers Peter ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
