Dave Seaman wrote:
> On Wed, 7 May 2008 05:53:45 -0700 (PDT), D3|\||\|!$ wrote:
>
> > I supplied the libraryname along with the path as "dir_pathname/
> > libfilename1.a dir_pathname/libfilename2.a.." in the make options.
> > Gmake shows success but does not create the corresponding .o and
> > bi
On Thu, 8 May 2008 05:18:03 -0700 (PDT), D3|\||\|!$ wrote:
> Dave Seaman wrote:
>> On Wed, 7 May 2008 05:53:45 -0700 (PDT), D3|\||\|!$ wrote:
>> > I supplied the libraryname along with the path as "dir_pathname/
>> > libfilename1.a dir_pathname/libfilename2.a.." in the make options.
>> > Gmake s
> You provide dependencies in the Makefile. That's what it's for. The
> entries there mostly specify dependencies and rules for bringing a target
> up to date. For example, if your Makefile has
>
> foo.o: foo.c
> ${CC} ${CFLAGS} -c $< -o $@
>
> that means that foo.o depends on f
On Fri, 9 May 2008 05:25:50 -0700 (PDT), [EMAIL PROTECTED] wrote:
>> You provide dependencies in the Makefile. That's what it's for. The
>> entries there mostly specify dependencies and rules for bringing a target
>> up to date. For example, if your Makefile has
>>
>> foo.o: foo.c
>>
