[haiku-development] Re: External package woes (was What to do with termcap?)
- From: Landon Fuller <landonf@xxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Tue, 5 Feb 2013 10:00:28 -0500
On Feb 4, 2013, at 8:44 AM, Axel Dörfler <axeld@xxxxxxxxxxxxxxxx> wrote:
> One short-term compromise I could think of is using a similar mechanism as 3rd
> party, and optionally let the build system download the known sources + Haiku
> build patches (or even source complete packages), and build them as part of
> the
> build system as it was done before externalizing them.
> This would probably be required to be done during Haiku's configure script, so
> that Jam can then work with those packages.
>
> Of course, this would duplicate the package maintaining effort. But maybe
> it's a
> viable solution until a proper one comes along, as the Haiku specific
> config.h/Jamfile for those packages usually already exist from prior work (but
> note that the generated config.h might be target dependent as well).
I think that's a reasonable intermediate step.
On Feb 4, 2013, at 11:49 AM, François Revol <revol@xxxxxxx> wrote:
>
> Just as a reminder, I started with such a scheme long ago, should be
> able to dig the stuff in svn history...
>
> It was hooked in jam though, not configure.
Awesome. I'll dig into this.
-landonf
Other related posts:
