[Slackbuilds-users] libcddb and libcdio: circular build dependencies

[Eric Hameleers (SBo)]

Niki Kovacs schreef:
> Niki Kovacs a écrit :
>> Hi,
>>
>> I'd like to build libcddb and libcdio. The two packages depend on each 
>> other for compilation, e. g. libcddb needs libcdio to build correctly, 
>> and libcdio needs libcddb. It's a catch 22.
>>
>> I'm searching a solution for this, but I'm rather clueless. Maybe do this:
>>
>> Write a SlackBuild for libcddb that first builds libcdio and installs 
>> the resulting lib into some temporary directory. Then build libcddb 
>> against that temporary directory. And then, once libcddb is built and 
>> installed, write an individual SlackBuild for libcdio.
>>
>> I've never done such a thing, so I'd like to know if it's feasible *in 
>> theory*. If someone competent here says that it is, I'll work out the 
>> details by myself.
> 
> Ah... this looks like the answer:
> 
> http://www.slacky.eu/forum/viewtopic.php?t=11395&highlight=libcdio+libcddb
> 
> Comprendo un poco, ma che casino...

Well that README was the basis for my lines in the vlc script:

# Circular dependencies need these loops:
make_cdio --without-vcd-info || exit 1
make_vcd || exit 1
make_cdio || exit 1

If you want to make a standalone package for cdio, you will indeed
have to build vcd and cdio into a temporary directory and point your
compiler and linker to that path when building the final cdio package.

Pat does basically the same with pine/imapd.

Cheers, Eric