LUMIERA.clone/doc/devel/rfc/MakeSconsTheOfficialBuildSystem.txt
Ichthyostega b556d2b770 clean-up: comb through the historical pages to fix markup errors
Some sections of the Lumiera website document meeting minutes,
discussion protocols and design proposals from the early days
of the project; these pages were initially authored in the
»Moin Moin Wiki« operated by Cehteh on pipapo.org at that time;
this wiki backed the first publications of the »Cinelerra-3«
initiative, which turned into the Lumiera project eventually.

Some years later, those pages were transliterated into Asciidoc
semi-automatically, resulting in a lot of broken markup and links.
This is a long standing maintenance problem problem plaguing the
Lumiera website, since those breakages cause a lot of warnings
and flood the logs of any linkchecker run.
2025-09-21 05:40:15 +02:00

89 lines
1.9 KiB
Text

Make Scons the official build System
====================================
// please don't remove the //word: comments
[options="autowidth"]
|====================================
|*State* | _Final_
|*Date* | _Mi 11 Jan 2012 21:45:58 CET_
|*Proposed by* | Christian Thaeter <ct@pipapo.org>
|====================================
********************************************************************************
.Abstract
_Bless SCons into the default build system for Lumiera._
********************************************************************************
Description
-----------
//description: add a detailed description:
So far we are using Autotools and SCons in parallel.
Over time the need arose to have one
reliable supported build system. This shall be SCons.
Tasks
~~~~~
// List what needs to be done to implement this Proposal:
// * first step ([green]#✔ done#)
// * second step [,yellow]#WIP#
Nothing to do except for releases SCons _must be working_ and all non functional
build systems will be stripped on the release branches.
////
Discussion
~~~~~~~~~~
Pros
^^^^
// add a fact list/enumeration which make this suitable:
// * foo
// * bar ...
Cons
^^^^
// fact list of the known/considered bad implications:
Alternatives
^^^^^^^^^^^^
//alternatives: explain alternatives and tell why they are not viable:
Rationale
---------
//rationale: Give a concise summary why it should be done *this* way:
////
Conclusion
----------
//conclusion: When approved (this proposal becomes a Final)
// write some conclusions about its process:
result of discussions and evaluation during the last years
Comments
--------
//comments: append below
.State -> Final
//add reason
Decided on the December 2011 Developer meeting.
Christian Thaeter:: 'Wed 11 Jan 2012 22:28:36 CET' ~<ct@pipapo.org>~
//endof_comments:
''''
Back to link:/x/DesignProcess.html[Lumiera Design Process overview]