Tinderbox newbie questions.

[Dan Casey]

Thank you both.  For now at least, I'm just going to worry about the
ports.. The base os and kernel are the easy parts :).

I have a few more questions about tinderbox however. 
1.  I want to control the environment when compiling.  Looking through
the mailling list I found that you can use a build.env file for this.  I
copied my make.conf into build.env and so far it has been working ok. 
Looking at the src, I now see that it is just sourcing this file in a
/bin/sh script.  I should probably go back and prefix all my variables
with "export ".  But, how would I control something on a per-port
basis.  How would I convert the following section of my make.conf to
work in build.env.  This is needed for ports that do not have 'options'
files.

### mysql Server
.if ${.CURDIR:M*/databases/mysql50-server}
BUILD_OPTIMIZED=YES
BUILD_STATIC=YES
WITH_PROC_SCOPE_PTH=YES
WITH_ARCHIVE=YES
.endif


Or. Is there a way that I can inject my make.conf into the build.



Tim Bishop wrote:
> On Fri, Apr 13, 2007 at 04:04:26PM -0400, Joe Marcus Clarke wrote:
>   
>> On Fri, 2007-04-13 at 15:33 -0400, Dan Casey wrote:
>>     
>>> 4. Is it possible to package a kernel and base system?  So for I have
>>> every box building there own.  I have stripped out a lot from the SMP
>>> kernel, and also I need to make modifications to syslimits.h before
>>> compiling. 
>>>       
>> TB only deals with the ports tree.  There is a src tinderbox available
>> under src/tools/tools/tinderbox.
>>     
>
> Maybe the freebsd-update tools could be used? I think the server side
> stuff is available and could be used to build custom source and kernel.
>
> Tim.
>
>