Subject | Re: [firebird-support] developer support .. build -> release |
---|---|
Author | Paul Reeves |
Post date | 2005-08-09T09:18:02Z |
On Monday 08 August 2005 21:37, Mark Probert wrote:
code for 'make install' and perhaps 'make packages' for the linux port
and hack it for Solaris. In any case, it should not be that difficult.
Firebird operates out of a single directory. Most of the install stuff is
just making sure that it 'fits' with the host OS. This means putting
appropriate sym links in /usr, for example, and making sure that
(x)inetd knows about it (if you are installing classic).
BTW, you will probably find more help with porting and building problems
on the fb-devel list. fb-support is for users needing support with
production versions of Firebird.
Paul
--
Paul Reeves
http://www.ibphoenix.com
Supporting users of Firebird and InterBase
> Hi ..I haven't come across one. I think you have no choice but to look at the
>
> Is there any document that details how to go from the build environment
> to the release environment? I have created the build (it all lives in
> pieces in ($BASE)/temp) but I don't know how to put all the parts
> together in a meaningful manner.
>
code for 'make install' and perhaps 'make packages' for the linux port
and hack it for Solaris. In any case, it should not be that difficult.
Firebird operates out of a single directory. Most of the install stuff is
just making sure that it 'fits' with the host OS. This means putting
appropriate sym links in /usr, for example, and making sure that
(x)inetd knows about it (if you are installing classic).
BTW, you will probably find more help with porting and building problems
on the fb-devel list. fb-support is for users needing support with
production versions of Firebird.
Paul
--
Paul Reeves
http://www.ibphoenix.com
Supporting users of Firebird and InterBase