From: Joerg F. <jf...@sa...> - 2004-04-29 08:14:57
|
>>>>> "Darrell" == Darrell Schiebel <dr...@nr...> writes: Darrell> On Wednesday, April 28 2004 at 17:34+0200, Joerg Faschingbauer wrote: >>> >>> I'm trying to build this for packaging with RPM (so I can get others to >>> try ccmtools, if it looks promising). Currently I have to sed most of >>> the Makefiles to patch the repo location not to install into /usr (BTW, >>> what is the repo for?), see below. Is there an easier way to build >>> cpp-environment in an intermediate location for later >>> installation via RPM? >> >> Why don't you give the prefix you want? Like so, >> >> confix.py '--prefix=/home/drs/dev/ccmtools/cpp-environment/root' >> '--buildroot=/home/drs/dev/ccmtools/cpp-environment' --bootstrap >> --configure --make --targets=install >> >> I believe the $(prefix) macro in the Makefiles is somewhat private >> anyway, in a sense that it should not be overridden by the user. >> >> Or am I missing something (I guess so)? I've never built RPMs. Darrell> Well, (too) often packages use the 'prefix' to compile in Darrell> paths for things like finding help files, shared object files, Darrell> state files, etc. So when I build RPMs I try to specify the Darrell> final resting place as the 'prefix' and then just coerce the Darrell> install step to install to an intermediate location. This seems Darrell> to be something confix does not support (though the 'setup.py' Darrell> which builds confix does support it). I see. The fact that the repo directory is an absolute path in the generated Makefile is clearly a bug. You might want to give 1.3.pre22 (sic!) a try, where this is fixed, so substituting $(prefix) should be just fine now. Joerg |