My setup is:
Visual Studio 2012
Qt 5.2.0 from
http://download.qt-project.org/official_releases/qt/5.2/5.2.0/qt-windows-opensource-5.2.0-msvc2012-x86_64-offline.exe
Unzip Qwt from http://sourceforge.net/projects/qwt/files/qwt/6.1.0/qwt-6.1.0.zip/download to C:\qwt-6.1.0
Opened Qt 5.2.0 64-bit for Desktop (MSVC 2012) and ran "qmake qwt.pro"
Opened VS2012 x64 Native Tools Command Prompt and ran "nmake" and "nmake install"
Set QWT_ROOT = C:\qwt-6.1.0
Added C:\qwt-6.1.0\lib to PATH
Copied C:\qwt-6.1.0\plugins\designer\qwt_designer_plugin.dll to C:\Qt\Qt5.2.0\Tools\QtCreator\bin\plugins\designer
When I open Qt Creator and edit the UI then go to Tools->Form Editor->About Qt Designer Plugins I see "Cannot load library qwt_designer_plugin.dll:" but no error or reason.
I used Dependency Walker to check the Dll, and QtCreator.exe and all its dependencies are 32-bit whereas my build of qwt_designer_plugin.dll is 64-bit. I wondered if this was causing the problem so I:
Downloaded Qt5.2.0 from http://download.qt-project.org/official_releases/qt/5.2/5.2.0/qt-windows-opensource-5.2.0-msvc2012-x86-offline.exe and install into C:\Qt\Qt5.2.0-32
Unzipped Qwt into C:\qwt-6.1.0-32bit to create a fresh copy.
Opened Qt 5.2.0 32-bit for Desktop (MSVC 2012), cd into C:\qwt-6.1.0-32bit and "qmake qwt.pro"
Opened VS2012 x86 Native Tools Command Prompt and ran "nmake" and "nmake install"
Copied C:\qwt-6.1.0-32bit\designer\plugins\designer\qwt_designer_plugin.dll to C:\Qt\Qt5.2.0\Tools\QtCreator\bin\plugins\designer
This works fine and I can now see the plugin loaded correctly and add Qwt widgets in the UI designer.
This worked for me:
Step 1
I check what MSVC version the QtCreator in my Qt framework version was built with. E.g. QtCreator that comes with Qt_5.6.2 MSVC2015 (qt-opensource-windows-x86-msvc2015-5.6.2.exe) was built with MSVC 2013 (qt-opensource-windows-x86-msvc2013-5.6.2.exe).
Step 2
I install qt-opensource-windows-x86-msvc2013-5.6.2.exe and build Qwt(plugin) with that Qt version.
For comparison here is what happens when Qwt is built with Qt_5.6.2 MSVC2013 and Qt_5.6.2 MSVC2015:
Also here:
https://stackoverflow.com/a/20156419/3096593
Related
i have downloaded the vtk from source both the latest version 9.1.0 and the previous version
8.2.0,
configured and generate a project file with no error, built the source in visual studio and it was a success also installed it.
but when i run a simple example as SIMPLE as this one https://kitware.github.io/vtk-examples/site/Cxx/GeometricObjects/CylinderExample/
it crashes with
I also tried to set it up with QT but i also am getting a crash in QVTKOpenGLWidget.
It looks like whatever version I am installing whether its a stand alone or in QT i ant seem to make VTK run.
I am using and configuring VTK for visual studo 2019.
maybe because the 'DEBUG/RELEASE' building setting? here
if you use 'DEBUG' to build your code,try change it to 'RELEASE'.
When trying to compile in the "Winsock Control" component on Windows 10, I get this error:
mswinsck.ocx could not be loaded
Notably, I have installed VB6 SP6, and with SP6 it works great on Windows 8.1 and Windows 7, but it won't compile on Windows 10.
Also notably, the compiled .exe, when compiled from Win7/8, has no problem loading ws2_32.dll. It's just the compiling step that doesn't work on Win10.
Running Dependency Walker, depends.exe suggests mswinsck.ocx can't be loaded because it's depending on API-MS-WIN-CORE-SYNCH-L1-2-0.DLL and API-MS-WIN-CORE-PROFILE-L1-1-0.DLL and API-MS-WIN-CORE-PROCESSTHREADS-L1-1-0.DLL and a bunch of other DLLs with similar names (I think these DLLs have something to do with SysWOW64), which can't be found:
Does anyone know how to compile in "Winsock Control" in VB6 on Win10?
(Also notably, it seems the MSFlexGrid component is un-compilable on Win10 in a similar fashion, but this question is about the WinSock control, not MSFlexGrid).
EDIT: additional info: I have installed "VB6 Service Pack 6", VB version is "Version 9782 VBA retail 6.0.9782", and the version on the mswinsck.ocx file itself is 6.1.97.82 (and thanks to the comments, I know a newer one exists: 6.1.98.16)
I have run into this problem often on Windows 10 machines and resolved it by unregistering and re-registering each OCX using an elevated Command Prompt:
Open a Command Prompt window from the Start Menu by right-clicking it and choosing "Run as administrator". It is important that your Command Prompt window is titled "Administrator: Command Prompt".
Go to SysWOW64 folder by typing cd \Windows\SysWOW64
Unregister OCX by typing regsvr32 -u mswinsck.ocx
Re-register OCX by typing regsvr32 mswinsck.ocx
That usually fixes the problem.
If you use Visual Studio Installer 1.1 to deploy applications, you will probably have the same issue on Windows 10 systems you deploy to. The installer doesn't seem to properly register files. If you use Visual Studio 2019 and the Setup extension, that will build an installer that properly registers the OCX, in my experience.
I am new to NDK. Just upgraded to Android Studio 3.5.2, installed LLDB 3.1.4508709, NDK (Side by side) 21.0.6113669, CMake 3.6.4111459 (BTW, the interface is terrible) on Ubuntu 16.04.
Created a new Native C++ project from template.
Every time I open cpp file, there is a pink message on the top of the window:
Unable to execute Clang-Tidy: Cannot create property=Diagnostics for JavaBean=com.jetbrains.cidr.lang.daemon.clang.tidy.ClangTidyYamlLoader...
The message is too long to fit the window. It happens on Ubuntu only, on Mac the same IDE version works fine.
Everything else seems working ok - building, running/debugging on emulator. Just the message is quite annoying. Any ideas?
I am building a setup in VS2012 - installshield.
I have to upgrade the version of my application and create a new installer.
I changed the product version and update the version of my application and setup too. (they where 2.0.2.0 now are 2.0.3.0).
The installation works correctly and the updates seem to work (2.0.2.0 does not exist anymore and 2.0.3.0 is installed) but it happens that myapplication.exe after the msi is launched is erased!
Only if I run the msi another time in repair mode the .exe is added.
I would like that the installation will keep the exe without this boring second step.
I answer my own question.
I naively just forgot to set the compile mode from debug to release; so the compilation worked but I had this side effect.
I have a VS2012 sln which includes an install shield installer project.
If I build the solution/projects manually via solution explorer everything builds fine.
However when using the TFS build definitions i get the following error:
C:\Builds\1\<NAME>\<Build_Definition_Name>\Sources\InstallSetup\InstallSetup.isproj (29): The imported project
"C:\Program Files (x86)\MSBuild\InstallShield\2012SpringLimited\InstallShield.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
Can someone please help with this?
Info:
Using VS 2012
OS - Win 7 x64 Pro
You need to install InstallShield on the machine on which you are running the build.
In-case someone is facing the same issue, I was able to solve it by reading what Flexera mentioned on their website: Link
Brief description: in build definition, process tab, make sure the MSBuild Platform is targeting x86.
I too had 64bit Windows (8.1) running and Team Foundation Server 2013 Express.