Re: {var_*} in actions defined in modules

Adriaan de Groot wrote:

> Consider this:
> 
> LDFLAGS=-bong
> 
> :ltlib { var_LDFLAGS = -module -avoid-version -no-undefined }
> 	...
> 
> 
> Now, the point is that for linking purposes, LDFLAGS from attributes
> should be used, not the recipe variable. Except:

Shouldn't that be:

  :ltlib target : { var_LDFLAGS = -module -avoid-version -no-undefined }
 	...

The ":ltlib" options are given right after the command, but attributes
for building after the ":".

> Aap: /mnt/src/kde-HEAD/kdepim/libtool --mode=link --tag=CXX g++ -bong   -o 
> conduit_null.la build-FreeBSD4_9_RC/setup_base.lo build-FreeBSD4_9_RC/
> null-conduit.lo build-FreeBSD4_9_RC/null-factory.lo
> 
> It looks like the new variable lookup code forgets to look in the
> attributes.  I don't really know where to look for this -- expand() is
> called from aap_shell(), but I don't think the problem is at runtime,
> but at AAP compile time.

In add_buildrule() there is this remark:

	# TODO: implement "cmd_attr".

But i'm not sure what it is that remains to be implemented, cmd_attr is
dictionary used to lookup things like "installvar" and "ojbecttype".

-- 
hundred-and-one symptoms of being an internet addict:
175. You send yourself e-mail before you go to bed to remind you
     what to do when you wake up.

 /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net   \\\
///          Creator of Vim - Vi IMproved -- http://www.Vim.org          \\\
\\\              Project leader for A-A-P -- http://www.A-A-P.org        ///
 \\\  Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html  ///


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php