Welcome, Guest. Please login or register. Did you miss your activation email?

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - bnz

Pages: [1] 2
1
Window / OpenGL context
« on: March 13, 2010, 10:44:20 pm »
Quote
What documentation? There is no documentation for SFML 2 yet :lol:

Oh, then "Documentation for SVN Version (next version)" is a bit misleading. =)

I'll try it out then.

Greetings,
bnz

2
Window / OpenGL context
« on: March 13, 2010, 10:29:36 pm »
Ah, cool.

I guess I'll have a look at SFML 2 then.
The documentation for SFML 2 does not seem to mention this possibilty - is it already implemented?

Greetings,
bnz

3
Window / OpenGL context
« on: March 13, 2010, 08:12:54 pm »
Hi,

is there a way to check what kind of OpenGL context was created by a sf::Window? And also, whether it's a compatibility or core profile?

Thanks,
bnz

4
General / Static Linking Errors
« on: January 30, 2010, 02:08:23 pm »
Quote
It is explained in the "getting started" tutorial.

It says so in the Code::Blocks tutorial - not in the VC++ one. ;)

Quote
But I think this is a different problem, the unresolved symbols are from the OS libraries, not from SFML. You'll probably have to recompile SFML with VS2010 to make it work.

Again?
If you recall this topic, I already did that. However this was on another computer (and maybe with beta1, not beta2 - EDIT: no, it was definetly beta2), so I'll give it another try.

Greetings,
bnz.

EDIT:

Well, now I tried to rebuild the library, using VC++ 2010 beta2 as I tried in the afore mentioned thread, and now VC++ 2010 beta2 says the following:

The german sentence means something like: "The system could not find the specified file."
Because of this error only four files are actually compiled.

I guess until you provide the proper builds for VC++ 2010 I won't be able to statically link to sfml.

Greetings,
bnz.

5
General / Static Linking Errors
« on: January 29, 2010, 11:30:10 pm »
I didn't even know the order in the linking list made any difference.
So now I'm linking in the following order:
sfml-window-s-d.lib;sfml-main-d.lib;sfml-graphics-s-d.lib;sfml-system-s-d.lib

However, this does not solve the problem.

Any other suggestions?

Thanks,
bnz.

6
General / Static Linking Errors
« on: January 29, 2010, 10:44:22 pm »
Since this topic covers exactly the same problem, I'm posting mine here.

I'm trying to link SFML statically, so my include list looks like this:
sfml-window-s-d.lib;sfml-system-s-d.lib;sfml-main-d.lib;sfml-graphics-s-d.lib

I don't define SFML_DYNAMIC.

However, when I compile (e.g. the tutorial code on event handling with windows), I get the linker errors like the following ones:
Code: [Select]
1>sfml-window-s-d.lib(VideoModeSupport.obj) : error LNK2019: unresolved external symbol __imp__EnumDisplaySettingsA@12 referenced in function "public: static void __cdecl sf::priv::VideoModeSupport::GetSupportedVideoModes(class std::vector<class sf::VideoMode,class std::allocator<class sf::VideoMode> > &)" (?GetSupportedVideoModes@VideoModeSupport@priv@sf@@SAXAAV?$vector@VVideoMode@sf@@V?$allocator@VVideoMode@sf@@@std@@@std@@@Z)
1>sfml-window-s-d.lib(WindowImplWin32.obj) : error LNK2019: unresolved external symbol __imp__ShowWindow@8 referenced in function "public: __thiscall sf::priv::WindowImplWin32::WindowImplWin32(void)" (??0WindowImplWin32@priv@sf@@QAE@XZ)

I'm using VC++ 2010 beta2.

I guess I'm missing something obvious here, so please give me a hint. =)

bnz

7
Window / Question on window tutorial
« on: January 24, 2010, 06:46:31 pm »
Quote
Renamed to what? They seem to have the right name, from the build log.

The only .lib files I could find in the directory you mentioned were called "sfml-xxx.lib". The suffix "-d" was missing, so I went ahead and added it. =)

bnz

8
Window / Question on window tutorial
« on: January 24, 2010, 06:16:37 pm »
Quote
But you should find the lib files in "C:\Users\bnz\Downloads\SFML-1.5-sdk-windows-vc2008\SFML-1.5\Temp\vc2008\sfml-network\Debug DLL", don't you?

Yes, I do.
For now, I simply renamed them to "sfml-xxx-d.lib", and it seems to work fine, finally. =)

Thanks for all your patience, help and of course for this great library! I just continued with the tutorial and I am stunned how easy things are!

I guess, when Visual Studio 2010 goes out of beta, you will provide precompiled files, as for VS 2008?

bnz

9
Window / Question on window tutorial
« on: January 24, 2010, 01:14:02 am »
So what would you suggest to do?
Is there another way to compile the library?

bnz

10
Window / Question on window tutorial
« on: January 24, 2010, 12:01:35 am »
I uploaded the new build log here.

For my taste there are too many fatal errors and warnings, but I don't know in how far this is "normal".

bnz

11
Window / Question on window tutorial
« on: January 23, 2010, 06:51:00 pm »


I changed the properties of every sfml project to the above, but it still doesn't produce the sfml-xxx-d.lib files.

bnz

12
Window / Question on window tutorial
« on: January 23, 2010, 06:32:45 pm »
Then I guess something went wrong during conversion, because  "Linker" -> "Advanced" -> "Import library" is empty.
The follwing picture shows the situation:


I don't know if this is of any help, but here is the Build-Log of the build with "Debug DLL" setting: BuildLog.txt

bnz

13
Window / Question on window tutorial
« on: January 23, 2010, 05:34:40 pm »
I think I'm getting closer.  :D
Quote
Debug dynamic produces sfml-xxx-d.lib (and .dll) files

With "Debug dynamic" you mean "Debug DLL", right?
Because, if so, it produces sfml-xxx-d.dll files and sfml-xxx-d.ilk files, not sfml-xxx-d.lib files.
Is there maybe a setting, which changes the file ending from .ilk to .lib (or can I simply do so by myself :) )?

bnz

14
Window / Question on window tutorial
« on: January 23, 2010, 03:14:36 pm »
Quote
To actually select the configuration to build, you should have a combobox in the toolbar.

So when I simply change select another build mode in the dropdown menu, framed red in the following picture, it should build the correct files?

Because I tried that. I built in "Debug", "Debug DLL", "Debug static", "Release", "Release DLL" and "Release static" mode and I still didn't get the "sfml-xxx-d.lib" files. The only -d.lib file I get, is "sfml-main-d.lib".

So just to make sure I'm doing everything correctly, I'm going to list the single steps:
  • Open SFML.sln located in \SFML-1.5-sdk-windows-vc2008\SFML-1.5\build\vc2008.
  • Converting the project with the Visual Studio Conversion Wizard
  • Deleting all files in \SFML-1.5-sdk-windows-vc2008\SFML-1.5\lib\vc2008, because that's the directory where the new files will be located
  • Choosing "Debug" from the combobox (red frame in picture above) and then Build->Build solution. This results in "sfml-xxx-s-d.lib" files being created in \SFML-1.5-sdk-windows-vc2008\SFML-1.5\lib\vc2008
  • Repeating last step with other build modes
Is it correct that "sfml-xxx-s-d.lib" files are created, when I only select "Debug" as build mode? Because when I afterward select "Debug static" as build mode, it says that the 6 files were already up-to-date.

bnz

15
Window / Question on window tutorial
« on: January 23, 2010, 01:04:40 pm »
Okay, but how can I create the "sfml-xxx-d.lib" files?
Here are some screenshots, that show all different configurations I tried:


And these are the resulting files:


(By the way: Can I delete the .ilk files? )
As you see, the "sfml-xxx-d.lib" files are missing.

Since this is the first library I have to compile by myself, please forgive my, if my questions are trivial. =)

bnz

Pages: [1] 2