使用Heroku Vulcan构建具有依赖性的库

时间：2013-04-18 19:56:03

标签： ruby-on-rails-3 heroku build-process

使命：构建ffmpegthumbnailer，可以使用Rails应用程序进行销售并部署到Heroku的Cedar堆栈。

到目前为止的流程：

  1. [success]使用Vulcan构建ffmpeg（使用this guide）并上传到S3
  2. [failed]用ffmpeg构建ffmpegthumbnailer作为依赖。

    3. 使用命令：

    $ vulcan build -v -s ffmpegthumbnailer-2.0.8 -d http://s3.amazonaws.com/remoting-io-cdn/heroku-building-lib/ffmpeg

    我得到以下内容（见底部错误）：

    Packaging local directory... done
Uploading source package... done
Building with: ./configure --prefix /app/vendor/ffmpegthumbnailer-2.0 && make install
downloading http://s3.amazonaws.com/remoting-io-cdn/heroku-building-lib/ffmpeg
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.
bin/vulcan-make:69:in `chdir': No such file or directory - /app/vendor/ffmpegthumbnailer-2.0 (Errno::ENOENT)
    from bin/vulcan-make:69:in `block (2 levels) in <main>'
    from bin/vulcan-make:18:in `chdir'
    from bin/vulcan-make:18:in `block in <main>'
    from /usr/local/lib/ruby/1.9.1/tmpdir.rb:83:in `mktmpdir'
    from bin/vulcan-make:17:in `<main>'
>> Downloading build artifacts to: /tmp/ffmpegthumbnailer-2.0.tgz
   (available at http://remoting-io-lib-builder.herokuapp.com/output/e25f3591-ce65-433d-a45a-15bd7ea36109)

    该错误消息是什么意思？我应该采取哪些不同的方式来正确编译它？

2 个答案:

答案 0 :(得分：0)

你有一些问题

  1. 您需要首先构建它的依赖项（libavutil，libavformat，libavcodec，libswscale）
  2. 你下载的东西实际上不是构建（构建从未发生过，它在配置时失败）它只是来自 所做进展的工件。
  3. 我在锤子（https://github.com/hone/hammer）方面取得了更大的成功，然后就可重复使用性而言是vulcan。

    4. 要解决这个问题，您需要为每个依赖项执行相同的过程，然后在构建脚本中将它们从s3中提取出来并确保它们位于您的路径或lib目录中。

    我还发现heroku run bash在攻击这些东西时是非常有价值的，因为它可以让你更多地修补你的环境。

答案 1 :(得分：0)

ffmpeg和ffmpegthumbnailer可以在steps explained here

之后使用Vulcan构建

此处提供了带有售卖ffmpeg和ffmpegthumbnailer的示例应用程序：https://github.com/JonasNielsen/ffmpegthumbnailer查看自述文件中的Heroku配置说明。

相关问题
最新问题