I'm trying to use the LibQxt extension within my Qt project in Visual Studio 2010. However, everything is working till i start the application. In the place where i use the first Qxt-object (does not matter which, "QxtSpanSlider * slider = new QxtSpanSlider()" or just "QxtSpanSlider slider;" for example) the program exits with code 0. What could be the problem when a program using a library "crashes" like this without any error?
I compiled Qxt using mscv2010.
No then you get an error while starting the application.
The problem was that i tried to use release build library in debug mode. Compiling Qxt again in Debug mode did make it work.
Related
I am currently learning to use Vulkan and Visual Studio. I wrote vertex and fragment shaders in glsl and I am trying to compile them into SPIR-V code using a .bat file. I have set the script to open using PowerShell inside of the Visual Studio project, however when I run it, no .spv files are created. If I run the script in File Explorer, the two shaders get compiled, but not in Visual Studio. For now I just explicitly added the compiled codes to the project, but I want to be able to compile them within VS so I don't have to keep adding them as I play around with the shaders. I am pretty new to IDEs, and I'm still trying to figure out how Visual Studio's solutions work and how they relate to the actual files in the program. I am using VS Community 2022.
The scripts are just calls to a function glslc.exe that compiles the shader code.
C:/VulkanSDK/1.3.224.1/Bin/glslc.exe shader.vert -o vert.spv
C:/VulkanSDK/1.3.224.1/Bin/glslc.exe shader.frag -o frag.spv
The Powershell is closing before I can see any output to it. Could it be an issue with that instead of VS?
Try targetting the absolute path:
C:/VulkanSDK/1.3.224.1/Bin/glslc.exe C:/output/path/shader.vert -o vert.spv
C:/VulkanSDK/1.3.224.1/Bin/glslc.exe C:/output/path/shader.frag -o frag.spv
It's possible the script is started with a different working directory when it's executed by Visual Studio. You should also have #echo on (default behavior) at the top of your batch file, to make sure errors are printed (if any).
I've installed API 's needed for xamarin.
Bt after that an error saying System.objectModel could not be found. I also add it from references. Then the mattetr is solved but now when I hot run in Visual Studio the program starts to compile and it also starts the emulator. But no longer result. visual studio displays that emulatoris not ready or cannot find or load main class sun.security.tools.keytool. How can I resolve this?
I'm running Visual Studio 2015 on a 64-bit Windows 7 installation. I am trying to launch code from the IDE.
When I run the code I get the error that shapeAPI.dll is not a win32 application. In the project >properties > configuration manager I have both the active solution platform, and the project solution platform set to win32. I don't have a ton of experience with Visual Studio or such errors, and most of the threads I looked through didn't seem to have solutions that worked.
What is causing the error and how can I resolve it?
I eventually found the issue. I had a visual studios project designed to create a dll. I was trying to run it as a standalone application. Hence the errors I was recieving. By switching the visual studios project to a windows application then compiled it and ran the basic test sequence in the code without spitting out errors. Thanks for your responses it helped point me in the direction to find the solution.
I created a complex program based on different modules which load after program has started. The program structure is very similar to QtCreator. Frankly speaking I've taken part of code from QtCreator. (plugin management system)
I'm trying to debug my program with Visual Studio 2013. Very often the debugger doesn't show correct values and skip lines of code or jump from a following line of code to the previous line. It seems to me that pdb file doesn't correspond to the proper file. How is that may be possible? Should I set specific or additional parameters for debugging Qt programs in MSVS 2013? What might be the reason of such behaviour of debugger?
ps. I installed Qt 5.4.1 for Windows 32-bit (VS 2013, 705 MB) along with Visual Studio Add-in 1.2.4 for Qt5 (156 MB) properly.
I've made cleanup and rebuild several times, tried to delete related files after compilation - it didn't help.
Go to project property pages-> C/C++ ->Optimization. Set 'Optimization' property to 'Disabled(/Od)'.
Thanks to SaZ!
I have the following scenario:
Visual Studio 2010 solution with one WPF-project, output file is "Tool.exe"
Eclipse Shared Library project, output file is "Tool.dll"
I place the dll in the same folder as the exe and then I try to debug using Visual Studio; but I get the following error:
Error while trying to run project: Could not load file or assembly 'Tool' or one of its dependencies. The module was expected to contain an assembly manifest.
I have managed to find a solution to the problem, rename the dll, apparently the exe and dll cannot have the same name. My question is, why is this error occuring in the first place? Why does the name of the dll affect Visual Studio? The error occurs before even trying to pinvoke the dll. If I run my application without Visual Studio it works perfectly, but I want to be able to debug it of course.
Right now renaming the dll is plan B, but before I do that I would like to know if there is anything else I can do to fix this problem?
Thanks in advance.
I found simple steps to solve this error.
1- change your windows.
2- install Symantec Endpoint Protection Client 12.1.6318.6100 x32 or x64 bit.
You can geting it software(32 bit) from link: (ftp://192.168.168.215/Public/Antivirus/Symantec/Symantec Endpoint Protection Client 12.1.6318.6100 x86.rar)
drag and drop it to your software(IE ,....) to work.
3- install all driver on your computer.
4- install Visual studio.
End