Ticket #661 (closed enhancement: duplicate)
Opened 3 years ago
Last modified 23 months ago
Haikuporter doesn't help building hybrid packages
| Reported by: | pulkomandy | Owned by: | brecht |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | haikuporter | Version: | |
| Severity: | normal | Keywords: | |
| Cc: |
Description
There is no easy way to build an "hybrid" package with Haikuporter (for example, build a gcc4 lib to install on a gcc2-hybrid system).
I suggest at least the following changes :
- Set a variable in the shell environment that tells the current compiler (this will be set to x86/gcc2 or x86/gcc4) :
ARCH=`readlink /boot/develop/abi/current`
- Provide some predefined variables, according to the current OS and compiler setting :
libdir=/boot/common/lib/gcc4 # on gcc2h with gcc4 compiler libdir=/boot/common/lib/gcc2 # on gcc4h with gcc2 compiler libdir=/boot/common/lib/ # other cases
- Name the generated optional package files properly (so we'd have gcc4h and gcc2h packages alongside the existing gcc2 and gcc4 ones).
Currently, it is not possible to use haikuporter to build Caya on a gcc2h system.
Change History
comment:1 Changed 2 years ago by scottmc
- Component changed from default to haikuporter
- Owner set to brecht
comment:2 Changed 23 months ago by scottmc
- Resolution set to duplicate
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.

Moved to new site: http://bb.haikuports.org/haikuports/issue/15/haikuporter-doesnt-help-building-hybrid