trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: March 2011

Re: [trinity-devel] All current Arch PKGBUILDS now broken due to new Out of Source Build Requirement

From: Baho Utot <baho-utot@...>
Date: Fri, 25 Mar 2011 18:51:32 -0400

On Friday 25 March 2011 03:03:57 pm David C. Rankin wrote:
> On 03/25/2011 01:59 PM, Serghei Amelian wrote:
> > [...]
> >
> >> >      Of course I will do it however you guys decide, but I would
> >> > suggest it is far better to warn about potential problems when reusing
> >> > a source tree than it is to mandate a change from the traditional
> >> > build methods.
> >> >
> >> >      You guys think about it and let me know. I would change
> >> > the*mandate*  of the out-or-source requirement to a*WARNING*  so that
> >> > the build can proceed, but the builder is aware that if he is not
> >> > building from a clean source, then unforeseen problems can arise.
> >> > Something like:
> >
> > [...]
> >
> > I recommend you to try to comply with out-of-source requirement.
> > Otherwise, you will be on your own, I will refuse to debug problems
> > generated by in-source mode. Trinity build system is*very*  complicated,
> > with a lot generated files, which can interfere with sources in many
> > unexpected ways.
>
> OK,
>
>    Decision made, we will start re-working all of the Arch PKGBUILDs to use
> out of source building...

Or use the ones I have created.  Out of source works just fine.  You may want 
to modify them to your own tatse though.