Need to install gitahead via SCCM on our lab machines. Gitahead provides .exe installers, not .msi files. Need to find correct flags/parameters for silent install.
I've already tried /qn /q /silent /verysilent and the other common ones. They all still pop up the installer GUI.
Stackoverflow seems like a weird place to get support for a non-coding problem, but I'm doing as githead requests on their site: "Ask questions about using GitAhead on Stack Overflow by including the 'gitahead' tag." -okay, that's what I'm doing.
Looks like they use NSIS (an alternative to MSI technology). Silent installs need a /S or /SD switch and if I remember correctly it is case sensitive.
Thank you, Paul! Yes, that did the trick - silly of me to not have tried /S
Question resolved! I upvoted you but because I'm new here, it doesn't seem to have publicly shown.
Related
I'm using visual studio code to program in R and I have recently had trouble using the ?func and ??func command.
When typing something like ?rnorm, the message Couldn't show help for path: /library/stats/html/Normal.html shows up. The path is there and I'm sure R is in the path environment. This is really boggling me.
When I first installed R it was working absolutely fine in VSC but now it does not work. However the function works in the R shell. When I try to navigate to the R extension and click on "Help Topics by Package" it says help provider not available.
The packages/html files are there, but VSC doesn't want to access them.
Please advise what I can do to solve this.
I solved the same issue by checking my environmental variables. The steps I followed:
I added the bin installation file (C:\R\R-4.1.3\bin in my case, or C:\Program Files\R\R-4.1.3\bin) to the path in my user environmental variables. If you have an admin account, then you have to add the bin folder to the system environmental variables.
Check if you can start a R console from any terminal.
If that is positive, then in the Rpath settings for the R extension in vscode write r, or in the settings.json: "r.rpath.windows":"r"
Restart vscode. Check if the help pages are working.
Hope this helps ! Cheers.
This happened to me as well. I googled and tried different things and this works for me:
You need to provide the Rpath for the system you are using in the settings for the vscode R package. For example, for a windows machine, you need C:\Program Files\R\R-4.1.3\bin\x64\R.exe there if you installed the latest R using the default settings, and similarly for other systems.
Hope it helps!
I want to start developing of my first test addon. I have a problem on the basis of mr.bob. Any described ways have leaded to one result. my documentation
log image
Check
mrbob --help
do the same answer.
After I came to the conclusion the problem is in pre-installed Python2.7 with no worked mr.bobe and bobtemplates. I do not know how to make a working set.
Looking at your traceback I guess mr.bob is not fully supporting Windows.
The readline module on Windows is not available. There's some alternatives like pyreadline.
Seems it's a know issue: see https://github.com/domenkozar/mr.bob/issues/49
Don't know about mr.bob, but you could alternatively try adi.devgen (disclaimer: one of my add-ons). Install it with pip:
pip install adi.devgen
And then do:
devgen addOn yournamespace.youraddonname
I was compiling Qt, then saw in the log "C:\Program Files (x86)\Microsoft DirectX SDK (June 2010)\Utilities\bin\x86\fxc.exe" /nologo /E VS_Passthrough2D /T vs_4_0_level_9_3 /Fh libANGLE/renderer/d3d/d3d11/shaders/compiled/passthrough2d11vs.h ../../../3rdparty/angle/src/libANGLE/renderer/d3d/d3d11/shaders/Passthrough2D11.hlsl
It gave error Too many files specified ('E:/' was the last one), use /? to get usage information
it shows in the help that /E<name> entrypoint name
It seems to me that it is treating the /E option as the path E:/ (its unfortunate I have a drive E, and many data residing in it). Is there anyway around this? is my analogy correct? some suggestions would be really appreciated.
Having had the same problem recently, I asked colleagues about it and was advised to use MS's cmd.exe command prompt instead of MinGW's Git Bash prompt. For some reason that worked ! I won't pretend to understand how choice of command shell can help, but apparently it does.
See also discussion of this on Qt's own forum:
https://forum.qt.io/topic/73114/building-with-mingw64-on-windows-8
I am trying to follow this tutorial, in order to install the Nix package manager in my home directory instead of /nix.
I am doing the PRoot installation (see 2. in tutorial). At the end, the
tutorial proposes to be smart in Building native packages section, to be
able to run packages without PRoot:
To run packages natively (without PRoot) they have to be build from source because all paths to the nix store are hard-coded. It is simple, really:
mkdir $HOME/nix
nix-channel --update
env NIX_STORE_DIR=$HOME/nix nix-env -i nix
And now your Nix store gets built up using the new paths. The built binaries can be run directly from there.
I did that, but I don't see how it frees me from PRoot. If I don't do the /nix mounting point with PRoot, nothing works (no nix-env executable,
I can't install new packages).
Should this NIX_STORE_DIR environment variable be put in my .bashrc ?
It seems I always need to run PRoot because ~/.nix-profile points to
a /nix/... directory:
.nix-profile -> /nix/var/nix/profiles/default
There are more steps in the tutorial (5., 6.) - should I follow them ? It seems they apply only in case of using the manual installation (step 4.),
although it is not explicit.
Any help would be appreciated :)
For anyone stumbling on this old question: there is no currently supported way to install Nix without root. The above wiki was moved to https://nixos.wiki/wiki/Nix_Installation_Guide . It may well be out of date. PRoot could work, but even then, rebuilding the whole store at a different path is not a good idea, not the least because the binary caches won't help and you'll need to build everything.
I suggest trying Nix in a virtual machine or cloud server.
Future people from Google, it's still unsupported but does work. Script here that installs a couple dependencies, builds a temporary Nix, and uses that to install a proper version in your directory of choice.
I'm trying to build an application from source in windows that requires some Unix tools. I think it's the apparently standard ./configure; make; make install (there's no INSTALL file). First I tried MinGW but got confused that there was no bash, autoconf, m4, or automake exes in \bin. I'm sure I missed something obvious but I installed Cygwin anyways just to move forward. For some reason when I run
sh configure.sh
I get:
platform unix
compiler cc
configuration directory ./builds/unix
configuration rules ./builds/unix/unix.mk
My OS has identity problems. Obviously the makefile is all wrong since I'm not on unix but win32. Why would the configure script think this? I assume it has something to do with Cygwin but if I remove that I can't build it at all. Please help; I'm very confused.
Also is it possible to build using MinGW? What's the command for bash and is mingw32-make the same as make? I noticed they're different sizes.
Everything is fine. When you are inside CygWin, you are basically emulating an UNIX. sh runs inside CygWin, and thus identifies the OS correctly as Unix.
Have a look at GCW - The Gnu C compiler for Windows
Also, you might be interested in this help page, that goes into some detail about the minimal system (MSYS), such as how to install, configure et. c.
That should help you get bash, configure and the rest to work for MinGW as well.
From the Cygwin home page
Cygwin is a Linux-like environment for Windows. It consists of two parts:
A DLL (cygwin1.dll) which acts as a Linux API emulation layer providing substantial Linux API functionality.
A collection of tools which provide Linux look and feel.
Since configure is using the Cygwin environment, it is interacting against the emulation layer and so it is just like it's working on a Unix environment.
Have you tried building the application and seeing if it works?