public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: "Forstner Michael" <Michael.Forstner@cpg.de>
To: <pthreads-win32@sources.redhat.com>
Subject: RE: Create static .lib without .dll [W2K, VC++ 6] [Viren geprueft]
Date: Fri, 14 Feb 2003 12:28:00 -0000	[thread overview]
Message-ID: <4011F019854CC743A74EC317F5779B5D091A00@mail2.cpg.de> (raw)

Thank you for your answer, but I thougt there would be a makefile for building pthreads as a static lib.
Do you know if there exist one?

Regards,
Michael Forstner

> -----Original Message-----
> From: ignace [mailto:ignace.saenen@pandora.be]
> Sent: Friday, February 14, 2003 12:58 PM
> To: Forstner Michael; pthreads-win32@sources.redhat.com
> Subject: RE: Create static .lib without .dll [W2K, VC++ 6] [Viren
> geprueft]
> 
> 
> 
> The easy way: just create a 'Win32 Static Library' project 
> under "File /
> New Project", and load it with your files.
> 
> The harder way: although it is highly you can specify the 
> "-lib" option
> in the linker options or even in the project .dsp directly, 
> but you have
> to make sure you're using the default linker options, see 
> MSDN for more
> information under 'static libraries, creating'.  If you're not
> comfortable with editing .dsp files by hand, then please don't! :)
> 
> Regards,
> i.
> 
> > -----Original Message-----
> > From: pthreads-win32-owner@sources.redhat.com 
> [mailto:pthreads-win32-
> > owner@sources.redhat.com] On Behalf Of Forstner Michael
> > Sent: Friday, February 14, 2003 9:04 AM
> > To: pthreads-win32@sources.redhat.com
> > Subject: Create static .lib without .dll [W2K, VC++ 6]
> > 
> > Hello all,
> > 
> > is there a way to create a static .lib without the .dll 
> with VC++ 6 ?
> > 
> > regards,
> > Michael Forstner
> 
> 

                 reply	other threads:[~2003-02-14 12:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4011F019854CC743A74EC317F5779B5D091A00@mail2.cpg.de \
    --to=michael.forstner@cpg.de \
    --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).