autoconf

问题 the error message is as follows: ./libtool: line 1129: X-I.: command not found ./libtool: line 1129: X-DLT_CONFIG_H=<config.h>: command not found ./libtool: line 1129: X-DLTDL: command not found ./libtool: line 1129: X-I.: command not found ./libtool: line 1129: X-I.: command not found ./libtool: line 1129: X-Ilibltdl: command not found ./libtool: line 1129: X-I./libltdl: No such file or directory ./libtool: line 1129: X-I./libltdl: No such file or directory ./libtool: line 1129: X-g: command

问题 autogen.sh failed, the output shows that i need an autoconf of higher version. but in fact i have a 2.6x autoconf.... why it still failed? [mirror@home 4]$ ./autogen.sh + autoreconf -i -f -v autoreconf: Entering directory `.' autoreconf: configure.in: not using Gettext autoreconf: running: aclocal --force -I m4 configure.in:4: error: Autoconf version 2.60 or higher is required configure.in:4: the top level autom4te: /usr/bin/m4 failed with exit status: 63 aclocal: autom4te failed with exit

问题 I have a quite complex (C++) project using autoconf / automake, which includes some "generated" files (foo.yy -> foo.cc). Actual builds are done using a "control script" (Gentoo .ebuild for those familiar with the concept), on various platforms. Now, one of the target platforms does not properly support the foo.yy -> foo.cc step, and has to use the foo.cc file generated on a Linux box. Now I have two ways to go about this: 1) Check in foo.cc into the project repository and somehow patch

问题 I need to build tesseract without leptonica dependency for some work(to porting using emscripten). I looked into the make files and it seems tesseract requires leptonica header files and lib files in order to build. Providing header files is not an issue but i can't provide lib files because of some reason(emscripten doesn't generate lib files of leptonica). and i tried to stop tesseract asking for leptonica by editing make files but it seems i'm heading in wrong way. I'm very new to make

问题 I have a list of cpp files in project which is built using automake tools. Some of them are written using pre-C++11 standard (ie C++98) and they cannot compile with c++11 flag of gcc (-std=c++11). Latest cpp files are using C++11 standard and they need -std=c++11 flag in compile. Can I define in Automake two lists of cpp source files and give different compilation flags? 回答1: This is ripped directly from Setting per-file flags with automake You may bundle your c++11 code into a lib and

问题 I'm integrating C check framework for my project and I was able to run autoreconf --install successfully without any errors. But when I integrate the C check framework, I'm getting an error and warnings that doesn't make sense. Here is the error I'm getting src/Makefile.am:7: warning: variable 'main_LDADD' is defined but no program or src/Makefile.am:7: library has 'main' as canonical name (possible typo) tests/Makefile.am:2: error: 'SHELLTESTS_PROGRAMS' is used but 'SHELLTESTSdir' is

问题 I already read about the difference between CFLAGS and CPPFLAGS. But my Makefile.am currently uses both DEFS and CPPFLAGS and I am not sure about the difference. DEFS += -DLOCALEDIR=\"$(localedir)\" -DDATADIR=\"$(datadir)\" -DPKGDATADIR=\"$(pkgdatadir)\" and: src_foo_CPPFLAGS = \ $(AM_CPPFLAGS) \ -I$(top_builddir)/src \ -DDATADIR='"$(datadir)"' \ -DMODULEDIR='"$(moduledir)"' \ -DLIBEXECDIR='"$(libexecdir)"' Both the CPPFLAGS and the DEFS seems to create defines with the -D option. So whats

问题 Background We build .mex files for both Matlab and Octave. The source code is common to both Matlab and Octave but with slight modifications here and there (taken care of via macro conditionals in the code). For reference, the source structure is: mex/ | ------------------------------ | | sources/ build/ | | ----------- ------------------------------- | | | | | | mex1/ ... mexN/ octave/ mex1.am ... mexN.am matlab/ | | | ----------- ------------- ------------- | | | | | | file1.cc ... fileM.cc

问题 Using autoconf in configure.ac I need to append to an output variable. Specifically I want to append to the LIBS variable differently for each of my programs (myprogram1 and myprogram2 in the Makefile.am). Lets imagine myprogram1 requires a -lboost_python and myprogram2 requires -losg. Essentially some programs require certain libs while others do not. Here is an example of what I am doing. Of course AC_SUBST does an assignment (= vs +=) from what I understand so that doesn't work. AC_CHECK

问题 I’ve written a C library that builds using Libtool, and I’d like to only build static libraries on Cygwin. To that end, I placed if test "$target_os" = "cygwin"; then AC_DISABLE_SHARED fi in my configure.ac . This does indeed disable building shared libraries on Cygwin; however, it also disables building them everywhere else. I assume this is because expanding AC_DISABLE_SHARED causes some unfortunate side effects. How can I use Libtool to avoid building shared libraries on Cygwin while still