RE: [binarycloud-dev] master make process

[Andreas A. <a.a...@th...>]

Hi Alex,

>The idea is to move nearly all of the interesting logic out
>to php scripts instead of meking logic-heavy Makefiles.

Agreed. We then can consider using php only for the make process at a later
point. So we are more independent - users don't need gnutools. This is
especially interesting for the windows world.

BTW: Does anyone have experience with Ant? The Java Make Tool? Is this of
any use for us?


Looks good, Alex.

Andi



>Install.php
>-------------------------------------
>    -Checks the path to see where the file came from. if it's in
>     resources/images, marks it as an image.
>
>    -Checks to see if the file needs preprocessing
>     (does it have a special name?)
>
>    -If so, registers it as such and assignes a 'name handler'
>     to deal with that file.
>
>    -Runs install -Dp on the source file with the proper destination.
>        For source, the destination is determined by one of two factors:
>            -Package declaration in the file
>            -Location in the source tree.
>             (be careful here.. this is ok only for modules, config files,
>              and a few other dirs. Try and put package declarations on
>              everything but markup source.
>        For images, can only ever be in
>        htdocs/resources/images/* or mod/module_name/resources/images/*
>            The latter is handled as a 'mask' on the build htdocs.
>            For example, a source of
>mod/module_name/resources/images/project_name/Image.gif
>            will end up at
>build/site_name/lang_code/htdocs/resources/images/project_name/Image.gif.
>
>    -If the file has a handler assigned, that handler is run
>     and does its job (which may be renaming the file
>     after processing it, etc.)
>
>    -Checks the build file against the source file,
>     matches the modification dates if necessary.
>
>
>PHPDoc.php
>-------------------------------------
>    -Takes the path of the _build_ tree, and target directory.
>     (not the source, as these can contain string keys and other ick)
>    -Builds documentation for that tree, and writes html into
>     target directory.
>     (This dir should be a build dir, but you can modify it
>      however you like)
>
>BCC.php
>-------------------------------------
>    -Takes the path of the file to be processed in the build tree
>    -Runs bcc on that file
>    -Always writes output to same file