I've looked around on Google for tutorials on setting up SDL with it. The problem is that all the tutorials for linking to SDL with Code::Blocks is with the Mingw compiler, and never with VC++ 2008 Compiler.
I have the SDL for VS downloaded at C:\SDL. The problem is, I can't get it to work with Code::Blocks.
What do I need to do? I tried following the tutorials for Mingw but they don't seem to work.
This tutorial covers setting up SDL to work with Visual Studio .NET. I followed along with Visual Studio 2008 and found it fairly intuitive:
http://pgdc.purdue.org/sdltutorial/sdl_setup.html (broken link)
As the person who commented on your question implied, more information would be useful.
Related
I want develop Win32 and DirectX in Visual Studio Code.
I already installed gcc, mingw.
OS is windows10.
How do I setting it?
See Microsoft Docs for details on developing C++ code with VS Code.
The latest DirectX headers and link libraries are found in the Windows 10 SDK. Using the Visual C++ or clang/LLVM for Windows toolsets are the best options for consuming the latest Windows 10 SDK.
You may find the DirectX Tool Kit a useful starting point, although my tutorials focus on the Visual Studio MSBuild build environment. I also reference using CMake. You can use MSBuild through Visual Studio Community, and you can use CMake through either VS Community or VS Code.
i have downloaded CEF binaries from the link http://opensource.spotify.com/cefbuilds/index.html as successfully created a .sln file using VS 2017.
But now our requirement is to compile the cef binaries on windows through MinGW or through command line(Do not want to use Microsoft visual studio).
can someone helpme out with this thing?
Only Visual Studio is officially supported to build CEF on Windows. You'll unlikely be successful to make a different compiler work in a reasonable time.
There is also ways to compile a VS project via the command line. Example: msbuild project.sln /Flags... For more details have a look at this stackoverflow link
If you ever want to compile libcef (Chromium) for Windows, the whole build is entirely command-line only despite using the Visual Studio compiler.
There is a free edition of Visual Studio called Visual Studio Community (used to be Visual Studio Express):
https://www.visualstudio.com/vs/community/
Also, if you are a small company, you might want to check out Microsoft's Action Pack for 400 EUR/year which includes 3 Visual Studio Prof. subscriptions.
Have a look at the CEF wiki:
https://bitbucket.org/chromiumembedded/cef/wiki/MasterBuildQuickStart.md
I do not have enough points to comment on Eugen. Maybe someone can edit.
I think Eugen is right, and VS is a must. I suggest flowing also this link to learn how to build CEF programmatically and on different OS.
I generate a Visual Studio 2013 solution using CMake 3.0.2. When compiled it gives errors similar to this:
MSVCP110D.dll and Visual Studio 2013
I can't get my head around this, the toolset is v120 so why does it link v110 libraries? I've asked in the CMake IRC channel but they can't help me. It's impossible to debug the program because the redistributable does not include debugging dlls.
Edit: This is an Ogre3D application that i derived from the tutorials cmake zip. I've barely touched the CMakeLists.txt, only set REQUIRED for finding boost and added boost-system to libraries that are copied during install.
I found the solution regarding the Ogre3D-specific issues with this. The latest prebuilt 1.9 package was compiled with VS11 (2012) so that's why the .dll is missing, since I use VS12 (2013) as IDE.
The solution is to build Ogre3D from source, as is explained in depth here: http://www.ogre3d.org/tikiwiki/Building+Ogre
Remember to update your OGRE_HOME environment variable to point at the sdk folder inside the build.
Hope this helps other lost souls!
i'm trying to port to Windows a C project wrote to work on Linux. It's a simple project that depends CUDA and Glib librarys.
I believe the best way is to compile with Microsoft Visual Studio 2010, but i don't have idea how to link Glib to this project. CUDA code is going well, but every call to Glib methods generate a "unresolved external symbol" error.
i just solved my problem using this guide to configure GTK on Visual Studio 2008:
http://www.etechplanet.com/blog/visual-studio-2008-configuration-for-gtk2b-gui-development.aspx
The only change i done was about the Tools/Options/VC++ Directories because this was deprecated on VS2010. I added the paths directly to the project properties.
I built OpenCV from CMake to work with QT in prior months. I now want to also develop in Visual Studio 2010. Can I use this same installation, or do I need to have 2 opencv installations for this to work?
Since your question isn't quite clear, I'm going to make an assumption that you compiled OpenCV with Qt support. It should be noted that Qt support has nothing to do with whether or not you compiled it to work with Qt Creator for example. This Qt support enhances the highgui API (e.g., imshow etc...).
If you set your OpenCV build target to be MinGW based, then yes, you will have to recompile OpenCV.
If, on the other hand, you set the build target to Visual Studio 2010 based, then no the OpenCV build should work fine with Visual Studio.
Hope that is helpful!