Re: gmake error: No rule to make target lib_file.a

[Dave Seaman]

On Fri, 9 May 2008 05:25:50 -0700 (PDT), main13@gmail.com 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
>>         ${CC} ${CFLAGS} -c $< -o $@
>>
>> that means that foo.o depends on foo.c, and if foo.c is newer than foo.o
>> (or if foo.o does not exist), then the rule that is provided on the next
>> line is used to bring foo.o up to date.

>> What messages do you get when you run the "make"?  Most likely, the first
>> error message is the important one, not the last one.
>>
>> Was the Makefile intended to work in a Windows environment, or does it
>> assume a Unix/Linux platform?  In the latter case, there may be no easy
>> solution.

> I ported the project from VC++ to KDevelop. So there was nothing
> common between the two projects except the source. So the makefiles
> were generated by KDevelop hence they assume Linux since I've not
> played with any of the default options.

Sorry, I can't help you with KDevelop.


-- 
Dave Seaman
Third Circuit ignores precedent in Mumia Abu-Jamal ruling.
<http://www.indybay.org/newsitems/2008/03/29/18489281.php>