[oi-dev] Distribution build system

[TJ Yang]

On Fri, Apr 8, 2011 at 7:04 PM, Andrzej Szeszo <aszeszo at gmail.com> wrote:
> Hi TJ,
>
> This is great that you are trying TWW tools.
>
> I was actually thinking about using a GNU make based system, possibly with
> few helper scripts.

FREEBSD:make buildworld
How about OpenIndiana: make buildworld  too ;)


>
> The advantage of using Makefiles is that everyone is familiar with them,
> incremental builds are possible and also parallel builds are possible.
>
Agree about using make.

At work, I do use make on top of TWW sb/pb tools to achieve
incremental builds and parallel builds(not actually doing this right
now).
for parallel/distributed builds, I played with distcc before but end
up using ElectricCloud(different name now)[3].

I am hoping OI project can implement C.I. tools to distribute the
build(once above is ready).

> Can you point me to some docs about TWW tools describing what they can do? I
> have never heard about them :)

See [2] Reference section. the best doc so far is still the RTFM. each
tools has detail doc in its manpages.

>
> Thanks,
>
> Andrzej
>
>

[1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
[2] http://wiki.openindiana.org/oi/Building+O.I.+by+sb
[3] http://www.electric-cloud.com/products/electricaccelerator.php

tj

> On 04/06/11 16:44, TJ Yang wrote:
>>
>> On Wed, Apr 6, 2011 at 10:43 AM, TJ Yang<tjyang2001 at gmail.com>  wrote:
>>>
>>> Hi, Deano
>>>
>>> I am converting all the consolidations building instruction into xml
>>> files.
>>> and this xml file can be playbacked but /opt/TWWfsw/bin/sb
>>> (sb=software build) tool.
>>
>> s/but/by/
>>
>>> Very similar following command to create  O.I. CD/USB image.  except
>>> the abstraction is one level higher.
>>>
>>>  pfexec distro_const build ./new_slim_cd_x86.xml
>>>
>>> So for this digitization effort is to generate O.I. sparc image to
>>> provide alternative OS that our Sparc hardware can run freely.
>>>
>>> I don't expect it got adopted by this group since TWW Inc.'s GNU
>>> tool-sets is not well-known.  But I am documenting this approach at
>>> R1.
>>>
>>> tj
>>>
>>> R1: http://wiki.openindiana.org/oi/CPAMTWW
>>>
>>> On Wed, Apr 6, 2011 at 7:13 AM, Deano<deano at rattie.demon.co.uk>  wrote:
>>>>
>>>> Hello,
>>>>
>>>> The conversation on the Distributed build system stalled on finer points
>>>> but
>>>> the large idea seemed to have everyone support. A continuous build
>>>> system,
>>>> that automatically went through all consolidations would be a major step
>>>> forward for the OI development process.
>>>> So lets get things moved on a least for the most basic system we all
>>>> agree
>>>> would be useful. I looked into some more advanced build systems (Scons,
>>>> WAF,
>>>> etc.) but tbh all were slightly overkill for what the basic simple
>>>> system
>>>> needs which is simply a makefile or script that grabs each
>>>> consolidation,
>>>> sets up the environment, builds and moves onto the next (with
>>>> appropriate
>>>> error handling etc.)
>>>>
>>>> Aszezo has some idea and how to get this party started I believe, so
>>>> probably best for him to make more concrete suggestions?
>>>>
>>>> If we could get a empty framework in place and running, we could then
>>>> pop in
>>>> each consolidation in turn when ready, and therefore gradually get our
>>>> continuous build system working, the particularly troublesome ones don't
>>>> have to stop the easier ones.
>>>>
>>>> A hack-a-thon might make an ideal time for people to get together and
>>>> push
>>>> this all together?
>>>>
>>>> Thoughts please,
>>>> Deano
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> oi-dev mailing list
>>>> oi-dev at openindiana.org
>>>> http://openindiana.org/mailman/listinfo/oi-dev
>>>>
>>>
>>>
>>> --
>>> T.J. Yang
>>>
>>
>>
>



-- 
T.J. Yang