[haiku-development] Re: Updates relating to build-o-matic, haiku-files.org

  • From: Matt Madia <mattmadia@xxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Tue, 17 May 2011 20:03:32 +0000

On Tue, May 17, 2011 at 19:15, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> That is caused by 1. limitations of the build system, which installs only one 
> version of a package (either gcc 2 or gcc 4), and 2. by there not being any 
> packages available for that purpose. The deal is that we'll have to build 4 
> versions of each package(*): gcc 2 for a primary gcc 2 Haiku (i.e. gcc 2 or 
> gcc 2 hybrid), gcc 2 for a secondary gcc 2 Haiku (i.e. gcc 4 hybrid), gcc 4 
> for a primary gcc 4 Haiku (i.e. gcc 4 or gcc 4 hybrid) and gcc 4 for a 
> secondary gcc 4 Haiku (i.e. gcc 2 hybrid). On the regular Haiku release the 
> gcc 2 and the gcc 4 for gcc 2 hybrid packages of a library have to be 
> installed, so that it is available with either compiler.
> I was hoping we could address that when readying the package management 
> support -- and I believe that was also what Oliver intended. Without proper 
> package building tools building four versions per software package is very 
> tedious and error prone.

Until the package manager is ready for trunk, would it be
possible/feasible/... to (temporarily) install files to gcc2/ or gcc4/
subdirs? This way, only two archives would be needed, things would be
easier for package maintainers, easier for the build system to manage,


Other related posts: