Re: [ccmtools-devel] HelloWorld falls silent

[Darrell S. <dr...@nr...>]

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.

	Well, (too) often packages use the 'prefix' to compile in
	paths for things like finding help files, shared object files,
	state files, etc. So when I build RPMs I try to specify the
	final resting place as the 'prefix' and then just coerce the
	install step to install to an intermediate location. This seems
	to be something confix does not support (though the 'setup.py'
	which builds confix does support it).

>BTW, the repo directory contains "module descriptions" of the modules
>you have built. When you are using confix to build a package that uses
>the installed modules, confix uses these descriptions when building a
>dependency graph and generating build instructions. You can view the
>repo files using print_module.py <filename>. (print_module.py is a
>script that comes with confix.)

	Great, thanks. That's what I guessed, but I just wanted to make
	sure... since looking at the files themselves offered no clue :)

								Darrell