Autotools：包括预构建的第三方库

发布于 2024-12-21 11:15:36 字数 826 浏览 5 评论 0原文

我目前正在努力将一组 C++ 二进制文件升级为基于 Autotools 的更现代的文件，每个文件都使用自己的 Makefile 集。但是我不知道如何将第三方库（例如 Oracle Instant Client）包含到构建/打包过程中。

这真的是我错过的简单事情吗？

编辑以添加更多详细信息

我当前的构建环境如下所示：

/src
    /lib
        /libfoo
            ... source and header files
            Makefile
        /oci #Oracle Instant Client
            ... header and shared libraries
            Makefile
    /bin
        /bar
            ... source and header files
            Makefile
    Makefile
/build
    /bin
    /lib

build.sh

今天，顶层 build.sh 执行以下步骤：

运行每个库的 Makefile 并将输出复制到 /build/lib
运行每个二进制文件的 Makefile并将输出复制到 /build/bin

每个 Makefile 都有一组指向各个同级目录的硬编码路径。不用说，这已经成为维护的噩梦。我已经开始测试自动工具，但我遇到的问题是找出相当于将 /src/lib/oci/*.so 复制到 /build/lib 的方法，以进行编译时链接并捆绑到发行版中。

原文

I'm currently working to upgrade a set of c++ binaries that each use their own set of Makefiles to something more modern based off of Autotools. However I can't figure out how to include a third party library (eg. the Oracle Instant Client) into the build/packaging process.

Is this something really simple that I've missed?

Edit to add more detail

My current build environment looks like the following:

/src
    /lib
        /libfoo
            ... source and header files
            Makefile
        /oci #Oracle Instant Client
            ... header and shared libraries
            Makefile
    /bin
        /bar
            ... source and header files
            Makefile
    Makefile
/build
    /bin
    /lib

build.sh

Today the top level build.sh does the following steps:

Runs each lib's Makefile and copies the output to /build/lib
Runs each binary's Makefile and copied the output to /build/bin

Each Makefile has a set of hardcoded paths to the various sibling directories. Needless to say this has become a nightmare to maintain. I have started testing out autotools but where I am stuck is figuring out the equivalent to copying /src/lib/oci/*.so to /build/lib for compile time linking and bundling into a distribution.

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

南七夏 2024-12-28 11:15:36

我想出了如何实现这一点。

首先，我切换到非递归 make。

接下来，我按照此页面对configure.am进行了以下更改 http://www.openismus .com/documents/linux/using_libraries/using_libraries

AC_ARG_WITH([oci-include-path],
    [AS_HELP_STRING([--with-oci-include-path],
        [location of the oci headers, defaults to lib/oci])],
    [OCI_CFLAGS="-$withval"],
    [OCI_CFLAGS="-Ilib/oci"])
AC_SUBST([OCI_CFLAGS])
AC_ARG_WITH([oci-lib-path],
    [AS_HELP_STRING([--with-oci-lib-path],
        [location of the oci libraries, defaults to lib/oci])],
    [OCI_LIBS="-L$withval -lclntsh -lnnz11"],
    [OCI_LIBS='-L./lib/oci -lclntsh -lnnz11'])
AC_SUBST([OCI_LIBS])

然后在 Makefile.am 中使用以下行（假设名为 foo 的二进制文件）

foo_CPPFLAGS = $(OCI_CFLAGS)
foo_LDADD = libnavycommon.la $(OCI_LIBS)

ocidir = $(libdir)
oci_DATA = lib/oci/libclntsh.so.11.1 \
    lib/oci/libnnz11.so \
    lib/oci/libocci.so.11.1 \
    lib/oci/libociicus.so \
    lib/oci/libocijdbc11.so

I figured out how to make this happen.

First I switched to a non recursive make.

Next I made the following changes to configure.am as per this page http://www.openismus.com/documents/linux/using_libraries/using_libraries

AC_ARG_WITH([oci-include-path],
    [AS_HELP_STRING([--with-oci-include-path],
        [location of the oci headers, defaults to lib/oci])],
    [OCI_CFLAGS="-$withval"],
    [OCI_CFLAGS="-Ilib/oci"])
AC_SUBST([OCI_CFLAGS])
AC_ARG_WITH([oci-lib-path],
    [AS_HELP_STRING([--with-oci-lib-path],
        [location of the oci libraries, defaults to lib/oci])],
    [OCI_LIBS="-L$withval -lclntsh -lnnz11"],
    [OCI_LIBS='-L./lib/oci -lclntsh -lnnz11'])
AC_SUBST([OCI_LIBS])

In the Makefile.am you then use the following lines (assuming a binary named foo)

foo_CPPFLAGS = $(OCI_CFLAGS)
foo_LDADD = libnavycommon.la $(OCI_LIBS)

ocidir = $(libdir)
oci_DATA = lib/oci/libclntsh.so.11.1 \
    lib/oci/libnnz11.so \
    lib/oci/libocci.so.11.1 \
    lib/oci/libociicus.so \
    lib/oci/libocijdbc11.so

回复收藏 0 原文