[Mono-bugs] [Bug 668123] New: [MSBuild] Clean doesn't Clean

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=668123

https://bugzilla.novell.com/show_bug.cgi?id=668123#c0


           Summary: [MSBuild] Clean doesn't Clean
    Classification: Mono
           Product: MonoDroid
           Version: SVN
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Tools
        AssignedTo: mkestner at novell.com
        ReportedBy: jpryor at novell.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


The Clean target doesn't fully clean after itself.

I generally assume that Clean removes all generated and intermediate files, so
that a Clean + Build is akin to a fresh checkout.

Unfortunately, it isn't.

Case in point: when Google released their Android SDK 9 Release 2, I tried
doing a Clean + Build to reproduce an aresgen bug that was reported on the
mailing list.

Much to my surprise/chagrin/annoyance, my build continued to work without
error, because aresgen wasn't be executed, because (in this case)
obj/Debug/R.cs.flag wasn't removed.  I had to `rm -Rf obj/Debug` in order to
start reproducing the issue.

The same comes up when writing fixes for aresgen: aresgen isn't necessarily
executed, and my reflexive Clean+Build builds aren't actually executing
aresgen; I have to _know_ how the build works, know that obj/Debug/R.cs.flag
exists, and remove it in order to coax aresgen to execute (or just nuke
obj/Debug, which is very tempting, at which point the question becomes...what's
the point of the Clean target again?).

Is there a way to make the Clean target actually...Clean?

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.