On Fri, May 22, 2009 at 8:04 AM, James Coleman wrote:
...
> 4.
> I notice that adding a static library doesn't get picked up by a default
> rule. I'm not going to dig further into this. My syntax for libs might be
> wrong, makefile.lib:
> executable: othercfile.o staticlibrary.a
>
> staticlibrary.
On Mon, May 25, 2009 at 5:56 AM, Federico Poloni wrote:
...
> Thanks for the advice. I was not reporting this behavior as erroneous, but
> warning that it differs significantly from the documentation ("Each kind of
> file automatically made into `.o' object files will be
> automatically linked").
James Coleman wrote:
The intent of the default rule is to make it easy to handle object files
or libs I think. So it makes sense that for you the file is assumed to
be an object file and is passed to the link line.
For anything other than very simple cases you will make your own rules.
Thank
Hello,
The intent of the default rule is to make it easy to handle object files
or libs I think. So it makes sense that for you the file is assumed to
be an object file and is passed to the link line.
For anything other than very simple cases you will make your own rules.
1.
Do you actually
Hello everyone,
According to GNU Make documentation,
> Linking a single object file
n is made automatically from n.o by running the linker (usually
called ld) via the C compiler. The precise command used is `$(CC)
$(LDFLAGS) n.o $(LOADLIBES) $(LDLIBS)'.
This rule does the right thing for a simp
