configure

DESTDIR and PREFIX of make

由 我是研究僧i 提交于 2019-11-27 08:56:57
问题 I am trying to make software install to a specific directory. I found several ways, but not sure what are the differences between them. ./configure --prefix=*** make install DESTDIR=*** make install prefix=*** I am confused about the functions of these three. Do they achieve the same goal? 回答1: ./configure --prefix=*** Number 1 determines where the package will go when it is installed, and where it will look for its associated files when it is run. It's what you should use if you're just

Liferay: How to configure Liferay Portal

由 给你一囗甜甜゛ 提交于 2019-11-27 04:06:10
问题 How to configure or to override Liferay portal properties with portal.properties ? 回答1: Liferay properties is powerful instrument that allows us to configure Portal behaviour without coding of hooks-, ext- and theme-plugin. By new requirement we proof at first for possibility to solve this requirement with change of Liferay configuration. The default properties configuration can be found at Liferay source code: https://github.com/liferay/liferay-portal/blob/master/portal-impl/src/portal

Why always ./configure; make; make install; as 3 separate steps?

由 独自空忆成欢 提交于 2019-11-27 02:33:25
Every time you compile something from source, you go through the same 3 steps: $ ./configure $ make $ make install I understand, that it makes sense to divide the installing process into different steps, but I don't get it, why each and every coder on this planet has to write the same three commands again and again just to get one single job done. From my point of view it would make totally sense to have a ./install.sh script automatically delivered with the source code which contains the following text: #!/bin/sh ./configure make make install why would people do the 3 steps separately? Fatih

Append compile flags to CFLAGS and CXXFLAGS while configuration/make

由 风格不统一 提交于 2019-11-27 00:53:06
问题 The project that I am trying to build has default flags CFLAGS = -Wall -g -O2 CXXFLAGS = -g -O2 I need to append a flag -w to both these variables (to remove: 'consider all warnings as errors') I have a method to work it out, give make 'CFLAGS=-Wall -g -O2 -w'; 'CXXFLAGS=-g -O2 -w' OR Run ./configure and statically modify Makefile But I want to append my options with the existing options while running configure or make The post Where to add a CFLAG, such as -std=gnu99, into an autotools

How do I create a configure script?

由 烂漫一生 提交于 2019-11-26 22:31:35
问题 This may sound like a very generic question but here it goes. I have a requirement to create a configure script for my application, the result of this configure would be a generated makefile (basic configure , make , make install ). My question is, where do I start in building this? Is there an example I can follow? 回答1: To create the standard "configure" script you need GNU autoconf. You may need GNU automake and libtool too. There are tons of documentation and howtos. Google for something

Build 32bit on 64 bit Linux using an automake configure script?

由 走远了吗. 提交于 2019-11-26 18:51:13
问题 I'm using a 64bit system but want a set of 32bit binaries. What options must I pass to a configure script to generate a 32bit/x86 makefile? 回答1: Passing the following argument to configure script allowed me to build the 32bit library on 64bit Linux ./configure --build=i686-pc-linux-gnu "CFLAGS=-m32" "CXXFLAGS=-m32" "LDFLAGS=-m32" 回答2: Jack's answer is incomplete. You need compiler/libc support for 32-bit compilation. In some distros like Ubuntu, what you need to do is install packages gcc

What's the difference of “./configure” option “--build”, “--host” and “--target”?

由 大城市里の小女人 提交于 2019-11-26 17:01:49
The script ./configure accepts 3 options --build , --host and --target . I'm confusing their roles. What's the difference and semantics of them? user124850 As noted in this blog post and alluded to in the GCC Configure Terms , --target only applies when you are compiling toolchains. When you are doing normal cross-compilation of a library or binary you use --build=the architecture of the build machine --host=the architecture that you want the file to run on However, when you are building toolchains, things can get more complicated. I think that the following is correct (though I can't say I've

Android valgrind build fails

由 偶尔善良 提交于 2019-11-26 16:01:58
问题 Hello I'm trying to build valgrind for android-arm. On Linux Mint 13 it fails with: $ make echo "# This is a generated file, composed of the following suppression rules:" > default.supp echo "# " exp-sgcheck.supp xfree-3.supp xfree-4.supp glibc-2.X-drd.supp glibc-2.34567-NPTL-helgrind.supp glibc-2.X.supp >> default.supp cat exp-sgcheck.supp xfree-3.supp xfree-4.supp glibc-2.X-drd.supp glibc-2.34567-NPTL-helgrind.supp glibc-2.X.supp >> default.supp make all-recursive make[1]: Entering

Why always ./configure; make; make install; as 3 separate steps?

由 半腔热情 提交于 2019-11-26 10:06:10
问题 Every time you compile something from source, you go through the same 3 steps: $ ./configure $ make $ make install I understand, that it makes sense to divide the installing process into different steps, but I don\'t get it, why each and every coder on this planet has to write the same three commands again and again just to get one single job done. From my point of view it would make totally sense to have a ./install.sh script automatically delivered with the source code which contains the

What's the difference of “./configure” option “--build”, “--host” and “--target”?

由 末鹿安然 提交于 2019-11-26 04:59:21
问题 The script ./configure accepts 3 options --build , --host and --target . I\'m confusing their roles. What\'s the difference and semantics of them? 回答1: As noted in this blog post and alluded to in the GCC Configure Terms, --target only applies when you are compiling toolchains. When you are doing normal cross-compilation of a library or binary you use --build=the architecture of the build machine --host=the architecture that you want the file to run on However, when you are building
订阅 configure