Sorry I forgot to mention the files in EXTRA_DIST are to be packed into release
package. All the cpp files mentioned here already exists and are to be compiled
and released.
If I put all cpp files in _SOURCES, the EXTRA_DIST files are not released. The
only way I've found is to put only one cpp file in _SOURCES, while others to
EXTRA_DIST and add .o to _LIBADD. My goal is to build all the .cpp and put all
.cpp, .txt, .rc into release package.
-------------------------------------
And can I ask another question? I want to build some source code files into
this library and need to distribute some other files, too. But EXTRA_DIST in
Makefile.am does not work as below,
lib_LTLIBRARIES = libezcommon.la
...
libezcommon_la_SOURCES = ezcommon.cpp tinystr.cpp ...
EXTRA_DIST = tinyxml.txt ezcommon.rc ...
If I write only one file in libezcommon_la_SOURCES, while adding others to
EXTRA_DIST and others' .o to libezcommon_la_LIBADD, it works. I don't know why.
I'm sorry, I don't understand the question. Are you trying to generate
sources, or optional build some sources? Perhaps a bit more context on the
problem...
Thanks for your patience.
----- -----
On 7/22/2009 9:15 PM, A117 wrote:
Thank you. I've decided to put the library in /usr/local/lib, while its header
files in /usr/local/include/ezproject.
It's strange though /usr/local/lib is in /etc/ld.so.conf (actually in another
file it includes), and I can build other programs acting much as mine, I have
difficulty with mine only. I run ldconfig manually and then it works. Now I'm
releasing my software.
ldconfig updates the library cache. the /etc/ld.so.conf file is the file
used by ldconfig to determine which directories to scan for libraries.
When you add a new library to one of the directories in /etc/ld.so.conf,
then you need to run ldconfig to ensure that the cache is aware of that
new library.
John
