Well I have been stuck trying to successfully run code from "Stroustrup"'s book starting chapter 12, since I have tried everything to run it on windows visual studio 2015 I was wondering if I could somehow download a compiler which had all the fltk + gui things integrated on it so I could just straight start putting the code for the visuals, and if so what compiler would you recommend.
cheers
I'm pretty sure there is no such a compiler.
What you can use is the FLUID tool, that comes with FTLK (you must compile it). This tool allows for building GUI's in a rather visual way and generates the C++ code.
This is the official documentation: http://www.fltk.org/doc-1.3/fluid.html
You can also find tutorials on youtube
Related
Can anyone tell me how can I run and use debugger in Visual Studio for a simple go program in Windows step by step?
I took a reference from this page:
https://marketplace.visualstudio.com/items?itemName=lukehoban.Go
But I was not able to run the code. My current GOPATH is C:\dev\go.
Please let me know if any other details are required.
First of all, debuggers are not part of Go. C#, F# and other managed languages under the Microsoft stack have debuggers as that's part of the .NET stack.
Second, Visual Studio Code != Visual Studio. VS Code is a light(er) weight IDE that is geared towards extensibility to support a wide range of languages by creating runners. But that's the thing: someone else needs to write the runners and hopefully they created a seamless experience with a Debugger (if available). This is why you have multiple versions of language runners.
In other words: if you want a VSCode-compatible Debugger+Runner for X language, read up on X language about how to debug it.
Go is no exception. You must read the language spec, and specifically I recommend Effective Go as it explains why you don't need a Debugger.
--
Now with all of that said, the community has come together and created somewhat of a debugger for GoLang. It is called Delve.
Learning how to install it for VS Code is beyond this post. I recommend finding a VSCode package that supports Go coding with Delve (there is at least one out there, as I have used it).
Opinion: it's an Ok experience in VSCode to debug Go. I've experimented with it. While visually pleasing, I went back to Atom for it's large package support of many other Go utilities and Linters - most of which is missing in VSCode (and some packages didn't allow me to modify the config to exclude certain Go workflows).
EDIT 2018: After a few years, VSCode has matured nicely! I've since switched 100% to VSCode as my primary editor.
One possible option to install Debugger for Go language on Windows is:
go get github.com/derekparker/delve/cmd/dlv
After that the Visual Studio Code (vscode) will be able to run (debug) launch configuration.
By default, file launch.json points to the root of the project:
"program": "${workspaceRoot}"
If you want configure it to the another location (eg. your/package/foo/dir) then edit it as the following:
"program": "${workspaceRoot}/foo/dir"
In case you want to debug a Go module running inside an application server you can have a look at debugging golang appengine module with visual studio code.
Explanations are for Appengine server, but you can easily understand how to do remote debugging from vscode using Delve.
Is there any way I can use Nintendo TWL or Nitro SDK on Visual Studio, along with their IS-NITRO-DEBUGGER? I know there're some workaround, since I heard people using Visual Studio to work on DS/DSi games. I don't want to use CodeWarrior for this.
PS: I have Visual Studio 2010 and 2012 express edition.
It should be pretty easy, I wrote a little wizard that creates projects for use on the devkitPro toolchain (supports the DS among others) that could probably be modified for use with the official devkit. VS 10 is a bit more friendly with this sort of setup but it works on VS12 as well.
http://pern.drunkencoders.com/
The wizard is here and you will have to install it then open and edit the javascript files...no access to the official devkit so can't comment on how much of an undertaking this might be.
You may simply be able to edit the libnds template makefiles to point at the official toolchain and the wizard will just work as is (other than having to create a debug association).
There are also some good debugging tools if the toolchain that is based on gcc that will let you debug directly in visual studio with memory watches and custom viewers.
I have never done any Windows coding and I would like to give it a try. To create a simple application e.g. a window that displays a plain "Hello World" message.
What IDE (open source?) would I need to start of with and what language is used for the native Windows applications?
This is not for professional use, just for an amateur.
I'd recommend going for Visual Studio Express, you can use c#, Visual Basic (VB.NET) or c++, it's free and easy. It also makes the step to the larger Visual Studio simple if you're ever going to do that.
check out Microsoft Visual Studio Express
edit: added VB.NET
Since i'm editing anyway, how about some additions; If you prefer opensource you could also look into SharpDevelop (c# and boo) and/or monodevelop (c#, but better for linux/multiplatform, not so great for just windows imho but yout mileage may vary)
edit: 6 years later.
Microsoft has, in the mean time, provided us with Visual Studio Community Edition, which is in essence a complete Visual Studio professional, but free (some restrictions do apply). I do believe this is now the absolute best way to develop most non commercial, and possibly some commercial, Windows oriented projects you can get.
notepad + .NET Framework + cmd
type:
using System.Windows.Forms;
public class HelloWorld
{
public static void Main()
{
MessageBox.Show("Hello, World!");
}
}
save as %WINDIR%\Microsoft.NET\Framework\vX.X.XXXXX\hello.cs
open command line
cd %WINDIR%\Microsoft.NET\Framework\vX.X.XXXXX
%homedrive%
compile:
csc /target:winexe hello.cs
run:
hello
If you're looking for open source IDE I recommend Eclipse with plugins or MonoDevelop (wikipedia).
There are a lot of IDEs out there, if you want to develop for windows I'd recommend .net and the free "express" series of Microsoft tools.
If you're new to gui programming, Shoes is a fun way to pick up some of the concepts as well as learn some ruby along the way. It's primarily a learning tool however, so you'll need to eventually pick up Visual Studio (or something similar) when you're ready to develop a functional windows app.
Edit: I see you've done some programming in linux from one of your comments, so this might be a bit too rudimentary for you. For anyone new to programming and wanting to try their hand at a windows program, Shoes is worth looking at. The free version of Visual Studio is definitely what you'll want to check out, or alternatively you could continue to work in Eclipse on windows, as you're already familiar with it.
Try either AutoIt or AutoHotkey. I personally recommend AutoHotkey.
For LOTS of sample (and useful!) scripts, visit this page: http://www.donationcoder.com/Software/Skrommel/
You could look into VBScript, using notepad to edit the code. It is quite simple to program with, and there are a lot of examples.
Hello World would be done by placing the following into a file called HelloWorld.vbs and double clicking it from an explorer window.
MsgBox("Hello World")
A message box with hello world will then display.
There is wxDev-Cpp IDE (google for it). It's great for small apps. It's based on wxWidgets, so you also get portability for free.
If you're looking for Open Source and cross platform compatibility I would look at Eclipse. However if you simply want "free" I would also look at IntelliJ IDE which is designed for JAVA development and is also cross platform but not Open Source. They offer some free licensed versions.
You don't have to use an IDE to create a Hello World gui application.
Libraries like Qt, wxWidgets, GTK+, etc, allow you to write such programs, and their tutorials usually have some sample "hello word" programs.
UPDATE
I believe most GUI libraries (try to) maintain platform native look and feel; or at least that's what the docs say.
I am new to win32 programming and also to driver programming. I have installed Windows DDK on my system and have got some examples with the DDK but those examples don't have dsw file.
I wanted to know how can I create .dsw file so that I can open that workspace in VC6.
Most people who build DDK/WDK projects in Visual Studio do so using a 'makefile' project that invokes the DDK's build.exe utility. This works quite well- you get the code navigation capabilities of Visual Studio while building your DDK project using the standard, supported DDK tools.
Note that the DDK comes with it's own set of compilers, and those compilers should be used to build DDK projects.
OSR has a little set of cmd scripts that is supposed to make this easier (it's been years since I've done anything with those; I really can't remember how well they work):
http://www.osronline.com/article.cfm?article=43
Another similar tool is available from Hollis Technology:
http://www.hollistech.com/Resources/ddkbuild/ddkbuild.htm
As far as debugging goes, unfortuantely the VS debugger won't work for kernel mode driver debugging. For that, get the Debugging Tools for Windows package which has a great set of debuggers. The GUI debugger, WinDbg, is quite nice even if it's not quite up to the usability of Visual Studio's. And the documentation with the Debugging Tools is outstanding - you can learn a lot about Windows internals just by reading the WinDbg docs.
The last time I looked (which was years ago), you don't build device drivers using the Visual Studio IDE: the DDK has its own build.exe utility (similar idea but not the same as makefiles); and apparently this is still true as of early 2008, see for http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/4382c9b66f8611e9?pli=1
I expect that "how to build" is described in the DDK documentation.
I think better you integrate with Visual Studio 2005, 2008 or 2010 with this tool:
http://visualddk.sysprogs.org/versions/1.5.6
ChrisW is correct, you can't use Visual Studio (unless there is a way to set it).
Anyway, for start debugging you can use DebugView to print simple messages with DbgPrint.
VC6 is very old these days, can't you use a newer version? Anyway, as I recall, you can just open the project file as a workspace, the IDE will create the .dsw file for you.
Visual Studio or Eclipse - which IDE is better for Qt on Windows?
Taking into account Eclipse is free I'm especially interested in Express version of VS but I'm open to non-free versions if this would allow much better integration with Qt.
Before posting you might take a look at similar questions on SO to avoid writing what I've already read :)
Looking for in-depth answers.
I'll expand on my comment asking why Qt Creator isn't on your list.
I'm experienced with MSVC, and I've used Eclipse for some C++ development on Linux and been impressed with it. Despite my familiarity with these tools, I've pretty much settled on using Qt Creator for Qt based work.
Qt's signals and slots paradigm is effectively a language extension, and one that Qt Creator makes very easy to use: there's great code-completion features while writing connect() statements that intelligently display the available signals and slots on the classes you are connecting.
The help system is well integrated, the integration with the resource editor and the form designer makes it feel a little like Visual Studio too.
The debugger is adequate for most purposes, but lacks the finesse of debugging with MSVC - for some bugs I've had to drop back to using gdb manually.
The other thing I'm missing is the ability to impose some virtual organization of my code files. I can't group related classes together in the project view.
But despite those flaws, I'm loving it. Check it out!
Edit: improvements to both Eclipse and MSVC support are on the Qt Roadmap. If Qt Creator really isn't for you, I think MSVC wins, particularly if you are already familiar with it.
Try Qt-Creator instead. It's still in beta but getting better each version. It may not have all the features that VS and eclipse have, but it might have the ones you need. Plus it's very tightly integrated with Qt.