Re: [CsMain] Build Process

[John A. <joh...@co...>]

Sorry for the delay in reply.  I've been plagued by a hardware failure!

Anyway, I'm back up now.   No I didn't use the .spec files from the CVS 
tree. Honestly, I didn't even notice they were there.  I wrote some new 
specs from scratch that seem to work very well.  They are mostly plain 
with some modifications to accomidate the Planeshift build scripts which 
the .so and .h files to be in a different place than where they go after 
a jam install.

The spec files are posted at http://chesty.homedns.org:4572/planeshift/ .

If anyone can suggest any improvements, I'm all for it! 



Reed Hedges wrote:

>
> On Dec 30, 2004, at 11:24 PM, John Anderson wrote:
> ... lots ...
>
>> The build process of planeshift expects the $CRYSTAL and $CEL
>> directories to look like they do after a ./configure and jam.  Crystal
>> and CEL both have the capability to jam install.
>
>
>
> My guess is that the reason that Planeshift uses those environment 
> variables is so that you can keep updating CS & CEL from CVS without 
> having to uninstall, rebuild, & reinstall each time.
>
> It should work fine with a standard install process as well though.
>
> You mentioned making RPMs.  Were you able to use the RPM specs from 
> the CS source tree? Did you need to make any changes to them if so?
>
>
> Reed
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Crystal-main mailing list
> Cry...@li...
> https://lists.sourceforge.net/lists/listinfo/crystal-main
> Unsubscribe: 
> mailto:cry...@li...?subject=unsubscribe
>