Am Samstag 05 Dezember 2009 13:33:06 schrieb Ralf Wildenhues:
Hello Andreas,
besides answers already given:
* Andreas Otto wrote on Fri, Dec 04, 2009 at 09:41:16AM CET:
as you see both *lo and *.o are created. the *.o are useless and just
extend the compiling time
Q: what can I do to
Am Samstag 05 Dezember 2009 13:33:06 schrieb Ralf Wildenhues:
Hello Andreas,
besides answers already given:
* Andreas Otto wrote on Fri, Dec 04, 2009 at 09:41:16AM CET:
as you see both *lo and *.o are created. the *.o are useless and just
extend the compiling time
Q: what can I do to
Hello Andreas,
besides answers already given:
* Andreas Otto wrote on Fri, Dec 04, 2009 at 09:41:16AM CET:
as you see both *lo and *.o are created. the *.o are useless and just
extend the compiling time
Q: what can I do to avoid build static libraries ...
foo_LIBTOOLFLAGS =
Hi,
I have a project using together the both statements from above to configure.
This project hase many different parts includig many shared libraries
and executables.
Now the problem.
1. I have libraries which are only useful as shared libraries. this
libraries are language
On Fri, 4 Dec 2009, Andreas Otto wrote:
$(TCL_CFLAGS) $(AM_CFLAGS) -DMQ_IGNORE_EXTERN
tclmsgque_la_LIBADD = ../libmsgque/*.lo
The above line is wrong. You should refer to tclmsgque.la rather than
'*.lo'. Wildcard specifications do not belong in an Automake
makefile.
as you see both *lo
* Andreas Otto (aotto1...@t-online.de) [20091204 09:45]:
1. I have libraries which are only useful as shared libraries. this
libraries are language extension used to dl-open by an programming
language.
If they are to be dl-opened they aren't shared libraries but rather a form
of
