link 1
it worked on win32 build configuration debug mode, but doesn't work on x64 build configuration debug mode.
how can i change default command prompt on x64 build config ?
Run the x64 version from ConEmu, and set the same setting there.
Related
I'm trying to get WSL 2 working on my Windows 10 machine. I have followed the "Manual" directions in this page:
https://learn.microsoft.com/en-us/windows/wsl/install-win10#set-your-distribution-version-to-wsl-1-or-wsl-2
And then downloaded 2 different Ubuntu distros linked in this page:
https://learn.microsoft.com/en-us/windows/wsl/install-manual
I set the default version to WSL 2.
After invoking "Add-AppxPackage" (with no errors) and restarting, the WSL still reports that I have no installed distributions.
See:
I have confirmed that all Hyper-V options have been enabled in Windows Features, along with Virtual Machine Platform, and Windows Subsystem for Linux.
I have tried "wsl /install" but it simply reports the same "Windows Subsystem for Linux has no installed distributions."
I have tried Add-AppxPackage with both administrator rights and non adminstrator rights with no difference.
How can I get WSL to allow me to install a distro?
After performing all of the steps above, I noticed that "Ubuntu 18.04 LTS" was in my "Recently Added" programs list in the start menu. Double clicking on it finished the installation.
You loaded your distro from the Windows Store, but did you Open it from the Windows Store?
You need to do this to go through the install process, during which you'll create a username and password.
Once you've done this, you should see Ubuntu (or your other distro of preference) listed in wsl -l -v as running, along with the WSL version under which it's running.
Incidentally, if you find it's running under WSL 1 although you'd set the default to WSL 2, use wsl -l -v to get its exact name, then use wsl --set-version MY-DISTRO-NAME 2 (replacing MY-DISTRO-NAME with that exact name given before). Your current instance will be terminated and WSL will spend the next few minutes converting the distro.
I am trying to setup Cypress on WSL ubuntu for windows 10 machine. WSL ubuntu does not come up with its own display. Hence, we need to follow few steps before setting up Cypress. I followed all the steps mentioned in the blog here:
https://nickymeuleman.netlify.app/blog/gui-on-wsl2-cypress
But I keep getting the following error:
Cypress failed to start.
This is usually caused by a missing library or dependency.
The error below should indicate which dependency is missing.
https://on.cypress.io/required-dependencies
If you are using Docker, we provide containers with all required dependencies installed.
----------
(Cypress:1690): Gtk-WARNING **: 10:15:51.766: cannot open display: 183.87.117.18:0.0
----------
Platform: linux (Ubuntu Linux - 18.04)
Cypress Version: 4.6.0
I have also installed XLaunch for windows 10.
Was anyone able to resolve this issue earlier ? Could anyone please help me resolve this ?
Thanks
Got the idea from here: https://github.com/microsoft/WSL/issues/4106#:~:text=you%20may%20also%20need%20to%20launch%20vcxsrv%20with%20the%20-ac%20argument.
If you have XLaunch running - exit it by double-clicking on the icon in the taskbar and click Exit;
Then open your start menu > right-click XLaunch shortcut > More > Open file location;
Right-click XLaunch shortcut in the Explorer window > Properties;
Add " -ac" without double quotes right after the closing double quote in the Target field - i.e. for me it was "C:\Program Files\VcXsrv\xlaunch.exe" -ac;
Click ok
Now run Cypress again. Yay! Ran for me :)
For me, this was caused by having a WSL1 image (despite having WSL2 installed). You can check via wsl --list --verbose. Follow steps here to convert to WSL2.
I have a build definition in TFS that compile my code, then using a post build event, I create a Setup.exe file using Installshield.
Using Release Management I am able to deploy the installer to a machine and start the installation process using the tool RunCommandLine, I add the required parameters to the setup.exe so it will install the application silently (using an answer file to avoid user interaction). This process works smoothly!!!
I want to go far, so I tried to launch a release from a gated check-in....change the build template, install the release management client in the build agent, configure my build definition......I performed a small change in my code, then a check-in.....it compiles in the server, and start the release process: deploy the installer and start the installation process using the tool RunCommandLine, I add the required parameters to the setup.exe so it will install the application silently.....but I got a timeout so the release was rejected. I check the machine and found that the setup.exe was still running 0% CPU usage.....very strange.
Checking the build log I found that the command line used by msbuild to launch the release process is something like this:
C:\Program Files (x86)\Microsoft Visual Studio 12.0\Release Management\Client\bin\ReleaseManagementBuild.exe -tfs "http://tfs:8080/tfs/Mycollection" -tp "Project1" -bd "Mybuild" -bn "Mybuild_20150623_15.1.0.9" -ts "QA" -nologo
I ran it, and the behavior was the same: the installer got stuck...0% CPU Usage.....Release rejected by timeout.....
So...I open Release Management Client look for the recently created release, and click in the option "Retry failed deployment"....It works!!!! the installer install!!! it does not hangs!!!
I was able to reproduce this behavior several times:
Release launched from Release Management Console......Works
Release launched from ReleaseManagementBuild.exe .......Does not works (Setup.exe hangs)
Any suggestion??
I am writing a batch script in which I need to run a candle command:
candle.exe - present in wix installation 'bin' directory
I have set the path during my batch file load to the wix installation directory, and have checked writing
candle.exe abc.wxs -dplatform=x86 -ext WixUtilExtension
But on Windows XP it gives me an error:
The Application Failed to initialize properly (0xc00001235)" .Click on OK To terminate
On Windows 7, candle.exe works fine.
How can I resolve this?
I guess it is because i have not specified as to how to deal with different OS
This actually seems to be a result of not having .Net framework installed. Try installing .net 3.5 for Windows XP, or later for Windows 7 +.
Unable to locate the JVM for project scrapbook1. Please verify that you have a project-level JVM installed by inspecting your project's build path.
I get this error in the console when i debug my web application in Eclipse
Please help !!!
Have you installed JVM/JDK? Assuming you are on Windows, go to command prompt and type
set %JAVA_HOME%
This should the path to JDK. If it does not, then you need to install JDK and set the parameter JAVA_HOME in environment variables.
Once you have installed JDK and set the variable, check following: Go to Java build path of your project (Hit Alt+Enter on your project) and see if it shows JRE system library as shown in image:
I had the same problem, but the JDK was installed. I just updated all the libraries 'Help -> Check for Updates' and then restarted Eclipse. After that, everything worked.