On Wed, Sep 30, 2015 at 4:28 PM, Freddie Chopin <freddie.cho...@gmail.com>
wrote:
> > Yeah, they can be handy :). Part of me thinks that we could just use
> groups
> > for inputs/outputs and not list any files manually. Though we'd also have
> > to fix the explicit-listing-of-output-files issue for that to work.
>
> This is something (partially) close to what I've done in my project. If I
> archive multiple objects to an archive libsomething.a in output/some/path/
> then I also put this file in $(TOP)/output/some/path/<libsomething.a>. By
> passing such group to a function (that generates some rule - for example
> to do
> the linking) I can get the type of the file from the extension in the group
> name (".a") and I can get the path from the whole string. I actually pass
> only
> the real path to file to the function, which internally is converted to
> proper
> group. Lua parser gives you many possibilities, but because not many people
> use it (noone? (; ) most of the "proper ways of doing something" still
> wait to
> be discovered (;
>
Hmm, can you give an example here? I don't understand why you'd want to
have libsomething.a and then a <libsomething.a> group - after all, an
archive is really just a group of objects :). I'm curious to see how you're
using it!
-Mike
--
--
tup-users mailing list
email: tup-users@googlegroups.com
unsubscribe: tup-users+unsubscr...@googlegroups.com
options: http://groups.google.com/group/tup-users?hl=en
---
You received this message because you are subscribed to the Google Groups
"tup-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tup-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
