Le 16/10/2012 16:02, KP Kirchdoerfer a écrit :
> Hi Yves;
>
> I don't like neither, because it tends to clutter buildtool.*.
>
> Maybe it's possible to
> a) work with<?include>  and<?include64>, something similar and an env
> variable. That way buildtool.mk and buildpacket needs work.
> or
> b) to work with different source definitions (/conf/sources.d/openssl
> and ../openssl64) and providing seperate buildtool.* files for 32 and 64
> bit? It will also require an env variable and some logic in buildtool.
>
> Both, and esp. option b) seems to me less intrusive for the current
> buildenv than your ideas.
Hi KP,
but option b) need to duplicate a lot of buildtool.cfg files, and the 
maintenance will be more difficult (2 files to maintain instead of one).

Yves

------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to