I have to develop something in Linux(CentOS 6.5) Environment using C or C++ language with many of libraries for linux.
As you know, CentOS is not GUI. So, I want to use Microsoft Visual Studio for my work. It's OK even if use just VS as the Editor.
I mean that I like the features of IDE visual studio(intellisense, debugger, and so on).
I have Visual Studio 2008, 2010, 2013 Professional.
yes you can, in fact, if you have setup a VM machine, you can even directly include the C++ include library of Linux (However, this only works for write code, not work with compiling). You could also setup CYGWIN or MINGW for referencing the header of Linux platform.
In fact, for myself, I switched to QtCreator as a cross platform C++ IDE, it also has auto-complete and debug features.
Related
Is there any way i can install visual studio on linux?
Already tried installing it. Rider is too expensive for my needs and I want to upgrade from Window to Linux. Distro: Garuda
I don't think you can run it natively. Perhaps there's a workaround by using a Windows virtual machine inside your Linux distro and then using Visual Studio in the VM.
A quick google yielded these alternatives that are Linux compatible, but as you can read by the comments under each listing, it depends on your use case. See if any of these will work for you: https://alternativeto.net/software/jetbrains-rider/
Visual Studio Code (interactive text editor) runs pretty fine. Although you will need several extensions for languages like C# to compile. There is also a gtk# language implementation with MonoDevelop (C# native implementation for linux), but its development was freezed.
I plan to develop several programs using Rust programming language which will be deployed on the computer of several colleagues using Windows 10 (64 bits). According to what I understand by reading the online installation guide, in order to install Rust develoment environment on Windows, the installation of Microsoft Visual Studio C++ Build tools is a prerequisite.
My question is: Once a program has been compiled and the executable has been created and deployed on the computer of my colleagues, do they also need to have Microsoft Visual Studio C++ Build tools installed on their computers in order to be able to use these programs or this is just a prerequisite for develoment?
The build tools should not be necessary on the target machine, but that machine probably needs the redistributable C++ runtime unless you force statically linking the CRT.
https://stackoverflow.com/a/44387312/8182118
What is the requirements for running a Rust compiled program on another Windows machine?
I have developed Visual C++ 2008 code that runs in Windows. I have made it cross platform also so that it runs under Linux.
I am greatly concerned about distributing source code and even just libraries that Linux users can link to.
I have used CMake and Code::Blocks (only in Linux) but it was still developed using Visual Studio 2008 for most development.
The license looked similar for the professional version and the express version. Let me know if binaries can be released to run under Linux and also if it is okay to open source the entire project. I am pretty far into this project. Maybe it should have been done entirely in Linux.
I am also interested to jump to another Windows compiler such as MinGW in addition because of the Visual Studio licensing restrictions. Is this the path that cross platform programs are usually created or can they be created primarily with the professional or express Visual Studio compilers?
Disclaimer: I am a total beginner to Visual Basic but code a bit in python and Drupal
I need to compile this C++ app (http://sourceforge.net/scm/?type=git&group_id=227253). I succesfully cloned from git, but how do I compile it (get the .exe) in Visual Basic 2008 or 2010 Express?
I have tried this:
1. Open Visual Basic 2008 Express, File, New, Windows Form Application (naive assumption, which should I choose?)
2. Dragged the contents of the git clone into the Solution Explorer Window (which Adds files)
3. Click Build menu
After that I'm lost. Any help is appreciated! This project uses cmake if that helps.
You need Visual C++, not Visual Basic. They are separate languages.
You cannot compile a C++ program in Visual Basic 2008 Express.
You must download Visual C++. Or purchase Visual Studio 2010 Pro (which includes all of VB, C++, C# and the web tools).
If you've got the bandwidth, I'd encourage you to get this .iso:
http://www.microsoft.com/visualstudio/en-us/products/2010-editions/express-iso
If you're interested in the "bleeding edge", MSVS 2011 beta is available here:
http://www.microsoft.com/visualstudio/11/en-us/downloads
Otherwise, if you just want to compile some C+ code on a Microsoft Visual Studio compiler, get this:
http://www.microsoft.com/visualstudio/en-us/products/2010-editions/visual-cpp-express
First of all, I want to ask if Clang compiler is better than MSVC's default compiler? And how can I use Clang with MSVC? For example, I write code in MSVC then when I hit Build, it call Clang to build the project.
https://github.com/ishani/ClangVSx
AddIn for Visual Studio 2010 that allows use of the Clang C/C++ compiler in place of MSVC++. Translates VC project and build settings into gcc-friendly command line arguments, along with existing platform tools (MSVC Linker, Librarian, RC) to complete the build chain.
Using clang compiler on Windows is still considered to be in experimental state. However, some progress has been made recently. As I answered similar question:
LLVM provides Windows snapshot builds - a clang toolset for Visual Studio as Windows installer. Currently it should integrate with Visual Studio 2010, 2012 and 2013. More information can be found on LLVM's blog post A path forward for an LLVM toolchain on Windows.
You can use a "makefile project" to have Visual Studio invoke a makefile (or any command-line process) when you tell it to build.
I've done this before to get MSVC's nice source navigation for non-Windows embedded projects.
The drawback is that you have to manually keep the makefile in sync with the files in the project (or vice-versa depending on how you want to look at it) - generally not a huge problem.