Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.000 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'win32': 0.03; '(at': 0.03; 'interpreter': 0.04; 'subject:Python': 0.05; 'that?': 0.05; 'perl,': 0.07; 'python': 0.09; 'filenames,': 0.09; 'libraries.': 0.09; 'patch.': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'sqlite': 0.09; 'terry': 0.09; "wouldn't": 0.11; 'static': 0.13; 'slightly': 0.15; 'binaries': 0.16; 'build.': 0.16; 'filenames.': 0.16; 'openssl': 0.16; 'rationale': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'reedy': 0.16; 'subject: \n ': 0.16; 'workspace': 0.16; 'wrote:': 0.17; 'version.': 0.17; 'jan': 0.18; 'versions': 0.20; 'sort': 0.21; 'constant': 0.22; 'libraries': 0.22; 'work,': 0.22; 'dependent': 0.23; 'somebody': 0.23; 'least': 0.25; 'header:In- Reply-To:1': 0.25; 'header:User-Agent:1': 0.26; 'am,': 0.27; 'older': 0.27; 'newer': 0.27; 'header:X-Complaints-To:1': 0.28; 'perl': 0.29; 'source': 0.29; 'code': 0.31; 'could': 0.32; 'adjust': 0.33; 'exhibit': 0.33; 'instead,': 0.33; 'to:addr :python-list': 0.33; 'that,': 0.34; 'version': 0.34; 'changed': 0.34; 'project': 0.34; 'updated': 0.34; 'open': 0.35; 'received:org': 0.36; '2010.': 0.36; 'explain': 0.36; 'wanted': 0.36; 'visual': 0.36; 'subject:with': 0.36; 'why': 0.37; 'subject:: ': 0.38; 'behind': 0.38; 'files': 0.38; 'instead': 0.39; 'to:addr:python.org': 0.39; 'build': 0.39; 'header:Received:5': 0.40; 'link': 0.60; 'email addr:gmail.com': 0.63; 'gotten': 0.75; 'received:fios.verizon.net': 0.84; 'hassle': 0.91 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Terry Reedy Subject: Re: Linking with static libraries for Python standard components such as OpenSSL Date: Fri, 08 Mar 2013 05:03:23 -0500 References: <84193dbe-3256-4815-b828-7ce7bd90d388@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: pool-173-75-251-66.phlapa.fios.verizon.net User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 In-Reply-To: <84193dbe-3256-4815-b828-7ce7bd90d388@googlegroups.com> X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 30 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1362737024 news.xs4all.nl 6859 [2001:888:2000:d::a6]:59216 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:40855 On 3/8/2013 2:23 AM, gerson.kurz@gmail.com wrote: > I am rebuilding Python 2.7.4 using Visual Studio 2010. As part of > that, I wanted to build with a current OpenSSL version (1.0.1e) and > an updated SQLite version. > > What I noted: the projects in the main workspace (at least in > PCBuild) directly include the source code of dependent libraries. Can > somebody please explain the rationale behind that? > > Wouldn't it be better to instead link with static libraries of these > projects? > > Exhibit A: _ssl.pyd requires a Perl interpreter to build. (Perl! > Anathema!) Instead, _ssl.pyd could very well link with the Win32 > binaries for OpenSSL? If you can make that work, open an issue and submit a patch. I have not gotten perl, so I am not building ssl. > Exhibit B: _bsddb.pyd includes a ton of files from Berkley DB, with > their filenames. Alas, newer versions of Berkley DB have slightly > changed filenames, so the project needs to be changed to adjust for a > newer version of Berkley DB. The it would not work with older versions? This sort of constant hassle is why bsddb is not part of 3.x. -- Terry Jan Reedy