[M3devel] M3Config contains paths to installation directory.

[Dragiša Durić]

cm3 -?
...
> CM3_INSTALL_PREFIX path prefix to prepend to filenames being installed,
>                  "make DESTDIR=" behaviour for cm3
> 

This is one patch I've introduced earlier and it's excellent conduit for
RPM packaging scripts I develop. I am using it like this:


> export CM3_INSTALL_PREFIX=$RPM_BUILD_ROOT
> 
>  ./scripts/do-pkg.sh realclean m3core libm3
> 
>  ./scripts/do-pkg.sh buildship m3core libm3
> 

Please let me know if your script fails on you mentioning mkdir failure.
I have workaround for it (as Jay did not accept my report as a bug).


I'll put my RPM script in repository RSN.

dd

On Wed, 2009-07-15 at 18:19 -0700, Peter Eiserloh wrote:
> Hi Jay,
> 
> Do you know of any way to tell the build system that the
> final installation directory is located in one place, but
> that the software is to actually be shipped (temporarily)
> to a staging directory.
> 
> Specifically, libm3/src/config contains a m3makefile that
> derives the M3Config interface, containing a number of
> paths to the installation root directory.  
> 
> This is the normal situation for most people, but I am
> installing to a temporary directory, for packaging purposes.
> The packaging software later installs the package into
> the correct location.
> 
> Whenever I build the system, M3Config always contains
> the paths to my staging area.
> 
> I would like some way of specifying to the build system
> that the final (or real) installation root is one thing,
> but "ship" would actually install into a different one.
> 
> 
> 
> +--------------------------------------------------------+
> | Peter P. Eiserloh                                      |
> +--------------------------------------------------------+
> 
> 
>       
-- 
Dragiša Durić <dragisha at m3w.org>