I'm having trouble with launching aptana 3 after an update yesterday.
Running on windows 7 64bit.
I get this error trying to launch:
The aptana studio 3 executable launcher was unable to locate its companion shared library.
Did a re-install with the latest version from the Aptana website, I didn't try this primarily because I feared all my settings would be gone (like the update did). Nothing to fear, I just needed to re-link my workspace.
All my preferences where still there.
Related
When I am trying to install CMake I get the error:
Visual Studio 15 2017 could not find any instance of Visual Studio.
I am using Windows 7 and Visual Studio 2017. The CMakeOutput.log file writes:
The system is: Windows - 6.1.7601 - AMD64
Any ideas?
I ran into the same error and performed the following steps to resolve the issue:
Open Visual Studio
Go to Tools -> Get Tools and Features
In the "Workloads" tab enable "Desktop development with C++"
Click Modify at the bottom right
These steps resulted in the "Visual C++ tools for CMake" feature being installed, but the other optional C++ features included in this workload may also helpful for what you are trying to do.
After the Visual Studio updater finishes installing try re-running the command. You may need to open a new command window.
In my case, I installed Visual Studio, selecting the workloads and modules that I wanted, but I ignored the request to reboot, assuming that shutting down the computer at the end of the day and restarting it the following day would suffice. I was wrong.
The following day I tried a cmake build and got the "could not find any instance of Visual Studio" error. After several attempts to resolve, I re-ran the installer, made no changes to the configuration, and clicked Modify. This time I let it reboot the computer. The reboot took a long time. After which my cmake build worked.
If you have already installed the workload Desktop development with C++ and still getting the following errors while using visual studio 2022 for flutter
Generator
Visual Studio 16 2019
could not find any instance of Visual Studio.
Building Windows application...
Exception: Unable to generate build files"
Solution: Follow these steps,
Edit your_flutter_path\packages\flutter_tools\lib\src\windows\build_windows.dart, and change the constant on line 28 from Visual Studio 16 2019 to Visual Studio 17 2022
Delete flutter_tools.stamp and flutter_tools.snapshot from your_flutter_path\bin\cache\
Run flutter clean in the project
I had the same issue "could not find any instance of Visual Studio"
but with Visual Studio 2019 (Community Edition) and I just had to configure the VS160COMNTOOLS variable so that CMake correctly detects Visual Studio.
export VS160COMNTOOLS="/c/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/Tools"
(cf https://cmake.org/cmake/help/latest/generator/Visual%20Studio%2016%202019.html)
With Visual Studio 15 2017, the variable you need should be VS150COMNTOOLS.
(cf https://cmake.org/cmake/help/latest/generator/Visual%20Studio%2015%202017.html)
NB: in my case, in a Travis-CI workflow, I installed Visual Studio using the commands (no need to reboot):
choco install visualstudio2019community
choco install visualstudio2019-workload-nativedesktop # required
With only the first package, CMake detection of VS2019 failed.
I was configuring a Jenkins build node and could successfully run CMake GUI manually but command line use or builds using the CMake plugin would fail with:
Visual Studio 16 2019 could not find instance of Visual Studio.
-A x64 parameter was added with no change in result.
The problem was that CMake could not determine the Windows SDK version.
By adding CMAKE_SYSTEM_VERSION parameter CMake was then able to find Visual Studio.
-D CMAKE_SYSTEM_VERSION=10.0.18362.0 (use your windows SDK version)
Environment:
windows 10 system build: 19042
CMAKE 3.19.4
VS 2019 Professional 16.8.4
Jenkins 2.235.1
Full command line that worked:
"C:\Program Files\CMake\bin\cmake" -G "Visual Studio 16 2019" -D CMAKE_BUILD_TYPE=Release -A x64 -D CMAKE_SYSTEM_VERSION=10.0.18362.0
When using VS 2017, be aware that this is really VS 2015, and CMake identified it as VS 2017 2022 which is not the version of VS 2017 I had, that gave me this error. So the conclusion I offer is to try different versions, specifically the 2015 one.
I had a similar issue where installing libzmq in my npm project was throwing the same error and that wasn't getting solved by enabling "msbuild" under "Desktop development with C++" in the Visual Studio installer.
My solution ended up being to reinstall the Windows build tools for npm with the following command.
npm install --global windows-build-tools
Note: Remember to run the command prompt (or whatever terminal you are using) as admin before running this.
If the CMake used to work with the installed Visual Studio and is broken someday, then the problem could be VS requires system reboot to complete some update.
For quick verification, rename HKLM\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\Setup\Reboot to like HKLM\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\Setup\Reboot.bak, then re-run cmake which should succeed. Don't forget to rename the registry back and reboot the system if this is the problem.
In my case, I was selecting different version of visual studio in that configuration dialog box whereas I installed different version.
Do select the same version.
Above solutions did not solve this issue for me. After installing node.js from https://nodejs.org/en/download/ apparently a correct version of windows-build-tools was installed
I reinstalled the Visual Studio 2019(my former one is 2017 version ) with all those settings required(my cmake version is 3.23.0),and it works. So try to install different versions.
In my case, the problem was gone after I deleted the previous cmake result directory and then ran cmake again.
if you have installed two or more Windows 10 SDK, delete them excluding latest one.
Try downloading the windows-build-tools package.
npm install --global --production windows-build-tools --vs2015
This step should be the end-all-be-all solution to fixing node-gyp problems. For most people, that’s true. NPM has a package called windows-build-tools that should automatically install everything you need to get node-gyp working, including the Microsoft build tools, compilers, Python, and everything else required to build native Node modules on Windows.
Recently I tried to upgrade Qt to 5.8.0 on Windows 7 32bit from Qt5.6.2 MSVC 2013, and I saw strange issues.
I downloaded and installed Visual Studio 2015 from this link: https://www.visualstudio.com/downloads/
After I installed Qt 5.8.0 MSVC 2015 version, Qt Creator 4.2.1 can be launched. From the welcome page, I selected the example named: "Address Book Example". And then after clicking "Configure" project, the project is listed in Qt Creator.
Now I tried to build the project, which was successful. But when I tried to run the project, I got the following error messages:
Starting C:\Qt\Examples\Qt-5.8\widgets\itemviews\build-addressbook-Desktop_Qt_5_8_0_MSVC2015_32bit-Debug\debug\addressbook.exe...
The program has unexpectedly finished.
C:\Qt\Examples\Qt-5.8\widgets\itemviews\build-addressbook-Desktop_Qt_5_8_0_MSVC2015_32bit-Debug\debug\addressbook.exe crashed.
I didn't see this kind of error before when I was using Qt5.6.2 with MSVC 2013. I also tried the following things:
Reinstall Qt5.8.0 MSVC 2015 using offline installer
Reinstall Qt5.7.1 MSVC 2015 using offline installer
Reinstall Qt5.6.2 MSVC 2015 using offline installer
Reinstall Qt5.8.0 using online installer, in which I chose MSVC 2013 and MSVC 2015
I still kept getting the same error messages.
When I went to the debug folder, double clicked the exe file, it said some Qt dlls were missing. I then manually copied to the debug folder, then the exe can be run with no problem.
Now I want to run app from inside Qt Creator, but not sure what is the issue with Qt Creator 4.2.1. I researched in Google for a few hours, but still cannot find out the reason why Qt Creator cannot run projects even it's own Example projects. (same errors for my own projects)
I feel it must be something to do with Qt creator environment/settings. Anyone has any ideas about this problem?
Update 1:
I tried to use MinGW with Qt Creator, the addressbook example can be run correctly. Looks like it's related to MSVC 2015. I need MSVC 2015, because all other environments don't support webenginewidgets, and I got:
:-1: error: Unknown module(s) in QT: webenginewidgets
Not sure if this is a bug in Qt or Qt creator.
Update 2:
In my Qt Creator, I saw warning icons for MSVC 2013 and MSVC 2015 compilers, please see the screenshots below:
I finally resolved the issue. The reason is that the Windows 10 SDK is missing.
After I download and install all default components of the Windows 10 SDK, everything worked on Windows 7 32bit.
Basically, to make sure we can use Qt5.8.0+ on Windows (including Qt WebEngine), we need to install both:
Visual Studio 2015, and
Windows 10 SDK
I'm late but I've found the main culprit is "ucrtbased.dll".
I didn’t install Windows 10 SDK.
I'm on Windows 7 SP1 x64, Qt 5.9.2 with Visual Studio Build Tools 2015 (v14.0.25420.1) and Windows 8.1 SDK with MS Debugger Tools (CDB) installed. The Release Configuration builds are without any issue but the Debug Configuration exhibits the same crash behavior. The fix is simple. The normal install of Visual Studio Build Tools 2015 with Win8.1 SDK places "ucrtbased.dll" in "C:\Program Files (x86)\Windows Kits\10\bin\x64\ucrt" for 64-bit and "..\x86\ucrt" for 32-bit builds - even the Windows 10 SDK is not installed. If these are included in system path, or copied to the Qt's current project build folder, the issue is simply resolved.
I installed Multi-Device Hybrid Apps for Visual Studio 2013 CTP 2.0. I then updated VS2013 to update 4. Now I can't upgrade MDHA to 3.0 because it tells me to uninstall 2.0 first, however the uninstaller doesn't work. When trying to uninstall 2.0 from Programs and Features, it just goes through the setup and then doesn't remove the software from the Add/Remove list.
I tried following this however it doesn't work:
http://support.microsoft.com/kb/3014133
I ended up discovering that the package GUID in the the KB article is wrong. I used this to uninstall the 2.0, then I could install 3.0. The package ID may vary so you may need to search the directory for vs2013mda_0.1.exe and replace the command with your package location.
"%ProgramData%\Package Cache\{38f367f1-1468-4f16-a4c4-29747084003b}\vs2013mda_0.1.exe" /uninstall /passive /force /burn.ignoredependencies={53d408db-eb91-43fb-9d8f-167681c19763};vsupdate_KB2829760
Also,be prepared to wait. This takes a long time.
Thank you TechnoTim, the problem is that, every people has its own package GUID.
To solve the problem, you must lunch the command from the root directory, c:\, changing the package GUID with your package GUID.
In my system:
C:\>"%ProgramData%\Package Cache\{dea88246-f74a-4171-ad6c-d9c978bf2973}\vs2013md
a_0.1.exe" /uninstall /passive /force /burn.ignoredependencies={53d408db-eb91-43
fb-9d8f-167681c19763};vsupdate_KB2829760
To find the right package GUID I go to C:\ProgramData\Package Cache\ and search for
vs2013mda_0.1.exe and save the path in the block note, then change in path in the orignal command and lunch it from the root directory c:\, and its work.
Sorry fom my english.
Goodbye!
"You cannot install Visual Studio Tools for Apache Cordova CTP3.0 in Visual Studio 2013"
To resolve this issue, follow these steps to uninstall Multi-Device Hybrid Apps for Visual Studio CTP 2.0
Open a command prompt as an administrator.
Run the following command: "%ProgramData%\Package Cache{dea88246-f74a-4171-ad6c-d9c978bf2973}\vs2013mda_0.1.exe" /uninstall /passive /force /burn.ignoredependencies={53d408db-eb91-43fb-9d8f-167681c19763};vsupdate_KB2829760
Run vs2013mda_0.3.exe again for Visual Studio Tools for Apache Cordova CTP 3.0.
The above worked when installing update 4, please see: http://support.microsoft.com/kb/3014133
I solved this problem by another way.
I have tried to uninstall from command line, but no one of paths don't exists on my computer.
And I simply created another user with administrator permissions and installed new apache cordova tools from that user.
In my situation it correctly works running by new created user and old user.
Sorry for my horrible English.
After long work with no issues, Aptana started to crash every time I try to create new ftp connection.
Is this a known issue?
I am on Linux 64 and using standalone version
got the same problem. I'm using standalone Aptana Studio 3 Version: 3.4.2.201308081805 with JRE Version: 1.7.0_45 on Kubuntu 64 bit 13.10 Saucy. Everything should be fine, but unfortunately it's not.
The problem seems to appear after upgrading the OS-Version. Aptana on the previous Kubuntu version was and still is running quite well.
My workaround:
Install 13.04 on V-Box,
install AptanaStudio on Guest-System,
load workbench from host-system,
do changes in Connection Manager and save them,
start Aptana on host-system and the changes are there
It's not exactly what I would call a convenient way, but it works.
I hope that there will be a solution for this issue soon.
Installing the latest Update Aptana 3.5.0.201312191422 fixes this issue.
Aptana uses GTK themes on kde. Change the Gtk2 style from QtCurve to other because it can't render the FTP windows
I couldn't get Meteorite and Telescope running on windows 7, any ideas how should we do this?
Here's what I tried:
installed Meteor on win7 using win.meteor.com
tried to install Meteorite (following instructions on its Github page), but it threw
couple errors (although it finished installation):
C:\Users\Daler\AppData\Roaming\npm\node_modules\meteorite\node_modules\ddp\node_modules\w
s\build\bufferutil.vcxproj(18,3): error MSB4019: The imported project
"C:\Microsoft.Cpp.D efault.props" was not found. Confirm that the path
in the declaration is correct , and that the file exists on
disk.
C:\Users\Daler\AppData\Roaming\npm\node_modules\meteorite\node_modules\ddp\node_modules\w
s\build\validation.vcxproj(18,3): error MSB4019: The imported project
"C:\Microsoft.Cpp.D efault.props" was not found. Confirm that the path
in the declaration is correct , and that the file exists on
disk.
cloned Telescope, then ran it with mrt from its folder, but got errors about missing dependencies of Meteorite. manually copied "router" and "page-js" packages to "Meteor/packages" as suggested here:
But still, running mrt or mrt run exits without error.
However running with meteor command sometimes starts the server on localhost and then fails due to a missing file and sometimes cannot find/start MongoDB.
Installing Microsoft Visual C++ 2010 Service Pack 1 Compiler Update for the Windows SDK 7.1 (as suggested by https://github.com/TooTallNate/node-gyp) fixed the MSB4019 error for me doing npm install xxx on Windows7 x64.
The readme of that update states that the recommended order is
Visual Studio 2010
Windows SDK 7.1
Visual Studio 2010 SP1
Visual C++ 2010 SP1 Compiler Update for the Windows SDK 7.1