On 2020-09-25, Howard Chu wrote:
> Bob Friesenhahn wrote:
> > ... static libraries do not technically have "dependencies" since they
> > only represent a compilation step (no linking). If a static
> > library may also be built as a shared library then it may have
> > dependencies and should be de
Bob Friesenhahn wrote:
> ... static libraries do not technically have "dependencies" since they only
> represent a compilation step (no linking). If a static
> library may also be built as a shared library then it may have dependencies
> and should be described as such.
I've always found this
On Fri, 25 Sep 2020, Oleg Smolsky wrote:
On 2020-09-25 09:28, Bob Friesenhahn wrote:
With convenience libraries, there may be a necessary build order but the
object files are not 'linked' before going into the convenience libraries
(as a proper library would be) so all linking is when the fina
On Fri, Sep 25, 2020 at 11:38 AM Nick Bowler wrote:
> On 2020-09-25, John Calcote wrote:
> > On Fri, Sep 25, 2020 at 10:45 AM Bob Friesenhahn <
> bfrie...@simple.dallas.tx.us> wrote:
> >> Exactly! It might as well be a tar file except that the 'ar' archiver
> >> knows how to add/update/remove f
On 2020-09-25 09:28, Bob Friesenhahn wrote:
With convenience libraries, there may be a necessary build order but
the object files are not 'linked' before going into the convenience
libraries (as a proper library would be) so all linking is when the
final library or program is linked using the o
On 2020-09-25, John Calcote wrote:
> On Fri, Sep 25, 2020 at 10:45 AM Bob Friesenhahn
> wrote:
>> Exactly! It might as well be a tar file except that the 'ar' archiver
>> knows how to add/update/remove files from it and that is not possible
>> with a tar file. The ability to do incremental upd
Hi Bob,
On Fri, Sep 25, 2020 at 10:45 AM Bob Friesenhahn <
bfrie...@simple.dallas.tx.us> wrote:
> On Fri, 25 Sep 2020, Oleg Smolsky wrote:
>
> > Well, AFAIK any well-formed .a file (an archive) is a static lib. And
> these
> > can be passed to the linker. Are you saying that libtool extracts th
On 2020-09-25, Oleg Smolsky wrote:
> On Fri, Sep 25, 2020 at 6:58 AM Bob Friesenhahn
> wrote:
> > Libtool convenience libraries are not "real" static libraries.
> > Instead they are object files stored in an archive file. Prior to
> > use (when linking using libtool) the objects are extracted a
On Fri, 25 Sep 2020, Oleg Smolsky wrote:
Well, AFAIK any well-formed .a file (an archive) is a static lib. And these
can be passed to the linker. Are you saying that libtool extracts the
individual .o files instead passing -lfoo (for libfoo.a)?
Exactly! It might as well be a tar file except t
On Fri, Sep 25, 2020 at 6:58 AM Bob Friesenhahn <
bfrie...@simple.dallas.tx.us> wrote:
> On Thu, 24 Sep 2020, Oleg Smolsky wrote:
>
> Libtool convenience libraries are not "real" static libraries.
> Instead they are object files stored in an archive file. Prior to use
> (when linking using libtoo
On Thu, 24 Sep 2020, Oleg Smolsky wrote:
Libtool convenience libraries are not "real" static libraries.
Instead they are object files stored in an archive file. Prior to use
(when linking using libtool) the objects are extracted and passed to
the linker directly (perhaps with renaming to assu
On Thu, Sep 24, 2020 at 12:17 PM Nick Bowler wrote:
> On 2020-09-24, Oleg Smolsky wrote:
> > Hello, I'm working on an autotools-based build system and finally
> decided to
> > look into these messages:
> >
> > CXXLDlibtop.la
> > copying selected object files to avoid basename conflicts...
12 matches
Mail list logo