Re: [binarycloud-dev] Makefile blues

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

> 
> Well yes, but the heart of the problem is that $BUILD_DIR is now a
> relative variable.
> This becomes a serious pain as binarycloud/base/Makefile, etc has no
> idea which site and language you are wanted to build to.

Ah, now I see the point.

For example:
You've made a modification to some core class and want to propagate that
change throughout all your sites.

You can assume that you should go through all sites and make for each one...

so I think determining the set of sites and their languages should be a
function of the top-level makefile.

(or, much better, of a ./Configure script which _generates_ the top level
Makefile.in)

_alex


> I've gotten this (what I've got so far) to work, though I'm not too
> happy with it.  It just all seems too pasty. (aka not creamy enough)
> 
> jason
> 
> 
> alex black wrote:
>> 
>>> Ugh.  This isn't going to be fun.
>>> 
>>> Here's an example hurdle I just tripped over.
>>> 
>>> 
>>> binarycloud/Makefile
>>> - runs base/Makefile
>>> - which installs packages into the build directory. $BUILD_DIR.
>>> 
>>> 
>>> The build directory may be binarycloud/build/site_name8373/en/
>> 
>> Right.
>> 
>>> Currently, my Makefile.in sees $BUILD_DIR as
>>> $(BC_DIR)/build/$(BC_SITE)/$(BC_LANG)
>>> 
>>> So if you run 'make' from binarycloud/, somehow it's supposed to know
>>> which site and language you want to install to.
>> 
>> Yes, you will need to parse the Languages.xml file in
>> user/site_name/conf/Languages.xml and loop through the array of languages
>> building the code for each language.
>> 
>> Of course that will require you to use a php command line script, and not
>> default makefile capabilities...
> 
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> https://lists.sourceforge.net/lists/listinfo/binarycloud-dev
>