binarycloud-dev

[binarycloud-dev] make targets

[Alex B. <en...@tu...>]

hi all,

Anyone see anything I'm missing or that you would like to see added?
I'm nearly done with the Configure system spec, and the new Makefile spec.

This is _extremely_ important stuff, please read it carefully and put some
thought into it... I think we'd all like to have a final-ish make system so
we can move on to managers and builders :)

As you can see below, the idea is make the Configure system as simple as
possible... and there wouldn't need to be more than 5 makefile templates.

_alex


Make targets for new make system
---------------------------------
binarycloud/
    all = alias to base, sites, and phpdoc
    clean = rm build dir
    phpdoc = runs make phpdoc in sub dirs
    (site_name) = runs make all in site_name dir
    sites = runs make all in each site dir
    base = runs make all in base dir
    user = alias to sites

Makefiles should be generated in all subdirectories of the source tree,
minus some exclusions at bottom.

For each directory that contains only a makefile and other directories,
these targets:
    all = runs make all in all sub dirs
    clean = removes current dir from all build trees
    phpdoc = runs make phpdoc in all sub dirs
    (dir_name) = runs make all in dir_name
    *the list of dirs is generated by Configure

For each directory that contains a mix of files and directories:
    all = runs make all in all sub dirs, and 'files'
    clean = removes current dir from all build trees
    files = runs InstallCode.php and BCC.php on all files in this dir.
    phpdoc = runs make phpdoc in all sub dirs, and phpdoc on files list
    (dir_name) = runs make all in dir_name
    *the list of dirs is generated by Configure
    (file_name) = runs InstallCode.php and BCC.php on file_name.
    *the list of files is generated by Configure

For each directory that contains only files:
    all = runs InstallCode.php and BCC.php on all files in this dir.
    clean = removes this dir from all build trees
    phpdoc = runs phpdoc on all files in this dir

For each directory that contains only files under resources/images/:
    all = runs InstallImg.php on all files in the dir
    clean = removes this dir from all build trees


Exclusions
---------------------------------
binarycloud/base/utils/
    (This may be used is it should not really be part of the source tree.
     It might be moved to binarycloud/utils/ or binarycloud/make/.)
    
binarycloud/docs/

RE: [binarycloud-dev] make targets

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

Hi Alex,

the make stuff looks very fine to me, just one thought:


>Make targets for new make system
>---------------------------------
>binarycloud/
>    all = alias to base, sites, and phpdoc
>    clean = rm build dir
>    phpdoc = runs make phpdoc in sub dirs
>    (site_name) = runs make all in site_name dir
>    sites = runs make all in each site dir
>    base = runs make all in base dir
>    user = alias to sites

What about adding target: distro (or dist, or distribution, or..). This is
basically make all plus running some extra tools/scripts (i.e. ZendEncoder,
tar/gzip, generating snapshots etc) that can be configured in a file.


Andi

Re: [binarycloud-dev] make targets

[Alex B. <en...@tu...>]

> Hi Alex,
> 
> the make stuff looks very fine to me, just one thought:
> 
> 
>> Make targets for new make system
>> ---------------------------------
>> binarycloud/
>>    all = alias to base, sites, and phpdoc
>>    clean = rm build dir
>>    phpdoc = runs make phpdoc in sub dirs
>>    (site_name) = runs make all in site_name dir
>>    sites = runs make all in each site dir
>>    base = runs make all in base dir
>>    user = alias to sites
> 
> What about adding target: distro (or dist, or distribution, or..). This is
> basically make all plus running some extra tools/scripts (i.e. ZendEncoder,
> tar/gzip, generating snapshots etc) that can be configured in a file.

That's an excellent idea.

MakeConf will cover the configuration of that stuff, but I think that's
great.

I'll add it to the spec and push those to CVS (and to the list) today.

best,

_alex

Re: [binarycloud-dev] make targets

[Jason H. <jc...@ey...>]

How about this..  You can define the path to your Apache docroot in the
MakeConf, and add a target such as 'make install' to not only build your
tree, but to also install it to your document root.  (Could be symlink,
or a copy (??))

jason



> Anyone see anything I'm missing or that you would like to see added?
> I'm nearly done with the Configure system spec, and the new Makefile spec.

Re: [binarycloud-dev] make targets

[Alex B. <en...@tu...>]

> How about this..  You can define the path to your Apache docroot in the
> MakeConf, and add a target such as 'make install' to not only build your
> tree, but to also install it to your document root.  (Could be symlink,
> or a copy (??))

I far prefer symlink, because it means we don't have to add any additional
complexity to the already complex make system :)

_a

RE: [binarycloud-dev] make targets

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

Hi Alex,

>I far prefer symlink, because it means we don't have to add any additional
>complexity to the already complex make system :)

Good point.

so <deploy> could make a symlink :-)

Andi

RE: [binarycloud-dev] make targets

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

Hi jason,

>How about this..  You can define the path to your 
>Apache docroot in the
>MakeConf, and add a target such as 'make install' to not 
>only build your tree, but to also install it to your 
>document root.  (Could be symlink,
>or a copy (??))

That's very cool...

<deploy>/var/www/mysite</deploy>

Andi

Re: [binarycloud-dev] make targets

[Alex B. <en...@tu...>]

how abut the attached...

it's more flexible because it lets you make symlinks wherever you want :)

_a

> Hi jason,
> 
>> How about this..  You can define the path to your
>> Apache docroot in the
>> MakeConf, and add a target such as 'make install' to not
>> only build your tree, but to also install it to your
>> document root.  (Could be symlink,
>> or a copy (??))
> 
> That's very cool...
> 
> <deploy>/var/www/mysite</deploy>
> 
> Andi
> 
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> https://lists.sourceforge.net/lists/listinfo/binarycloud-dev
> 

RE: [binarycloud-dev] make targets

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

Hi Alex,

very groovy!


>how abut the attached...
>
>it's more flexible because it lets you make symlinks wherever you want :)
>
>_a
>
>> Hi jason,
>> 
>>> How about this..  You can define the path to your
>>> Apache docroot in the
>>> MakeConf, and add a target such as 'make install' to not
>>> only build your tree, but to also install it to your
>>> document root.  (Could be symlink,
>>> or a copy (??))
>> 
>> That's very cool...
>> 
>> <deploy>/var/www/mysite</deploy>
>>