[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Build a lib, then example programs

From: Ralf Wildenhues
Subject: Re: Build a lib, then example programs
Date: Thu, 9 Aug 2007 20:20:24 +0200
User-agent: Mutt/1.5.13 (2006-08-11)

Hello Benoit, all,

* Benoit SIGOURE wrote on Thu, Aug 09, 2007 at 10:12:02AM CEST:
> Hmm, that's not related to your problem but I *think* that you should do 
> something like this:
> nobase_include_HEADERS = DyConnect.h \
>       libdconn/DasyneInterface.hpp \
>       ...
>       libdconn/sync/SyncEngine.hpp \
>       libdconn/sync/SyncServerFSM.hpp
> libdconn_a_SOURCES = $(nobase_include_HEADERS) \
>       DyConnect.cpp \
>       libdconn/DasyneInterface.cpp \
>       ...
>       libdconn/sync/SyncClient.cpp \
>       libdconn/sync/SyncServerFSM.cpp
> In order to get proper dependency tracking from automake, can anyone 
> confirm this?  (as I'm not sure)

No, technically it is not necessary to add $(nobase_include_HEADERS) to
libdconn_a_SOURCES.  Just all files should be listed somewhere, so they
are distributed, and all compilable files should be listed in *_SOURCES
so compile rules are generated.

> Moreover I don't know whether this is intended but the _HEADERS primary is 
> used to specify headers that must be installed.  If you did not mean this, 
> you do better just list the headers in the libdconn_a_SOURCES.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]