Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
Prior to this commit, -module was not respected when the specified
output name happened to end with the platform's shared library
suffix. In addition, the logic for generating shared libraries
with -module in effect has been incomplete and partially also
incorrect.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The above internal interface is now doing the right thing, namely to
split the argument vector between object arguments and all other arguments,
then rejoin the arguments by placing object arguments first, and all other
arguments last.
|
|
|
|
|
|
|
|
|
|
tool
====
slibtool-shared (or slibtool with -disable-static).
scenario
========
- create libfoo.so (via libfoo.la).
- create libbar.a (via libbar.la), with libfoo.la as an input argument.
Before this fix, slibtool failed since it could not find libfoo.a.slibtool.deps.
After this fix, slibtool properly handles this scenario, first by detecting that
there is no archive for which secondary dependencies need to be processed, and then
by detecting that libfoo.a is a symlink to /dev/null.
|
|
|
|
|
|
|
|
|
|
|