Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I've never been sold on the idea of a separate directory for headers. That aside, the <code>src</code> <code>Makefile.am</code> can simply use the <code>AM_CPPFLAGS</code> variable:</p> <pre><code>AM_CPPFLAGS = -I$(top_srcdir)/inc # and other preprocessor flags. lib_LTLIBRARIES = libfoo.la libfoo_la_SOURCES = file_1.c file_2.c ... ../inc/file_1.h ../inc/file_2.h ... </code></pre> <p>Ideally, you would also include the headers in <code>libfoo_la_SOURCES</code> as above, since any changes in a header requires the recompilation of source files. By placing the headers in the <code>src</code> directory, we can simply list <code>file_1.h</code>, <code>file_2.h</code>, etc., in the <code>SOURCES</code> primary.</p> <p>Since <code>-I$(srcdir)</code> is already provided <a href="http://www.gnu.org/software/automake/manual/automake.html#Program-Variables" rel="nofollow">automatically</a>, you don't need to add this option to <code>AM_CPPFLAGS</code>, provided the headers are included in the form <code>&lt;file_1.h&gt;</code> or <code>"file_1.h"</code>.</p> <p>Furthermore, the headers will be installed by adding the following to <code>src/Makfile.am</code>:</p> <pre><code>libfoo_includedir = $(includedir) libfoo_include_HEADERS = file_1.h file_2.h ... </code></pre> <p>A minimal top-level <code>Makefile.am</code> might look like:</p> <pre><code>ACLOCAL_AMFLAGS = -I m4 --install # AC_CONFIG_MACRO_DIR([m4]) in configure.ac SUBDIRS = src tests # depth-first ordering of build. </code></pre> <p>This leaves us with <code>test/Makefile.am</code> :</p> <pre><code>AM_CPPFLAGS = -I$(top_srcdir)/src # or $(srcdir)/../src check_PROGRAMS = foo_test foo_test_SOURCES = foo_test.c foo_test_LDADD = $(top_builddir)/src/libfoo.la </code></pre> <p>Note the use of <code>top_builddir</code> - we want to be able to build 'out-of-tree'.</p> <p>Finally, you might want to consider building libraries with headers of the form: <code>&lt;foo/file_1.h&gt;</code>. I think this is a better approach, as the leading directory provides a sort-of 'name space' for the library headers. e.g.,</p> <pre><code>libfoo_includedir = $(includedir)/foo # in foo/Makefile.am AM_CPPFLAGS = -I$(top_srcdir) # in test/Makefile.am </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POHow to write makefile.am's in subdirectories?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBrett Hale
    1. USBrett Hale
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to write makefile.am's in subdirectories?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COI tried it in the same way but giving this error "No rule to make target `all'. Stop." at the directory i am trying to create a static library.
      singulars
      1. PO
      1. USSiva Krishna Aleti
    2. COsuppose i want to add a library to another library(suppose libfoo library requires another source files in other directory). How should i do it?. Is this correct way of doing? libfoo_la_LIBADD = $(top_srcdir)/src/another.la
      singulars
      1. PO
      1. USSiva Krishna Aleti
    3. COfoo_test_LDADD = $(top_builddir)/src/foo.la i this way we add static libraries to our program. But how they are automatically created or we have create them manually, is there any way of doing it automatically when required
      singulars
      1. PO
      1. USSiva Krishna Aleti
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload