I am trying to write a bat file for auto build generation. Could somebody please tell me how to change the install version and the version string from command line in install jammer? I am using below code for creating build. It runs well but now I need to change its install version and version string. how can I do this?
C:\Program Files<x86>\installjammer\installjammer --output-dir D:\Sumeet --build D:\AgnisysProjects\My InstallJammer Projects\Install jammer project\IDesignSpecExcel2007\IDesignSpecExcel2007.mpi
ok i got solution
C:\Program Files (x86)\InstallJammer> installjammer -DVersion 5.16.34.0 -DInstallVersion 5.16.34.0 --output-dir D:\Sumeet --build-for-release D:\AgnisysProjects\My InstallJammer Projects\Install jammer project\IDesignSpecExcel2007\IDesignSpecExcel2007.mpi
Related
I have installed a vcpkg package with vcpkg install shogun:x64-windows. The build fails and I need to change a file to fix it.How can I rebuild the package without the install option, that overwrites my changes?I cannot find any VC project in the vcpkg\buildtrees\shogun\x64-windows-<configuration>\src\shogun folder.
You should:
delete buildtrees directory
Execute command "vcpkg remove shogun:x64-windows"
If you need to change shogun solution before install you should write a .patch file and copy to this path("(install_path)\vcpkg\ports\shogun")
Add your patch file to "(install_path)\vcpkg\ports\shogun\portfile.cmake"
Find this line "set(ABSEIL_PATCHES" and add your patch file name in next line
Then "vcpkg install shogun:x64-windows"
I can't build my Rust project when I add an SSL dependency in my cargo file.
This isn't new to Windows, but I'd like to resolve the issue such that I can use Powershell and native Windows development to work on my Rust project.
The dependency in question is the following:
[dependencies.ws]
version = "0.8.0"
features = ["ssl"]
When I run cargo build, I get a lot of errors regarding SSL as I'm on Windows so let us begin debugging this step by step.
First errors:
PS C:\Users\sam\vcs\project> cargo build
Compiling openssl-sys v0.9.43
error: failed to run custom build command for `openssl-sys v0.9.43`
process didn't exit successfully: `C:\Users\sam\vcs\project\target\debug\build\openssl-sys-d964f46e4c48d206\build-script-main` (exit code: 101)
--- stdout
cargo:rustc-cfg=const_fn
cargo:rerun-if-env-changed=X86_64_PC_WINDOWS_MSVC_OPENSSL_LIB_DIR
X86_64_PC_WINDOWS_MSVC_OPENSSL_LIB_DIR unset
cargo:rerun-if-env-changed=OPENSSL_LIB_DIR
OPENSSL_LIB_DIR unset
cargo:rerun-if-env-changed=X86_64_PC_WINDOWS_MSVC_OPENSSL_INCLUDE_DIR
X86_64_PC_WINDOWS_MSVC_OPENSSL_INCLUDE_DIR unset
cargo:rerun-if-env-changed=OPENSSL_INCLUDE_DIR
OPENSSL_INCLUDE_DIR unset
cargo:rerun-if-env-changed=X86_64_PC_WINDOWS_MSVC_OPENSSL_DIR
X86_64_PC_WINDOWS_MSVC_OPENSSL_DIR unset
cargo:rerun-if-env-changed=OPENSSL_DIR
OPENSSL_DIR unset
note: vcpkg did not find openssl as libcrypto and libssl: Aborted because VCPKGRS_DYNAMIC is not set
note: vcpkg did not find openssl as ssleay32 and libeay32: Aborted because VCPKGRS_DYNAMIC is not set
Alright, lets set OPENSSL_LIB_DIR, OPENSSL_INCLUDE_DIR, and OPENSSL_DIR
$env:OPENSSL_LIB_DIR="C:\OpenSSL-Win64\lib"
$env:OPENSSL_INCLUDE_DIR="C:\OpenSSL-Win64\include"
$env:OPENSSL_DIR="C:\OpenSSL-Win64"
However, now running cargo build or cargo run actually compiles, but I don't think SSL works correctly since the code path that connects to the websocket fails with error none.
I installed the latest (1.1.0j) full (non-slim) version of OpenSSL from the following website: https://slproweb.com/products/Win32OpenSSL.html
The only environment variable it had set was:
OPENSSL_CONF: C:\OpenSSL-Win64\bin\openssl.cfg
But I also added C:\OpenSSL-Win64\bin to my PATH.
When cargo build actually compiled, the websocket fails with error None
The on_error block is executed on my Windows box, but my Linux machine never executes this code block.
Just so we're on the same page, this is the output of the print statement:
fn on_error(&mut self, err: ws::Error) {
println!("On Error, {}", err)
}
None isn't a very descriptive answer. So I assumed that I just needed some certs since OpenSSL doesn't come with certs.
I downloaded a cacert.pem from somewhere online and placed it into the certs folder of the OpenSSL installation but that didn't make much difference either. Still the same None error.
On my Linux box, I would expect the websocket connection to succeed and for the code to proceed to on_open:
fn on_open(&mut self, _: ws::Handshake) -> ws::Result<()> {
...
}
Has anyone worked through this OpenSSL issue on their Windows development environment?
UPDATE 0
As per Cloud's advice, I tried to use VCPKG. Unfortunately it didn't work.
PS C:\Users\sam\vcs\vcpkg> .\vcpkg.exe list
openssl-windows:x64-windows-static 1.0.2q-2 OpenSSL is an open source project that provides ...
openssl-windows:x86-windows 1.0.2q-2 OpenSSL is an open source project that provides ...
openssl:x64-windows-static 0 OpenSSL is an open source project that provides ...
openssl:x86-windows 0 OpenSSL is an open source project that provides ...
Then I set the variables in my powershell window:
PS C:\Users\sam\vcs\project> $env:OPENSSL_DIR = 'C:\Users\sam\vcs\vcpkg\installed\x64-windows-static'
PS C:\Users\sam\vcs\project> $env:OPENSSL_STATIC = 'Yes'
PS C:\Users\sam\vcs\project> $env:VCPKGRS_DYNAMIC='1'
Then I ran cargo clean and then cargo build and I still got the same error where my websocket throws the error None.
Still no luck here.
clone vcpkg
open directory where you've cloned vcpkg
run ./bootstrap-vcpkg.bat
run ./vcpkg.exe install openssl-windows:x64-windows
run ./vcpkg.exe install openssl:x64-windows-static
run ./vcpkg.exe integrate install
run set VCPKGRS_DYNAMIC=1 (or simply set it as your environment variable)
I had the same issue. Older version of the README of rust-openssl has the installation process for the Windows.
Precompiled Binaries
Download the precompiled binaries from here(non-light version), and install it. After the installation, set the environment variable OPENSSL_DIR to the installation path.
set OPENSSL_DIR=path\to\the\installation\dir
If you chose the Copy OpenSSL DLLs to: The OpenSSL binaries (/bin) directory option during the installation, add that directory to your path as well.
set PATH=%PATH%;path\to\the\installation\dir\bin
Then, you need to install the root certificate.
Using vcpkg
Install vcpkg by following the instructions on the README. After installation, run these commands.
vcpkg install openssl:x64-windows
set VCPKG_ROOT=c:\path\to\vcpkg\installation
Then, you need to install the root certificate.
Installing the root certificate
Download the cacert.pem file. Save it to somewhere (i.e C:\Program Files\OpenSSL-Win64\certs\cacert.pem), and add the SSL_CERT_FILE environment variable and point it to the file.
set SSL_CERT_FILE=C:\Program Files\OpenSSL-Win64\certs\cacert.pem
None of the other answers worked for me but I got it working with vcpkg and static linking. Here is what I did (I was trying to install wrangler, it worked after following the steps below and running cargo install wrangler).
Install vcpkg (following the instructions from https://github.com/Microsoft/vcpkg#quick-start-windows). I ran this in a Visual Studio 2019 Developer Command Prompt (%comspec% /k "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Auxiliary\Build\vcvars64.bat") but I don't know if this is necessary.
cd C:\
git clone https://github.com/microsoft/vcpkg
cd vcpkg
vcpkg\bootstrap-vcpkg.bat
From the same command prompt, install openssl
vcpkg\vcpkg install openssl:x64-windows-static
Install the CA certificates (as described by Fatih Karan's answer and the old README of the rust-openssl project)
mkdir "C:\Program Files\OpenSSL-Win64\certs"
curl --remote-name --time-cond "C:\Program Files\OpenSSL-Win64\certs\cacert.pem" -o "C:\Program Files\OpenSSL-Win64\certs\cacert.pem" https://curl.se/ca/cacert.pem
In a command prompt in your Rust project (or any other directory if you don't have a Rust project and just need to cargo install something), set the following environment variables:
set OPENSSL_NO_VENDOR=1
set RUSTFLAGS=-Ctarget-feature=+crt-static
set SSL_CERT_FILE=C:\OpenSSL-Win64\certs\cacert.pem
OPENSSL_NO_VENDOR to 1: Instruct the openssl-sys crate to use a pre-compiled openssl library. If this is not set it will try to compile it and fail (because perl is typically not available on Windows).
RUSTFLAGS to -Ctarget-feature=+crt-static: Instruct the Rust compiler (or more precisely the linker invoked by the Rust compiler) to produce a statically linked binary. If this is missing, the vcpkg crate (which is used by the openssl-sys crate to find the pre-compiled openssl library) will use the vcpkg triplet x64-windows-static-md. It seems that this triplet does not exist for openssl. With this environment variable, vcpkg will use the triplet x64-windows-static and this worked for me.
SSL_CERT_FILE to the location of cacert.pem: You need the root certificates in this file to make secure connections to servers.
I just had this issue and none of them worked, but here is what worked for me on Windows 11.
Install OpenSSL from http://slproweb.com/products/Win32OpenSSL.html into C:\Program Files\OpenSSL-Win64
Set all your env variables, for me I set OPENSSL_CONF to C:\Program Files\OpenSSL-Win64\bin\openssl.cfg and added C:\Program Files\OpenSSL-Win64\bin to my path.
Download the cert, assuming you have wget installed, wget https://curl.se/ca/cacert.pem -o cacert.pem into C:\Program Files\OpenSSL-Win64\certs
Next step is to set up your environment for building openssl run in powershell:
$env:OPENSSL_NO_VENDOR=1
$env:RUSTFLAGS='-Ctarget-feature=+crt-static'
$env:SSL_CERT = 'C:\OpenSSL-Win64\certs\cacert.pem'
$env:OPENSSL_DIR = 'C:\Program Files\OpenSSL-Win64'
and run cargo build
the cargo build logic for C/C++ libraries is quite simple actually, it just compiles a rust program which searches for include path and libs and then produce some text output and cargo will consume it.
From https://github.com/sfackler/rust-openssl/blob/master/openssl-sys/build/find_normal.rs I can see some vcpkg keywords, then I would suggest you simply using vcpkg to resolve all your dependencies, and get rid of those env variables.
git clone https://github.com/Microsoft/vcpkg.git
cd vcpkg
./bootstrap-vcpkg.bat
#Add the current folder into PATH environment variable
vcpkg install openssl-windows:x64-windows
#Switch to the rust project
cargo build
I am a newbie in linphone compilation and I am trying to compile it on my Ubuntu system.
Configuration:
OS: Ubuntu 14.04 LTS
Linphone version: 3.9.1
Inno compiler setup using wine
I have followed all the steps mentioned in README file of Linphone and followed below steps.
Install dependencies libtool, inittool, etc.
Clone belle-sip and followed it's README.
Installed dependencies pkg-config, libantlr3c-3.2, antlr3, bctoolbox (using clone and cmake), gcc, cunit.
Other debian / ubuntu dependencies from README such as libcunit1-dev, libpolarssl-dev, make, libgtk2.0-dev, libspeexdsp-dev, libavcodec-dev, libswscale-dev, libx11-dev, libxv-dev, libgl1-mesa-dev, libglew1.6-dev, libv4l-dev, libxml2-dev, libreadline-dev, libgsm1-dev, libtheora-dev, libsqlite3-dev, libupnp4-dev, libsrtp-dev
compile using ./autogen.sh, ./configure, make, make install, make zip, make setup.exe
All above command run successfully and generate output file successfully like Makefile, .zip file, .exe file.
when I am trying to install generated .exe (Size 22 MB) in any windows system, it install successfully but Linphone.exe file not generated during installation
It gives an error "Unable to execute file" (attached error screenshot).
Output of command "make setup.exe" is here
I am very grateful if anyone help me to solve this issue.
A bit late, but : the file added to the installer is named bin/linphone, not bin\linphone.exe according to the logfile. Looks like an oversight, as Windows uses extensions to indicate executable files whereas Linux uses the +x bits.
I am trying to get PHPDocumentor running on a local XAMPP installation.
Sadly I having a hard time doing it using package managers.
Some basic questions about package managers first:
How do I know where to install a package? For example: I installed PHPDocumentor using Composer. I go to my C:\xampp\htdocs\ and run a command:
composer require "phpdocumentor/phpdocumentor:2.*"
This installs phpdocumentor in a " vendor" folder in xampp\htdocs\
Is this the correct path to install all these packages or is there a default dir to install this?
If I want to uninstall the packages, do I simply delete the "vendor" dir?
After the installation I ran PHPdocumentor and got an error:
Unable to find the dot command of the GraphViz package. Is GraphViz
correctly installed and present in your path?
To resolve this, I tried the following:
Installed the package graph/graphviz while my pointer was in the htdocs-folder and pointed a path to the folders:
C:\xampp\htdocs\vendor\graph\graphviz
...graph\graphviz\src
...graph\graphviz\tests
None of the above solved the problem.
According to this link I have to add the \graphiz\bin directory to path, but there is no "bin" dir?
Can anyone help me out with this?
Best regards,
Abayob
Unable to find the dot command of the GraphViz package. Is GraphViz correctly installed and present in your path?
The steps to resolve this error are:
download zip from https://graphviz.gitlab.io/_pages/Download/Download_windows.html
extract to c:\some\where\graphviz
add c:\some\where\graphviz\bin to your environment variable PATH
run phpdoc
I don't like to have 184MB of usefull stuff on my PC just to run the 'dot' command?
Yes, its a lot of stuff. A more lightweight solution would be nice.
I'm trying to install the new Cabal in Windows 7. It successfully installs 1.18.02, but when I run "cabal --version" it shows 1.16. The folder C:\Users\me\AppData\Roaming\cabal\bin is at the front of my PATH.
When I directly run the 1.18 executable, I get a bunch of "cabal.exe does not exist" errors.
How can I configure Cabal to use version 1.18 by default?
There is a path conflict due the way haskell platform installs cabal.exe
As seen in this ticket
To fix it:
Delete `C:/program files(x86)/Haskell platform/lib/extralibs/bin/cabal.exe.`
In any case, you can use search tool to find which cabal.exe to delete.
I used cabal-dev to install cabal 1.18 to a sandbox, such that C:\cabal-dev\cabal-dev\bin contains the latest (1.18) cabal executable. I then set C:\Cabal-dev\cabal-dev\bin as the first Variable value in the "Path" variable in "systems variables" (as opposed to the "PATH" variable in "user variables"). That worked for me, and allowed me to keep the older build of cabal intact, (in case its needed later).
It worked for me. Good luck. Here are my exact steps:
Install cabal-dev
open command prompt anywhere
execute following command: “cabal install cabal-dev”
Install new cabal
create directory: c:\cabal-dev, cd to it
execute following command: “cabal-dev install cabal-install”
Set new, upgraded cabal path as higher priority
Close any open command prompts
run: Sysdm.cpl
Go to the “Advanced” tab
Click “Environment Variables”
Select the “Path” variable listed in the “System variables” (lower) windows
Click edit
Add following string to the beginning of the variable value:
“C:\Cabal-dev\cabal-dev\bin;”
Ok, Ok, Ok
Ensure latest cabal is being run:
Open command prompt (anywhere except c:\cabal-dev\ *)
execute following command: “cabal –V”
cabal version should be 1.18.0.2
One other possible cause of this error (aside from the cabal in extralibs problem described in another answer) is that the ld in your path can't read the .o files that GHC produces.
I hit this problem with GHC 7.8.1 RC1, and could see this going wrong by running cabal install with -v3. The 'ld' on my path was coming from Haskell Platform 2013.2.0.0.
Adding mingw\bin from the new GHC's directory to the path fixed the problem.