SFML Problem

[Nisheeth]

@Stewbond:
Better than before.
Now it does show C:\ once before again, going back to
e:\program files\microsoft visual c++\bin>

So the whole is like this:

e:\program files\microsoft visual c++\bin>cd c:
C:\
e:\program files\microsoft visual c++\bin>

[anonymous23323124]

@Stewbond I still think use of SFML 2.0 is better if possible. Sure, there are differences, but they can be managed with a combination of the SFML 2.0 documentation (this, as opposed to tutorials, is on the site, though I recommend building it yourself with doxygen to get the latest version) and this thread which lists changes:
http://www.sfml-dev.org/forum/viewtopic.php?t=5343

@Nisheeth How about you just use the regular command prompt cmd.exe and run the following file before continuing the procedure:
visual_studio_install_directory/vc/bin/vcvars32.bat
where your Visual Studio install directory will be something like c:/program files (x86)/microsoft visual studio 10/, but you'll have to check to be sure.

If you have a pro version of VS, the file might be called vcvars64.bat.

Anyway, try this as the only difference AFAIK between command prompt and VStudio command prompt is that the second automatically runs this file.

[Nisheeth]

run the following file before continuing the procedure:
visual_studio_install_directory/vc/bin/vcvars32.bat

How do I run it through the command prompt?
Its been years since I used the command prompt for anything, and have forgotten everything.

Though I have another idea. I will move the sfml folder to the E drive and then try it out...

[anonymous23323124]

Just type the name of the file, e.g.

>c:/program files (x86)/microsoft visual studio 10/vc/bin/vcvars32.bat

(obviously '>' is the prompt; you don't type it...)

EDIT: Oh, and you might need to put it in quotes, I'm not sure. I can't really remember much about Windows' command prompt either now as I primarily use Linux.

[Nisheeth]

Thanks!! That worked. And I need to put it in quotes, else, it will declare that "c:/program" is not a recognized function or executable.

EDIT:
I did the building, and will try making the project.

[anonymous23323124]

And I need to put it in quotes, else, it will declare that "c:/program" is not a recognized function or executable.

Thought it might do that. Oh how much nicer Linux Mint's terminal is...

[Nisheeth]

You are great!!
I watched the tutorial about setting sfml up (I couldn't find a way to avoid doing the setup for every project) and its working perfectly!

I also have tutorials on how to make a first SFML project, but the video is out of date

Any links from where I should start learning SFML?

[anonymous23323124]

In Visual Studio, I think you have to do it every time. Although VS Pro let's you make your own template projects somehow, I think.

its working perfectly!

When I said out of date, I didn't actually mean it no longer works. However, I think it fails to mention static vs. dynamic linking of the C runtime, which might cause a few problem for some people if they don't know how to fix it. If you took my advice in the previous video, it should be fine though. The point is that if you linked the C runtime statically to the SFML binaries, you must link it statically to your own program and similarly for dynamic. But if you do the default dynamic link when building SFML (STATIC_STD_LIBS=FALSE) then everything should work by default.

Well I have one or two other videos on event and windowing. There's also one on images, but the problem is, it's no longer correct as Laurent changed the public interface for images and sprites significantly.

There's not much on SFML 2.0 around yet. I'd have to suggest you use the tutorials for 1.6 and when something doesn't work look at the documentation for SFML 2.0, and also this thread:
http://www.sfml-dev.org/forum/viewtopic.php?t=5343

Or just ask me. I'll be able to help at least some of the time ;) PM me here or post on my SFML Q & A
http://sfmlcoder.wordpress.com/help/q-a

[Nisheeth]

In Visual Studio, I think you have to do it every time. Although VS Pro let's you make your own template projects somehow, I think.

What I meant was setting up the include and Library directories. Your tutorial showed how to do that. OK then, I will start with the tutorial you have on youtube.
Thanks again!

[anonymous23323124]

Well in Visual Studio 2008, you can make that a global setting. in 2010, one must set search directories for every project. It's very annoying. Code::Blocks lets you set them globally and per project, it's much nicer.

Take care with my tutorials. Many of those actually are out of date, though in some cases you'll find updates in the information section. I've decided not to re-record them until SFML 2.0 has a stable public interface lest they just become outdated again.

[DSLq5Di1]

In VS 2010, create a new project (or open an existing one), view->property manager, under the debug or release folder, edit "microsoft.cpp.XX.user".. this property sheet is included in all projects, so any changes you make here will apply globally.