autotools

Check framework example giving me error when running './configure'

こ雲淡風輕ζ 提交于 2019-12-06 05:01:26
问题 I'm building the check framework example 'check_money', but it's not building on my machine. The error is: configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.." I've tried installing it using: libtoolize --force aclocal autoheader automake --force-missing --add-missing autoconf ./configure It's still giving me the same error. So, I copied the same directory to another directory and ran: autoreconf --install ./configure And it's still giving me the same error.

g++-4.6.real: error: unrecognized option '-R'

为君一笑 提交于 2019-12-06 04:57:02
I am trying to compile phpcompiler from source using this configure command. ./configure --prefix=/opt/phc-0.3.0.1/ --with-php=/opt/php-5.3.17/ The configure error was, checking for exit in -lboost_regex-mt... no checking for exit in -lboost_regex-mt... (cached) no checking for exit in -lboost_regex... no checking for exit in -lboost_regex... (cached) no checking for exit in -lboost_regex... (cached) no configure: error: Could not link against boost_regex Thats completely wrong as I have both boost and boost_regex packages installed. Both libs and header files. Then I dug this in the config

Automake ignore missing NEWS/AUTHORS/COPYING/etc. standard files

给你一囗甜甜゛ 提交于 2019-12-06 01:44:34
问题 Automake requires that the following "standard" files exist in the source directory of my project: INSTALL NEWS README COPYING AUTHORS ChangeLog Obviously, none of these files are necessary for a program to build, but Automake refuses to run without them. I know about the --add-missing flag that will cause boilerplate files to be generated, but I would rather not have the files at all. Is there a way to force Automake to run and ignore the missing files without generating them? 回答1: Use the

Libtool slowness, double building?

拈花ヽ惹草 提交于 2019-12-06 00:57:04
In my project, modules are organized in subdirs for tidiness. My project dir hierarchy: $ ls -R .: configure.in Makefile.am Makefile.cvs src ./src: log Makefile.am main.cpp ./src/log: log.cpp Makefile.am configure.in: AC_INIT(configure.in) AM_CONFIG_HEADER(config.h) AM_INIT_AUTOMAKE(myapp, 0.1) AC_LANG_CPLUSPLUS AC_PROG_CXX AM_PROG_LIBTOOL AC_OUTPUT(Makefile src/Makefile src/log/Makefile) Makefile.am: AUTOMAKE_OPTIONS = foreign SUBDIRS = src Makefile.cvs: default: aclocal libtoolize --force --copy autoheader automake --add-missing --copy autoconf src/Makefile.am bin_PROGRAMS = myapp myapp

Autoconf subdirectories with subpackages depending on each other?

北慕城南 提交于 2019-12-05 22:38:56
问题 I've got a large project on my hand (master) that is split into several components (liba, b, c, d) to ease building and maintenance. When building the whole package, all of the subcomponents must be built in sequence, and some of these packages depend upon each other. In more explicit terms, liba is a prerequisite for b, c and d, and the presence of liba is checked by the configure script. This check is definitely necessary to give user-friendly error messages when building the b distribution

Calling SED for a source in Makefile.am

非 Y 不嫁゛ 提交于 2019-12-05 18:40:34
I've got c++ code that needs a sed done to it prior to compilation. How do I place this into Makefile.am ? I tried the typical makefile setup and the target appears to not exist: gentest.cc: $(SED) -i "s|FIND|REPLACE|" gentest.cc If you are interested as to why I want to do this, it's because I wrote my program ( slider3.py ) in python and my partner wrote his in c++ ( gentest.cc ) and his needs to call mine. I'm accomplishing this by editing the argv and then using execv() . ... { char **argv2 = new char*[argc]; memset(argv2,0,sizeof(argv2)); argv2[0] = "__PREFIX__/bin/slider3.py"; memcpy

make: disable parallel building in subdirectory for single target only

隐身守侯 提交于 2019-12-05 18:37:35
问题 I have a rather huge autotools-powered project that lives in a directory tree consisting of a lot of directories with subdirectories. It's got a target check (in each subdirectory as well as the main directory) that executes a whole lot of automated tests. The check target is built recursively. Building as well as testing in parallel (via the -j option to make) works for most of the directories. There is however one directory that contains test that don't work when executed in parallel

What is the best way to set compilation flags for individual source files using GCC and autotools?

强颜欢笑 提交于 2019-12-05 17:57:22
I need to disable optimization flag for a individual file using autotools. What is the best way to do it? Do you mean an individual source file or an individual executable? To disable optimization for an executable is simple: bin_PROGRAMS = myprog myprog_SOURCES = foo.c bar.c myprog_CFLAGS = -O0 If you mean that you want to disable the optimization for a single source file temporarily , say for debugging purposes, you can just remake that file at the prompt: (example from the automake manual) rm bar.o make CFLAGS=-O0 bar.o make To do it for an individual source file permanently is not so

Qt and QMake build dir

限于喜欢 提交于 2019-12-05 17:38:35
I would like to build qt and qt application out of the source tree. Do you know how to set from the command line the .obj directory both with configure and qmake? If I understand question correctly you should set OBJECTS_DIR variable in *.pro file for any directory you want. If you don't want to change *.pro file try qmake "OBJECTS_DIR=some_dir" *.pro 来源: https://stackoverflow.com/questions/1741877/qt-and-qmake-build-dir

Building autotooled software to LLVM bitcode

狂风中的少年 提交于 2019-12-05 17:16:01
问题 I would like to compile software using the autotools build system to LLVM bitcode; that is, I would like the executables obtained at the end to be LLVM bitcode, not actual machine code. (The goal is to be able to run LLVM bitcode analysis tools on the whole program.) I've tried specifying CC="clang -emit-llvm -use-gold-plugins" and variants to the configure script, to no avail. There is always something going wrong (e.g. the package builds .a static libraries, which are refused by the linker)