From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25889 invoked by alias); 31 Mar 2005 07:42:32 -0000 Mailing-List: contact pthreads-win32-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: pthreads-win32-owner@sources.redhat.com Received: (qmail 25848 invoked from network); 31 Mar 2005 07:42:26 -0000 Received: from unknown (HELO mx1.mail.bg) (193.201.172.114) by sourceware.org with SMTP; 31 Mar 2005 07:42:26 -0000 Received: from localhost (web1.mail.bg [193.201.172.98]) by mx1.mail.bg (Postfix) with ESMTP id 4D6C972C347E for ; Thu, 31 Mar 2005 10:42:10 +0300 (EEST) Received: from sun.fadata.bg (sun.fadata.bg [213.240.249.67]) by mail.bg (mail.bG Webmail 4.0.1) with HTTP for ; Thu, 31 Mar 2005 10:42:10 +0300 Message-ID: <1112254930.d6fc30c99fd62@mail.bg> Date: Thu, 31 Mar 2005 07:42:00 -0000 From: Dimitar Panayotov To: pthreads-win32@sources.redhat.com Subject: Re: Re: Static link (MSVC), alteration proposal References: <1112192108.9a7b65f2515a2@mail.bg> <1112226518.19990.69.camel@desk.home> In-Reply-To: <1112226518.19990.69.camel@desk.home> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1251" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: mail.bG Webmail 4.0-cvs X-SW-Source: 2005/txt/msg00052.txt.bz2 > Hi, > Thanks for the changes and the explanations. They > certainly fill a gap. Hello, Ross, and thank you for your detailed attention you attested. > The PTW32_BUILD conditional was added by me. I've never > built the > library statically, and don't test this side of things. > This is because > the library is essentially designed for dynamic linking No, PTW32 is written very clever. 1. Since the sources are written in a way which relies on the headers to determine the type of linkage of all the PTW32 functions, then actually everything is up to the headers. 2. Since all the sources are combined in single one -- , things are quite easy, because you only need to add to your project (or give to it a separate entry in the Makefile), it will be compiled, and then pthread.obj will be included in the final link, and that's it. I admit that the style of the people who have written PTW32, is professional. > Please see the description of:- > > pthread_win32_process_attach_np () > pthread_win32_process_detach_np () > pthread_win32_thread_attach_np () > pthread_win32_thread_detach_np () And thank you for pointing me to the functions which must be used when statically linking with PTW32. I am aware of those, but I forgot to mention them. Sorry. Again, thank you for your attention. Respects. - Dimitar Panayotov develop@mail.bg +359886420488 -------------------------------------- =D2=EE=E2=E0 =EF=E8=F1=EC=EE =E5 =E8=E7=EF=F0=E0=F2=E5=ED=EE =EE=F2 www.ma= il.bg =C1=E5=E7=EF=EB=E0=F2=ED=E0=F2=E0 =EF=EE=F9=E0 =E2 mail.bg =EF=F0=E5=E4=EB= =E0=E3=E0: - =D1=E8=EB=ED=E0 =E7=E0=F9=E8=F2=E0 =F1=F0=E5=F9=F3 =D1=CF=C0=CC/=F0=E5=EA= =EB=E0=EC=ED=E8 =EF=E8=F1=EC=E0 - 30MB =E1=E5=E7=EF=EB=E0=F2=ED=EE (SMS =EE=F2 2=EB=E2=3D3GB!) - 30MB =EC=E0=EA=F1. =F0=E0=E7=EC=E5=F0 =ED=E0 =EF=F0=E8=EA=E0=F7=E5=ED =F4= =E0=E9=EB - SMS =E7=E0 =ED=EE=E2=EE =EF=E8=F1=EC=EE (=E2=F1=E8=F7=EA=E8 =EE=EF=E5=F0= =E0=F2=EE=F0=E8) - WAP =E4=EE=F1=F2=FA=EF =EE=F2 GSM =E8 =E1=E5=E7 =EA=EE=EC=EF=FE=F2=FA=F0 - =C1=E5=E7=EF=EB=E0=F2=E5=ED POP3 =E4=EE=F1=F2=FA=EF - 24 =F7=E0=F1=EE=E2 =F2=E5=EB=E5=F4=EE=ED =E7=E0 =EF=EE=EC=EE=F9/=EF=EE=E4= =E4=F0=FA=E6=EA=E0 ______________________________________ =C1=C5=C7 =C8=C7=CB=C8=D8=CD=C8 =C2=DA=CF=D0=CE=D1=C8 =D0=C5=C3=C8=D1=D2=D0= =C8=D0=C0=C9=D2=C5 =D1=C2=CE=C9 =C1=C5=C7=CF=CB=C0=D2=C5=CD =C0=C4=D0=C5=D1 =CD=C0 http://www.mail.bg