Hi,
You should know that (order-only) inputs may be an over-approximation of
the actual inputs.
As long as you create no dependency loops, you can just as well add all
the libraries to a group and use it as an input to your gcc call.
More generally, if you want enough expressive power to avoid repeating
inputs and command flags, you should look at tup groups and/or bins, and
also variables and !-macros.
If that is not enough, you may want to consider the lua backend. The
ultimate option is to use a programming language of your choice to
generate Tupfiles, like mozilla does. But that may be a bit overkill for
you ;-)
I hope it helps,
-- Layus.
On 28/03/19 21:26, Ben Boeckel wrote:
On Thu, Mar 28, 2019 at 11:01:04 -0700, Robin wrote:
What flag I am referring to '-lname -L/path/to/lib'. GCC or linker must
look up and read the library right? Correct me if I am wrong.
Ah, I see what you mean now. Best would be to instead of relying on
linker search paths at all to just have `/path/to/lib/libname.so`
directly on the link line (e.g., this is what CMake prefers to do). I
don't know if Tup has built-in support for this (unlikely), but Lua
would probably be best for this.
--Ben
--
--
tup-users mailing list
email: [email protected]
unsubscribe: [email protected]
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
