[wix-devs] Broken Build

[Bob Arnson]

`git clean -ndx` is your friend. 😊 I agree incrementality is busted. I never trusted the incremental wix3 build either which is why I did all the multiproc hacking, to make a full clean build fast. (Pick your battles.) That's also why I started doing traversal projects. Maybe that'll help with incrementality...?

Or we just go back to microrepos.

-----Original Message-----
From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Sean Hall via wix-devs
Sent: Saturday, 3 July, 2021 12:36
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Cc: Sean Hall <r.sean.hall at gmail.com>
Subject: Re: [wix-devs] Broken Build

It's the easiest to explain. Commands like that one could permanently delete files you don't want deleted. The problem is that the build process is not incremental and as seen on the CI machine never has problems from a fresh clone (aside from the poisoned nuget cache mentioned in a different thread).

On Sat, Jul 3, 2021 at 11:10 AM Bob Arnson via wix-devs < wix-devs at lists.wixtoolset.org> wrote:

> How does that solve the problem? `git clean -fdx` would have the same 
> effect.
>
> -----Original Message-----
> From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of 
> Sean Hall via wix-devs
> Sent: Saturday, 3 July, 2021 11:46
> To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
> Cc: Sean Hall <r.sean.hall at gmail.com>
> Subject: Re: [wix-devs] Broken Build
>
> >  I'm going to try cloning the wix4 repo to a different folder to see 
> > if I
> can build that.
>
> Yes, you have to do something like that until somebody fixes the build 
> so that isn't necessary.
>
> On Sat, Jul 3, 2021 at 10:37 AM Ron Martin via wix-devs < 
> wix-devs at lists.wixtoolset.org> wrote:
>
> > Sean,
> >
> > Your commit:
> >
> > 9bdf3730cd43e1af8a4ea9be6cf2fba77fcff2d2
> >
> > breaks my build.
> >
> > Specifically, the following files cannot see your changes in 
> > WixBundleSymbol.cs and therefore generate errors:
> >
> > Compiler_Bundle.cs
> > CreateBootstrapperApplicationManifestCommand,cs
> > CreateBurnManifestCommand.cs
> >
> > However, the following files do see those changes and therefore 
> > compile without issue:
> >
> > BalBurnBackendExtension.cs
> > CerateBundleExeCommand.cs
> >
> > I don't know what I could have done to create this situation. It 
> > appeared when I rebased several branches on the most recent head of 
> > the develop branch.
> >
> > I'm going to try cloning the wix4 repo to a different folder to see 
> > if I can build that.
> >
> > I would appreciate any suggestions you might have.
> >
> > Ron
> >
> > ____________________________________________________________________
> > WiX Toolset Developer Mailing List provided by FireGiant 
> > http://www.firegiant.com/
> >
> ____________________________________________________________________
> WiX Toolset Developer Mailing List provided by FireGiant 
> http://www.firegiant.com/ 
> ____________________________________________________________________
> WiX Toolset Developer Mailing List provided by FireGiant 
> http://www.firegiant.com/
>
____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/