使用介子构建 C 项目：处理 3rd 方本地库的正确方法

Question

I wanted to build a project that's making use of the Criterion testing library and I'm using meson to build it all. I'm able to build my own code, a static library which relies on just standard c libraries. The unit tests rely on #include <criterion/criterion.h> . If I try to download the binary archive and include it in the meson.build file, I'm not able to sucessfully build the project. I believe I'm not confuring meson correctly. I'm new to meson so I'm not sure what it is I'm getting wrong.

meson.build ,

project('is_substring', 'c')

static_library(
    'is_substring',
    'is_substring.h',
)

executable(
    'test_is_substring',
    'is_substring.test.c',
    include_directories: include_directories(
        'libs/criterion-v2.3.3',
    ),
    #dependencies: [
    #    dependency('criterion')
    #]
)

The project structure is,

  ▸ builddir/
  ▸ libs/criterion-v2.3.3/
    is_substring.h
    is_substring.test.c
    meson.build

and the Criterion binary archive tar.bz2 has extracted into ./libs ,

  ▾ libs/criterion-v2.3.3/
    ▾ include/criterion/
      ▸ internal/
        abort.h
        alloc.h
        assert.h
        criterion.h
        event.h
        hooks.h
        logging.h
        options.h
        output.h
        parameterized.h
        redirect.h
        stats.h
        theories.h
        types.h
    ▾ lib/
        libcriterion.so
        libcriterion.so.3
        libcriterion.so.3.1.0
    ▾ share/pkgconfig/
        criterion.pc

is_substring.test.c ,

#include "criterion/criterion.h"
#include <stdbool.h>
#include <stdio.h>

#include "is_substring.h"


Test(is_substring, is_substring)
{
    cr_assert(is_substring("aaa", "a") == true);
}

is_substring.h ,

#include "stdbool.h"

bool is_substring(const char *fullstr, const char *substr)
{
    return true;
}

The error when I try to build is,

francium@4ab5198f934f:/mnt/c/brute-force/builddir$ ninja
[1/2] Compiling C object 'test_is_substring@exe/is_substring.test.c.o'.
FAILED: test_is_substring@exe/is_substring.test.c.o
cc -Itest_is_substring@exe -I. -I.. -I../libs/criterion-v2.3.3 -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -MD -MQ 'test_is_substring@exe/is_substring.test.c.o' -MF 'test_is_substring@exe/is_substring.test.c.o.d' -o 'test_is_substring@exe/is_substring.test.c.o' -c ../is_substring.test.c
../is_substring.test.c:1:10: fatal error: criterion/criterion.h: No such file or directory
 #include <criterion/criterion.h>
          ^~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
ninja: build stopped: subcommand failed.
francium@4ab5198f934f:/mnt/c/brute-force/builddir$

As pointed out by @jonathan-leffler in the comments, this gcc command works, compiles and links correctly,

gcc -o is_substring.test is_substring.test.c -I libs/criterion-v2.3.3/include/ -Llibs/criterion-v2.3.3/lib -lcriterion

Answer 1

Managed to get it to compile, but since the Criterion library is a shared library and it's not installed globally, it doesn't work if you just try to run the compiled test executable.

But the fix to make it compile is adding in a,

executable(
    ...
    objects: [
        'libs/criterion-v2.3.3/lib/libcriterion.so',
    ]

Note that the include_directories path should also be 'libs/criterion-v2.3.3/include/' with the include/ at the end.

Full meson.build ,

project('is_substring', 'c')

static_library(
    'is_substring',
    'is_substring.h',
)

include_criterion = include_directories(
    'libs/criterion-v2.3.3/include/',
)

executable(
    'test_is_substring',
    'is_substring.test.c',
    include_directories: [
        include_criterion,
    ],
    objects: [
        'libs/criterion-v2.3.3/lib/libcriterion.so',
    ]
)

But running the output executable gives the following error at runtime,

./test_is_substring: error while loading shared libraries: libcriterion.so.3: cannot open shared object file: No such file or directory

As suggested by Jonathan, fixed for this are,

You may need to specify -R/opt/criterion-v2.3.3/lib or -R/usr/local/lib if you will install your Criterion library into one of those places. Or that may be misremembered from Solaris and not relevant on Linux. The system might look in /usr/local/lib anyway. There's also LD_LIBRARY_PATH; you could add /home/you/project/libs/criterion-v2.3.3/lib (or thereabouts) to your LD_LIBRARY_PATH environment variable and that should allow it to be picked up until it is formally installed

Thanks to @jonathan-leffler for his help and insight.