...
Rule | Description | Example |
---|---|---|
modlibs_<modname> | Names of "internal" static or shared object libraries in the repository /build/../modlib sub-tree; these libraries are to be linked into the target module at build time (as opposed to dynamically linked at run time). See Figure 6. |
...
modlibs_transport := rce/enet |
...
modslib_<modname> | Names of "external" system or third-party static libraries to be linked into the target module at build time (as opposed to dynamically linked at run time). |
...
modslib_packet := \ |
...
modlibnames | Name of an "internal" library to build; the resulting library is suitable for linking into a module at build time. |
...
modlibnames := foo |
...
libsrcs_<modlibname> | Source files to use in building an "internal" library. | libsrcs_foo := alpha.cc beta.cc | Header file include directories for headers inside the RCE release tree. | libincs_foo := rce/fci |
libsinc_<modlibname> | Header file include directories for headers outside the RCE release tree. |
...
libsinc_foo := /usr/lib/net |
...
The following example constituents.mk file illustrates the use of these optional make rules in building an rce module, george.1.0.example, which is composed of its own compiled sources as well as two internal libraries in the fci and enet projects (libcontainer and libutil) and an external library (libmodcommon). Make instructions for the libcontainer library are included in the george makefile, and the two are built as part of the same sequence.
...