X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=MQWsj9uJKiWZ6bELpb8xPH1akVXOKYhMK/BZ777J6WM=; b=d6gKLKHaKW22H7y3PHYRlPkeLgh6Hzg/c84zNUmDZXl2uvTzQKm4RxyRRmK/a3FgD/ /DKCVE49jvWqJxtiwSnZqW7lmZAnf6UQ/87x9uNBK2h36YGalzkvnnvpgO9frp2+qsR8 i1sg8LWgLUKKND6yTI7I3zutmbOgZmXP7B1YhR0XwsX9/q23OPA1x9wZc+IGJ7mHqtdA j4OI+UXSXMkLr0tF71ByXF6MXyqav3QFBQybQHnSHD6I6Ff+RIx+kArYj/fO4P1xdLNS GUQzK5/X9LSFEK8zHUuKIsS1YJDT3Vkme9k9sZQ2Teqx63PDO4EOcpX8Sb9BXgjZRLbx MAWw== MIME-Version: 1.0 X-Received: by 10.28.19.78 with SMTP id 75mr15439187wmt.101.1447607270290; Sun, 15 Nov 2015 09:07:50 -0800 (PST) In-Reply-To: <20151114234238.19176.qmail@stuge.se> References: <20151114234238 DOT 19176 DOT qmail AT stuge DOT se> Date: Sun, 15 Nov 2015 08:07:50 -0900 Message-ID: Subject: Re: [geda-user] build system handles files starting with pcb- in some special way? From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=001a1146ee9e1ebe09052497551f Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk --001a1146ee9e1ebe09052497551f Content-Type: text/plain; charset=UTF-8 On Sat, Nov 14, 2015 at 2:42 PM, Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com] wrote: > Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > > I tried to make a file pcb-foo.c and the build system seemed to always > > think its o-file was up to date, and seemed to never compile the file > > itself (I think the .o was just a dependency build or something). > > After autoreconf etc. of course. Renaming it seemed to fix the problem. > > How did you adjust Makefile.am to include this file in a _SOURCES > variable for automake? > > > Does the build system treat files starting with pcb- in some special way? > > automake+libtool need to know about source files. I would expect your > source file would be compiled to pcb-pcb-foo.o if correctly added to > a _SOURCES variable. I added them in with the other source names in in src/Makefile.am. The odd thing is there's at least one other source file with the same form (pcb-printf.c) and that one works fine. I guess it might be the fact that I also had a source file with the same name sans pcb- prefix. --001a1146ee9e1ebe09052497551f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Sat, Nov 14, 2015 at 2:42 PM, Peter Stuge (peter AT stuge DOT se) [via = geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote= :
Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> I tried to make a file pcb-foo.c and the build system seemed to always=
> think its o-file was up to date, and seemed to never compile the file<= br> > itself (I think the .o was just a dependency build or something).
> After autoreconf etc. of course.=C2=A0 Renaming it seemed to fix the p= roblem.

How did you adjust Makefile.am to include this file in a _SOURCES variable for automake?

> Does the build system treat files starting with pcb- in some special w= ay?

automake+libtool need to know about source files. I would expect you= r
source file would be compiled to pcb-pcb-foo.o if correctly added to
a _SOURCES variable.

I added the= m in with the other source names in in src/Makefile.am.=C2=A0 The odd thing= is there's at
least one other source file with th= e same form (pcb-printf.c) and that one works fine.=C2=A0 I guess it
<= div style=3D"">might be the fact that I also had a source file with the sam= e name sans pcb- prefix. =C2=A0
=C2=A0
--001a1146ee9e1ebe09052497551f--