make-install

How to install a specific version of NASM on MacOS

杀马特。学长 韩版系。学妹 提交于 2019-12-24 10:40:43
问题 I got NASM for MacOS from http://www.nasm.us/pub/nasm/releasebuilds/2.11.06/macosx/ How to do I install this specific version of NASM? I know that I can do a brew install nasm . But I dont want the latest version. I want to install NASM 2.11.06 for MacOS. How should I install the nasm-2.11.06-macosx.zip that I have downloaded? Environment: I am running MacOS Sierra . 回答1: All you would need to do is: Unpack the zip file Update your PATH statement to include the location you unzipped the

How do I write CMake install for a library?

…衆ロ難τιáo~ 提交于 2019-12-23 12:46:02
问题 Here is my try: IF (NOT WIN32) #INSTALL_TARGETS(${LIB_INSTALL_DIR} ${tinyscheme-nix_BINARY_DIR}/libtinyscheme.so) #INSTALL(TARGETS ${tinyscheme-nix_BINARY_DIR}/libtinyscheme.so DESTINATION ${LIB_INSTALL_DIR}) ENDIF() Both variants are wrong. I want to move libtinyscheme.so from ${tinyscheme-nix_BINARY_DIR} to /lib or /lib64 . Basically, I think ${LIB_INSTALL_DIR} handles it. How can I make it? Where is my mistake? 回答1: You probably want the FILES version of install here instead of the TARGETS

VTK install error cannot find libvtkCommonCore-6.3.so.1

那年仲夏 提交于 2019-12-10 11:24:36
问题 I'm trying to install VTK but I'm getting the following error CMake Error at Common/Core/cmake_install.cmake:47 (file): file INSTALL cannot find "/home/VTK-6.3.0/VTKBuild/lib/libvtkCommonCore-6.3.so.1". Call Stack (most recent call first): cmake_install.cmake:100 (include) These are the steps I followed cd VTKBuild cmake ..\ -D"CMAKE_INSTALL_PREFIX:PATH=/home/VTK-6.3.0/VTKBuild" make make install Can anyone point me to what might be going wrong 回答1: I had to turn off shared library option,

VTK install error cannot find libvtkCommonCore-6.3.so.1

蹲街弑〆低调 提交于 2019-12-06 08:39:30
I'm trying to install VTK but I'm getting the following error CMake Error at Common/Core/cmake_install.cmake:47 (file): file INSTALL cannot find "/home/VTK-6.3.0/VTKBuild/lib/libvtkCommonCore-6.3.so.1". Call Stack (most recent call first): cmake_install.cmake:100 (include) These are the steps I followed cd VTKBuild cmake ..\ -D"CMAKE_INSTALL_PREFIX:PATH=/home/VTK-6.3.0/VTKBuild" make make install Can anyone point me to what might be going wrong I had to turn off shared library option, these are the configuration I used to build VTK mkdir VTKBuild cd VTKBuild cmake ..\ -DCMAKE_INSTALL_PREFIX=

Adding a custom installation directory option to Autoconf-generated configure scripts

倖福魔咒の 提交于 2019-12-06 00:20:10
问题 configure scripts always include something like the following in the help message: ... By default, `make install' will install all the files in `/usr/local/bin', `/usr/local/lib' etc. You can specify an installation prefix other than `/usr/local' using `--prefix', for instance `--prefix=$HOME'. For better control, use the options below. Fine tuning of the installation directories: --bindir=DIR user executables [EPREFIX/bin] --sbindir=DIR system admin executables [EPREFIX/sbin] --libexecdir

How to install Qt on Windows after building?

青春壹個敷衍的年華 提交于 2019-11-27 11:09:06
I can't find any information on how to install Qt built on Windows. In wiki article How to set up shadow builds on Mac and Linux there's description of -prefix option in configure script but this option is not available on Windows. I know I can use Qt right from the build folder but it does not seem the right thing not to perform an install step. One problem with this approach is size; Qt's build folder takes about 4GB space whereas after installing using binary installer Qt takes about 1GB space. I guess the difference is due to temporary files created during building. I hope some install

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

How to install Qt on Windows after building?

折月煮酒 提交于 2019-11-26 17:58:56
问题 I can't find any information on how to install Qt built on Windows. In wiki article How to set up shadow builds on Mac and Linux there's description of -prefix option in configure script but this option is not available on Windows. I know I can use Qt right from the build folder but it does not seem the right thing not to perform an install step. One problem with this approach is size; Qt's build folder takes about 4GB space whereas after installing using binary installer Qt takes about 1GB

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