I'm trying to install some software packaged using ISMP (InstallShield Multi Platform). I'm trying to do a silent mode install something like ./setup.bin -silent which does the installation completely. But, I want to have an option to install specific features using some properties file or something similar in silent mode. Any help would be appreciated. Thanks.
Related
xcode is over 10gb but I only need it to get some dependencies in the cmd line tools and install packages for nodejs. Without it I cant even set the compiler for bootstrap 4.
Is there a lightweight option?
You can use Terminal to try and install only command line tools:
xcode-select --install
Alternatively, you may also try go to the Apple developer website (Downloads > more downloads section), and, once you are logged in and have accepted the agreement, you may download the package for the command line tools from there.
We have a project made of python scripts and home-made tools. We use cmake with custom targets to handle the application of the tools and python sripts and install resulting binary resources.
We use this under GNU/Linux and MS Windows. It works well but we don't want to force our users to install a compiler, like Visual Studio under Windows.
So, is it possible to install and run cmake without any compiler ? We can use ninja as the build system.
Yes, its possible.
CMake's project() command takes a NONE parameter (no compiler/languages searched for or activated)
project(MyProject NONE)
CMake's -P script mode if you want to take CMake as a cross-platform scripting environment
I am trying to install Qt on a Linux machine remotely from a Windows machine using PuTTY.
When I run the command to install Qt on Linux I get the following error:
~/QT# ./qt-unified-linux-x64-2.0.4-online.run
QXcbConnection: Could not connect to display
Aborted
Please suggest any workaround.
You can use the software repository of that Linux distribution.
For example, if it's Debian or Ubuntu:
sudo apt-get install qtbase5-dev
But if you really want to use the installer (usually, when specific Qt version is needed), then try one of the options:
run an X server on that machine
use the --script option of the online installer (you'll have to write a script like here: https://stackoverflow.com/a/34032216/4742108), it will probably need UI anyways
see if the offline installer has an option to run without UI
refer to here: https://community.nxp.com/message/532966
maybe use the cmd "export DISPLAY=:0" and it works
Try to connect with ssh to the host machine using -X to enable X11 display:
ssh <username>#<ip> -X
aqtinstall is a good option: https://github.com/miurahr/aqtinstall
It's a simple command line tool to download and install any Qt version. It's a fork of my old qli-installer script.
How to enable debugger in fp-ide? I read somewhere that I should compile fp-ide from sources, but I don't know how to do this. Can someone help me?
Get the generic linux tar installer (fpc-2.6.0.x86_64-linux.tar) for FPC from http://www.freepascal.org/down/x86_64/linux-hungary.var It comes with a precompiled IDE with integrated debugger support and it works fine at least on 12.04 LTS.
I wasn't able to find a PPA for fp-ide, but I can describe how the CLI IDE is compiled on Arch Linux as documented in the repository. Do note that compiling will not enable the debugger in the CLI, as it seems to be an incompatibility between gdb and fp (fp-ide) according to e.g. this bug report in Debian. On Arch Linux, the fpc package also doesn't support the debugger in fp by design (it is explicitly disabled using the NOGDB flag).
Anyhow, here goes the compilation process:
Make sure you have FreePascal installed already, as you need it to compile the IDE
Download the source tarball
Extract the tarball to a location of your convenience and cd into that directory
Execute the following code from within your shell:
pushd fpcsrc/compiler
fpcmake -Tall
popd
make build
make -j1 install
# in Arch, the switch "NOGDB=1" is present in both make lines
That should compile the IDE and install it (you can even try to integrate it in dpkg by using checkinstall instead of make install, but take a look at the Arch PKGBUILD to see an example of what might be needed).
But why do you use the command line IDE fp instead of lazarus? With lazarus you can also make console applications and it offers much more features (e.g. working debug support).
I wanted to use cscope enabled vim - unfortuantely , the binaries at work are not compiled with cscope support , and when I tried building from src , I'm getting a lot of errors due to proper dev packages not being installed.
So , does anyone have a link where I can a precompiled binary with cscope support ? Btw , I'm using linux.
Just build your own vim binary from source code maybe a good solution ^_^
wget ftp://ftp.vim.org/pub/vim/unix/vim-7.2.tar.bz2
tar xjf vim-7.2.tar.bz2
cd vim72
./configure --enable-cscope
make && make install
You will get a cscope supported vim 7.2
Not quite an answer to your request for a pre-compiled vim 7.2, but you said part of your compiling problems is that you "don't have the privileges for installing reqd packages" (in you comment to #chenkaie's answer). If the other reqd packages use configure, you can compile them to install into a directory you have control over, like this:
./configure --prefix=/dir/with/permissions
make && make install
configure-based installers support the --prefix switch, which results in the installed packages in locations like <prefix>\bin, <prefix>/lib, etc. With this trick you may be able to build all the reqd packages in order to build vim 7.2 itself.
If the reqd packages are not configure-based, you might want to look at the installer (makefile?) of the reqd package to see if it has an option similar to configure --prefix=<dir>
I have the default package Ubuntu gives me from doing an 'apt-get install vim', vim_1%3a7.1-138+1ubuntu3.1_i386.deb.
Inside of vim, when I type
:echo has('cscope')
it prints
1
as expected.
Granted, you do say you are looking for Vim 7.2 I don't know what improvements 7.2 has seen over 7.1, but it looks like there are still build problems with 7.2 that are being hammered out. I'd suggest just using 7.1 for the time being.