Path: csiph.com!usenet.pasdenom.info!news.redatomik.org!newsfeed.xs4all.nl!newsfeed3a.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; 'static': 0.04; '(so': 0.07; 'received:198': 0.07; 'variables': 0.07; 'currently,': 0.09; 'seemed': 0.09; 'subject:GNU': 0.09; 'subject:modules': 0.09; 'subject:using': 0.09; 'worked,': 0.09; 'python': 0.11; 'project,': 0.12; 'archive': 0.14; 'background.': 0.14; '(and,': 0.16; "(i'm": 0.16; '(there': 0.16; 'cleanly': 0.16; 'install".': 0.16; 'invokes': 0.16; 'libtool': 0.16; 'libtool,': 0.16; 'obviously,': 0.16; 'porting': 0.16; 'sucked': 0.16; 'toolset': 0.16; 'url:gnu': 0.16; 'subject:python': 0.16; 'appropriate': 0.16; 'wrote:': 0.18; 'library': 0.18; 'basically': 0.19; 'thu,': 0.19; 'code,': 0.22; 'install': 0.23; 'certainly': 0.24; 'of.': 0.24; 'question': 0.24; "i've": 0.25; 'compiled': 0.26; 'references': 0.26; 'gets': 0.27; 'header:In-Reply-To:1': 0.27; 'point': 0.28; 'function': 0.29; 'needed.': 0.30; "i'm": 0.30; 'libraries': 0.31; 'linux.': 0.31; 'though.': 0.31; 'file': 0.32; 'themselves': 0.32; 'run': 0.32; 'text': 0.33; 'open': 0.33; 'url:python': 0.33; 'guess': 0.33; 'actual': 0.34; 'tool': 0.35; 'editor': 0.35; 'objects': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'building': 0.35; 'library.': 0.36; 'hi,': 0.36; 'url:org': 0.36; 'should': 0.36; 'message- id:@gmail.com': 0.38; 'jason': 0.38; 'to:addr:python-list': 0.38; 'files': 0.38; 'embedded': 0.39; 'sure': 0.39; 'to:addr:python.org': 0.39; 'university': 0.39; 'called': 0.40; 'hope': 0.61; 'mentioned': 0.61; 'first': 0.61; 'here:': 0.62; 'complete': 0.62; 'email addr:gmail.com': 0.63; 'name': 0.63; 'our': 0.64; 'believe': 0.68; ':).': 0.84; 'skip:/ 30': 0.84; 'pic': 0.91 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:subject:from:to:date:in-reply-to:references:content-type :mime-version:content-transfer-encoding; bh=qotXDZ0vP8/Y7SuH+c6kF73esZzQu6ToTwDNYFWgpYI=; b=AUYoaE/xFUpNIKGaow93yZ2/xc437apxdjMpkfb/tPbD1+ktdkHq8W5odiiQGAvF9f Bbu30ceellWsRJPX5ckEBvQ0nM7Q3GTwmB79tccxaV6b6Jcj/GzYGeuGFZuBWCnG1CFS kMhBrb2ehpy93JSsrlqrajrRXIfc94O/VtjWp7z/Ezfg4pbNmTZRcA+ue9ZKVdLXTSlk VxgY/6O1xpEx1dB9rw5al+jTU42YL/2bLijsw+IDhtiVFvVvEShB+4STFUkPEx2aW+zG US33Cb0APZ1ZodJ/Mamvka4KnO/Ye7Z6Dr34FW4Dv2SyVgOLn7Q77wBdg0Y0C6rO15Dm w7Sw== X-Received: by 10.229.78.137 with SMTP id l9mr20216460qck.11.1424968492207; Thu, 26 Feb 2015 08:34:52 -0800 (PST) Subject: Re: Building C++ modules for python using GNU autotools, automake, whatever From: Jason Swails To: python-list@python.org Date: Thu, 26 Feb 2015 11:35:03 -0500 In-Reply-To: <364c8f3d-808e-4513-9041-6d8cdfdc42b7@googlegroups.com> References: <364c8f3d-808e-4513-9041-6d8cdfdc42b7@googlegroups.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.8 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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: 47 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1424968500 news.xs4all.nl 2932 [2001:888:2000:d::a6]:33371 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:86512 On Thu, 2015-02-26 at 07:57 -0800, af300wsm@gmail.com wrote: > Hi, > > I'm a complete neophyte to the whole use of GNU > autotools/automake/auto... . (I'm not sure what it should be called > anymore.) Regardless, I'm porting a library project, for which I'm a > team member, to using this toolset for building in Linux. I'm to the > point now of writing the Makefile.am file for the actual library. > (There are several other static libraries compiled first that are > sucked into this shared object file.) > > I found some references here: > http://www.gnu.org/savannah-checkouts/gnu/automake/manual/html_node/Python.html, which seemed to be just what I was after. However, I've got a big question about a file named "module.la" instead of "module.so" which is what we compile it to now. I certainly hope module.la is not what it gets compiled to. Open it up with a text editor :). It's just basically a description of the library that libtool makes use of. In the projects that I build, the .la files are all associated with a .a archive or a .so (/.dylib for Macs). Obviously, static archives won't work for Python (and, in particular, I believe you need to compile all of the objects as position independent code, so you need to make sure the appropriate PIC flag is given to the compiler... for g++ that would be -fPIC). > > I guess I should have mentioned some background. Currently, we build > this tool through some homegrown makefiles. This has worked, but > distribution is difficult and our product must now run on an embedded > platform (so building it cleanly requires the use of autotools). > > Basically, I need this thing to install > to /usr/lib/python2.6/site-packages when the user invokes "make > install". I thought the variables and primaries discussed at the link > above were what I needed. However, what is a "*.la"? I'm reading up > on libtool now, but will it function the same way as a *.so? To libtool, yes... provided that you *also* have the .so with the same base name as the .la. I don't think compilers themselves make any use of .la files, though. HTH, Jason -- Jason M. Swails BioMaPS, Rutgers University Postdoctoral Researcher