Re: Building an RPM from a compiled application

[Bill Woodward <wpwood dazel com>]

"Mike A. Harris" wrote:
> 
> On Tue, 12 Sep 2000, Bill Woodward wrote:

[snip]

> 
> >2) Build normally, and just use rpm for the packaging.  This seems to
> >make more sense from our build environment, but I can't figure out how
> >to do it.
> 
> This is essentially what I just described above.  What is the
> normal procedure from source tarball for building your app and
> installing it?
> 
> ./configure
> make all
> make install
> 
> Or something different?  Post how you do it, and we'll see if we
> can come up with some suggestions.
> 

Basically, we have a config file (rc.buildtools) and a build script
(buildall).  Nothing terribly sophisticated, buildall reads the config
file, resolves dependencies on other source trees (basically by just
pulling over the binaries, libraries, and header files), checks the
source out of CVS, runs imake to create the makefiles, and runs make. 
The end result of the build is a tar file with relative paths,
containing all of the files we need to install.

My current thinking is just to untar that tar file into RPM_BUILD_ROOT
and list the files in the %files section and hope that it works.  We'll
see :-)

Thanks,
- Bill

-- 
<>< ><> <>< ><> <>< ><> <>< ><> <>< ><> <>< ><> <>< ><> <><
Bill Woodward (Bill_CCHKK@yahoo.com or wpwood@dazel.com)
http://members.xoom.com/Bill_CCHKK