Question

在我详细说明问题之前，我应该让你知道我已经成功地在heroku的bash（heroku run bash）上安装了ffmpegthumbnailer。

我尝试使用我编写的自定义Heroku buildpack来构建ffmpegthumbnailer，但是当我运行时./configure＆amp;＆amp;在bin / compile buildpack文件中make install，ffmpegthumbnailer告诉我它找不到ffmpeg libs（util，format，codec，scale）并建议我设置PKG_CONFIG_PATH。所以我设置了PKG_CONFIG_PATH，它似乎仍然无法找到库。

我已经尝试过以哪种方式设置PKG_CONFIG_PATH。 echo export，export，直接通过PKG_CONFIG_PATH = / app设置它...我总是使用.configure命令将其设置为内联。我甚至将PKG_CONFIG_PATH设置为heroku config var，并尝试通过作为第三个参数传递给buildpack的ENV_DIR变量来访问它，但我很快意识到我只是将变量PKG_CONFIG_PATH设置为文件名为PKG_CONFIG_PATH，即我正在设置PKG_CONFIG_PATH = / app / vendor ...，我已经完成了!!这些都没有奏效。另外，正如您在编译文件和日志中看到的那样，echo $ PKG_CONFIG_PATH会打印正确的路径。

我可以做多少调试？发生了什么事？

下面是我的bin / compile buildpack文件，以及我将应用程序部署到heroku后的日志。

#!/bin/sh

indent() {
  sed -u 's/^/       /'
}

echo "-----> Install ffmpeg-thumbnailer"
BUILD_DIR=$1
VENDOR_DIR="vendor"
DOWNLOAD_URL="https://ffmpegthumbnailer.googlecode.com/files/ffmpegthumbnailer-2.0.8.tar.gz"

echo "DOWNLOAD_URL = " $DOWNLOAD_URL | indent

cd $BUILD_DIR
mkdir -p $VENDOR_DIR
cd $VENDOR_DIR
curl -L --silent $DOWNLOAD_URL | tar xz
cd ffmpegthumbnailer-2.0.8/
export PKG_CONFIG_PATH="$PKG_CONFIG_PATH:/app/vendor/ffmpeg/lib/pkgconfig/"
echo $PKG_CONFIG_PATH
./configure --prefix /app/vendor/ffmpegthumbnailer && make install

echo "exporting PATH and LIBRARY_PATH" | indent
PROFILE_PATH="$BUILD_DIR/.profile.d/ffmpeg-thumbnailer.sh"
mkdir -p $(dirname $PROFILE_PATH)
echo 'export PATH="$PATH:vendor/ffmpeg-thumbnailer/bin"' >> $PROFILE_PATH
echo 'export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:vendor/ffmpeg-thumbnailer/lib"' >> $PROFILE_PATH

我的heroku部署日志......

Fetching repository, done.
Counting objects: 5, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 311 bytes, done.
Total 3 (delta 2), reused 0 (delta 0)

-----> Fetching custom git buildpack... done
-----> Multipack app detected
=====> Downloading Buildpack: https://github.com/shunjikonishi/heroku-buildpack-ffmpeg
=====> Detected Framework: ffmpeg
-----> Install ffmpeg
       DOWNLOAD_URL =  http://flect.github.io/heroku-binaries/libs/ffmpeg.tar.gz
       exporting PATH and LIBRARY_PATH
=====> Downloading Buildpack: https://github.com/johnklawlor/heroku-buildpack-ffmpeg-thumbnailer
=====> Detected Framework: ffmpeg
-----> Install ffmpeg-thumbnailer
HERE COMES PKG_CONFIG!
/app/vendor/ffmpeg/lib/pkgconfig
       DOWNLOAD_URL =  https://ffmpegthumbnailer.googlecode.com/files/ffmpegthumbnailer-2.0.8.tar.gz
/app/vendor/ffmpeg/lib/pkgconfig
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether make supports nested variables... yes
checking for ANSI C header files... (cached) yes
checking for inttypes.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking whether /usr/bin/ld -m elf_x86_64 accepts --as-needed... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for FFMPEG... no
configure: error: Package requirements (libavutil libavformat libavcodec >= 52.26.0 libswscale) were not met:

No package 'libavutil' found
No package 'libavformat' found
No package 'libavcodec' found
No package 'libswscale' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables FFMPEG_CFLAGS
and FFMPEG_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
       exporting PATH and LIBRARY_PATH
=====> Downloading Buildpack: https://github.com/heroku/heroku-buildpack-ruby

Answer 1

问题是您将PKG_CONFIG_PATH设置为不存在的目录。请注意，https://github.com/shunjikonishi/heroku-buildpack-ffmpeg在构建dyno上创建目录$BUILD_DIR/vendor/ffmpeg，而不是/app/vendor/ffmpeg，而$BUILD_DIR类似于/tmp/build_<hash>。

如果您将变量赋值更改为

export PKG_CONFIG_PATH="$BUILD_DIR/vendor/ffmpeg/lib/pkgconfig"

然后configure将找到库。

然而，还有另外一点。为此，有必要知道构建之后$BUILD_DIR中的内容是您的应用程序slug，并且将在/app生产dynos中。因此，ffmpeg的路径在构建期间为$BUILD_DIR/vendor/ffmpeg，但在生产期间为/app/vendor/ffmpeg。

目前，

./configure --prefix /app/vendor/ffmpegthumbnailer && make install

您正在将ffmpegthumbnailer安装到应用程序slug之外的/app/vendor/ffmpegthumbnailer。但它确实是您在制作期间想要的位置，但这意味着它必须在构建结束时位于$BUILD_DIR/vendor/ffmpegthumbnailer。

实现此目的的一种方法是将您的东西配置并安装到/app，然后将完成的安装目录复制到$BUILD_DIR。因此，你可以做到

./configure --prefix /app/vendor/ffmpegthumbnailer && make install
mkdir -p "$BUILD_DIR"/vendor/ffmpegthumbnailer
cp -R /app/vendor/ffmpegthumbnailer/ "$BUILD_DIR"/vendor/ffmpegthumbnailer

通过这种方式，用于./configure --prefix的路径是在运行时有效的路径（否则在运行时出现问题），和我们将安装包含在我们的应用程序slug。

然后在运行时设置PATH和LD_LIBRARY_PATH：

echo 'export PATH="$PATH:/app/vendor/ffmpegthumbnailer/bin"' >>"$PROFILE_PATH"
echo 'export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:/app/vendor/ffmpegthumbnailer/lib"' >>"$PROFILE_PATH"

因为这些是在运行时有效的路径。

事实上所有归结为等式$BUILD_DIR （构建）== /app （制作）

如何在Heroku buildpack中设置CONFIG_PATH

1 个答案: