From: Keresztfalvi Laszlo <kereszt@crossys.com>
To: pthreads-win32@sources.redhat.com
Subject: Re: Static linking under win32
Date: Mon, 06 Dec 2004 10:46:00 -0000 [thread overview]
Message-ID: <20041206104619.GC3208@cross> (raw)
In-Reply-To: <41B40FB0.4070503@callisto.canberra.edu.au>
For the apropo PW32 have just introduced the DLL and API versioning..
> If you statically link pthreads-win32 with your application, you will
> need to provide access to object files such that your users can relink
> the application with, for example, an updated pthread-win32. That is,
> you might provide yourapp.obj such that a user could build pthreadVC.obj
> from source and relink to create yourapp.exe. Both the GPL and the LGPL
If I develop a commercial application then stability rules and I would use a
choosen version of pthread (or any other external) library which I link
against, usually lagging some versions (to be real-life tested). So, even if
I provide the object files I cannot accept any claims if you link it with
eg. a newer version of the library either statically or dynamically.
Moreover, I usually use more than one external library with some licenses so
then I must provide those too to really enable you to relink..
I think this would be not a real case if the application is not something
simple and you provide good support which is generally your business..
Otherwise ask lawers who play that game ;)
Regards,
Laszlo
next prev parent reply other threads:[~2004-12-06 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200412060635.iB66ZiF01425@callisto.canberra.edu.au>
2004-12-06 7:52 ` Ross Johnson
2004-12-06 9:57 ` Alexander Terekhov
2004-12-06 10:46 ` Keresztfalvi Laszlo [this message]
2004-12-06 17:35 ` Phil Frisbie, Jr.
2004-12-06 17:47 ` Gili
2004-12-06 18:07 ` Alexander Terekhov
[not found] ` <E1CbMx8-0006Ad-S5@m1.dnsix.com>
2004-12-06 20:08 ` Keresztfalvi Laszlo
[not found] <200412061747.iB6HlGug210260@mtagate1.de.ibm.com>
2004-12-06 18:53 ` Alexander Terekhov
[not found] <200412060337.iB63beF00812@callisto.canberra.edu.au>
2004-12-06 6:22 ` Ross Johnson
2004-12-06 6:35 ` Gili
2004-12-06 3:37 Gili
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041206104619.GC3208@cross \
--to=kereszt@crossys.com \
--cc=pthreads-win32@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).