makefile

Can't compile LAME for iOS

ⅰ亾dé卋堺 提交于 2021-02-09 10:58:26
问题 I'm trying to compile lame mp3 encoder as static library for iOS. I'd like to support all architectures including i686, armv6, armv7, armv7s and arm64. Here is my build script: #!/bin/bash DEVELOPER=`xcode-select -print-path` SDK_VERSION="7.1" mkdir build function build_lame() { make distclean ./configure \ CFLAGS="-isysroot ${DEVELOPER}/Platforms/${SDK}.platform/Developer/SDKs/${SDK}${SDK_VERSION}.sdk" \ CC="${DEVELOPER}/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -arch ${PLATFORM}

Choose between makefile and Makefile on Linux

坚强是说给别人听的谎言 提交于 2021-02-09 07:17:49
问题 I want to do a make in a directory with both Makefile and makefile. By default, it will execute makefile. Is there any options I can do to execute the Makefile instead? Thanks in advance. 回答1: The easy option is to use -f : $ make -f Makefile From man 1 make (the GNU make, I presume): If no -f option is present, make will look for the makefiles GNUmakefile , makefile , and Makefile , in that order. So you con link your Makefile to the name GNUmakefile. But my advise, if you really want this,

Choose between makefile and Makefile on Linux

南楼画角 提交于 2021-02-09 07:15:11
问题 I want to do a make in a directory with both Makefile and makefile. By default, it will execute makefile. Is there any options I can do to execute the Makefile instead? Thanks in advance. 回答1: The easy option is to use -f : $ make -f Makefile From man 1 make (the GNU make, I presume): If no -f option is present, make will look for the makefiles GNUmakefile , makefile , and Makefile , in that order. So you con link your Makefile to the name GNUmakefile. But my advise, if you really want this,

Choose between makefile and Makefile on Linux

故事扮演 提交于 2021-02-09 07:13:25
问题 I want to do a make in a directory with both Makefile and makefile. By default, it will execute makefile. Is there any options I can do to execute the Makefile instead? Thanks in advance. 回答1: The easy option is to use -f : $ make -f Makefile From man 1 make (the GNU make, I presume): If no -f option is present, make will look for the makefiles GNUmakefile , makefile , and Makefile , in that order. So you con link your Makefile to the name GNUmakefile. But my advise, if you really want this,

Choose between makefile and Makefile on Linux

拜拜、爱过 提交于 2021-02-09 07:12:29
问题 I want to do a make in a directory with both Makefile and makefile. By default, it will execute makefile. Is there any options I can do to execute the Makefile instead? Thanks in advance. 回答1: The easy option is to use -f : $ make -f Makefile From man 1 make (the GNU make, I presume): If no -f option is present, make will look for the makefiles GNUmakefile , makefile , and Makefile , in that order. So you con link your Makefile to the name GNUmakefile. But my advise, if you really want this,

Intel Fortran to GNU Fortran Conversion [closed]

走远了吗. 提交于 2021-02-08 10:35:56
问题 Closed. This question needs debugging details. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 4 years ago . Improve this question I am working on a custom CFD Solver written in Fortran 90 and MPI. The code contain 15+ Modules and was initially designed to work with the Intel Fortran compiler. Now since i do not have access to the Intel compiler I need to make it work using the GNU Fortran Compiler. I made

Intel Fortran to GNU Fortran Conversion [closed]

╄→гoц情女王★ 提交于 2021-02-08 10:33:26
问题 Closed. This question needs debugging details. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 4 years ago . Improve this question I am working on a custom CFD Solver written in Fortran 90 and MPI. The code contain 15+ Modules and was initially designed to work with the Intel Fortran compiler. Now since i do not have access to the Intel compiler I need to make it work using the GNU Fortran Compiler. I made

AOSP - Error: Overriding commands for target (…), previously defined at (…)

五迷三道 提交于 2021-02-08 06:08:16
问题 I'm trying to build AOSP for non - supported device (surnia - Moto E2 2015 LTE) . I solved lots of problems earlier but now I have one that I can't avoid. I saw a lot of people had that problem, but their was just warning... What can I do? Or could you help me finding surnia device tree (but for stock AOSP)? [100% 441/441] writing build rules ... FAILED: build/make/core/Makefile:28: error: overriding commands for target `out/target/product/surnia/system/vendor/lib/libHevcSwDecoder.so',

GNU Make Under Windows: Check for cygwin in PATH

别等时光非礼了梦想. 提交于 2021-02-08 05:43:26
问题 I have been putting together a makefile in a Windows environment for my team to use. I decided to use MinGW's version of make for Windows. I put that executable with its dependencies into a repository location that should be in everyone's PATH variable. The executable was renamed "make.exe" for simplicity. Then I realized that I have to account for the case when someone has cygwin's bin folder in their path. Commands like echo, rmdir, and mkdir will call echo.exe, rmdir.exe, and mkdir.exe

See output of shell script in Makefile

↘锁芯ラ 提交于 2021-02-07 20:46:49
问题 How can I execute a shell script before building my targets in a Makefile, and see the output as it runs? I have a script called prepare.sh that generates a bunch of .pyx files. The .pyx files are the starting point of my build process involving make. It goes from .pyx -> .c -> .o -> .so I don't like having to run prepare.sh separately prior to make. I'd like make to run it for me. I got it to work but I don't see the output of the command. I'd like to see it. This is what I have now: PATH :=