*.o's are for _PROGRAMS an _LIBRARIES
*.lo's are for _LTLIBRARIES
So it depends on what you are building. If you are building .a and .so, both
will be built. Of course all of this is IMO :)
On 22-Nov-00 at 05:11, Alexander Mai ([EMAIL PROTECTED]) wrote:
> Some simple auto* questions. I dare to ask them here - the result
> will help in creating some new Makefiles in our sources, so ...
>
> What's the canonical way of referencing the object files with the auto*
> tools, e.g. the objects for a library within Makefile.am?
>
> Some rules have to use this and I'm not sure whether I should
> use
> foo.o
> foo.lo
> foo.$(OBJEXT)
> ...
>
> (as a matter of fact .o and .lo have been used in our Makefiles!)
>
>
> Another related question: to transform a list of files e.g.
> SRCS= foo.c bar.c ...
> one could use some GNUMake extensions which would not work
> with another make tool. As I confess I use GNUMake on all systems
> I have access to, so I never cared about this issue. Do our Makefiles as
> generated by auto* really work with common unix make versions?
>
> --
> Alexander Mai
> [EMAIL PROTECTED]
>
>
