Re: {var_*} in actions defined in modules
Bram Moolenaar <[email protected]>
| Newsgroups | gmane.comp.tools.aap.devel |
|---|---|
| Message-ID | <[email protected]> |
Adriaan de Groot wrote:
> On Sunday 12 October 2003 12:32, you wrote:
> > Shouldn't that be:
> > :ltlib target : { var_LDFLAGS = -module -avoid-version -no-undefined }
>
> Perhaps. As in perhaps is _ought_ to be like that, but it isn't.
>
>
> :ltlib target { var_* assignments for link time } : sources
>
>
> that works, for the final linking step.
Ah, of course. The target, with its attributes, is given to the build
step.
> As for variables for the compile
> steps, those work as well, but need to be specified for each source
> individually, like
>
> :ltlib target : source1 { var_* assignments for compile time }
> source2 { var_* assignments for compile time }
>
> It would be convenient (I know, wishlist, send patches) if you could put var
> assignements at the start of the list of sources for all of them.
I think this exercise makes clear that it's not obvious where attributes
are put. And having to repeat the attributes for the sources should not
be needed.
Does someone have a bright idea how to do this in a simple and
consistent way?
--
hundred-and-one symptoms of being an internet addict:
203. You're an active member of more than 20 newsgroups.
/// 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