Hi all, Yeah. Over linking should be avoid even we have as-needed flag to help. And the reason to use search path is that it will affect the soname of dynamic shared library and runtime linkage.
Precise dependency management is valuable in large scale project. And it is very hard to setup and maintain the dependency by hand. And if tup already support commands as dependency and is able to detect some form of missing input already, it will be best if Tup can support shared library linking dependency automatically, provided there is no circular dependency. I dont know how tup implment the warnning message of missing input. It probably worths a pull request. Best, Robin On Fri, Mar 29, 2019 at 07:37 Ben Boeckel <[email protected]> wrote: > On Fri, Mar 29, 2019 at 03:49:33 +0100, Guillaume Maudoux (Layus) wrote: > > 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. > > I suppose that works, but overlinking is also something to avoid in > general. > > --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. > -- -- 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.
