Messages

1

General / Re: SFML 2.2 & Windows XP

« on: December 15, 2015, 05:37:39 pm »

Bump on this. Any luck, slotdev?

Running the window/win32 examples of Sfml 2.1 Visual C++ 10 (2010) - 32-bit works.
Running the window/win32 examples of Sfml 2.2 (or later) Visual C++ 10 (2010) - 32-bit fails partially:
Window example works (creating window and showing OpenGL), but win32 example (creating window and displaying moving textures) fails after loading window.
Same result when using csfml 2.1 vs later (via sfml.net).

Any ideas? I would really love not to have to attempt to install and attach a debugger on all this old crap i have to support.

System is 32bit xp with intel 82852/82855 GM/GME.

Thanks!

2

DotNet / Re: Definitive guide to SFML.NET on OSX

« on: February 19, 2015, 01:01:13 am »

This work is awesome! Thank you so much. I ported a rather large application using SFML 2.0.

Btw I noticed a difference in the way SFML behaves on OS X and Windows. Rendering an empty string (not null) crashes the process on OS X, but not on windows.

myl

3

C / Re: CSFML cmake broken?

« on: June 18, 2014, 12:33:55 pm »

Hey Laurent (and anybody else down with CSFML).

Bump. Anybody got any ideas why the C externs are missing?

myl

4

C / Re: CSFML cmake broken?

« on: June 10, 2014, 03:05:22 pm »

Ok, it turns out that the libcsfml-window.a i'm trying to link with is missing the C externs, and that is what is making mtouch complain.
nm command for iOS built libcsfml-window:
http://pastebin.com/Tzvv0uZA
Compared to OSX built libcsfml-window.dylib:
http://pastebin.com/73ajMtUN

I'm looking to get definitions like
T _sfWindow_createUnicode

Any ideas how to make CSFML build for iOS with the usual externs?

myl

5

C / Re: CSFML cmake broken?

« on: June 09, 2014, 10:15:33 am »

I've tried to merge  libcsfml-window, libsfml-window-s and libsfml-system.s together using libtool to see if the mtouch compiler likes it better to be fed a single lib instead of three, and then I got an interesting error:

libtool libsfml-system-s.a libsfml-window-s.a ../../../CSFMLiOS/lib/Release/libcsfml-window.a -o fatlibcsfml-window.a
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: warning for architecture: i386 same member name (Context.o) in output file used for input files: ../../../CSFMLiOS/lib/Release/libcsfml-window.a(Context.o) and: libsfml-window-s.a(Context.o) due to use of basename, truncation and blank padding
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: warning for architecture: i386 same member name (Joystick.o) in output file used for input files: libsfml-window-s.a(Joystick.o) and: ../../../CSFMLiOS/lib/Release/libcsfml-window.a(Joystick.o) due to use of basename, truncation and blank padding
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: warning for architecture: i386 same member name (Keyboard.o) in output file used for input files: libsfml-window-s.a(Keyboard.o) and: ../../../CSFMLiOS/lib/Release/libcsfml-window.a(Keyboard.o) due to use of basename, truncation and blank padding
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: warning for architecture: i386 same member name (Mouse.o) in output file used for input files: ../../../CSFMLiOS/lib/Release/libcsfml-window.a(Mouse.o) and: libsfml-window-s.a(Mouse.o) due to use of basename, truncation and blank padding
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: warning for architecture: i386 same member name (VideoMode.o) in output file used for input files: libsfml-window-s.a(VideoMode.o) and: ../../../CSFMLiOS/lib/Release/libcsfml-window.a(VideoMode.o) due to use of basename, truncation and blank padding
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: warning for architecture: i386 same member name (Window.o) in output file used for input files: libsfml-window-s.a(Window.o) and: ../../../CSFMLiOS/lib/Release/libcsfml-window.a(Window.o) due to use of basename, truncation and blank padding

So this would explain why mtouch linking fails if it's attempting something like this. What would be the best way to go about these naming clash issues? Is there perhaps a setting in CSFML XCode project that will allow me to include SFML in the CSFML libraries?

myl

6

C / Re: CSFML cmake broken?

« on: June 04, 2014, 04:55:53 pm »

This forum discussion seems like it could be helpful.

Thx Laurent. I'll look into it! Sorry for google proxying you

myl

7

C / Re: CSFML cmake broken?

« on: June 04, 2014, 03:45:48 pm »

I'm not sure, but I don't think -U is the same as -u. And why is it used in your project?

Hah, I was wondering the same, but haven't found a better match yet The compile options for clang++ are generated by mtouch, which is the xamarin mono compiler/linker.

8

C / Re: CSFML cmake broken?

« on: June 04, 2014, 03:23:01 pm »

From http://linux.die.net/man/1/clang:

-Umacroname
Adds an implicit #undef into the predefines buffer which is read before the source file is preprocessed.

9

C / Re: CSFML cmake broken?

« on: June 04, 2014, 02:59:51 pm »

Ok. I've tried to simplify things by only linking in libcsfml-window, libsfml-window-s and libsfml-system.s. These should work fine together by themselves, right?

To get through build errors I've also linked in QuartzCore.framework, CoreMotion.framework and OpenGLES.framework. I now get consistent errors when building for Simulator (i386) or when building for iOS device (armv7). It looks like one for every p invoke (41) in sfmlnet-window:
Undefined symbols for architecture armv7:
  "_sfJoystick_getAxisPosition", referenced from:
     -u command line option

(The above error says "for architecture i386" for simulator builds). Full build command and errors: http://pastebin.com/ZS3J5ZqN

I've verified the 3 linked in sfml libs are the correct archs (i386 or armv7) by using lipo like this:
xcrun -sdk iphoneos lipo -info CSFMLiOS/lib/Release/libcsfml-system.a
Architectures in the fat file: CSFMLiOS/lib/Release/libcsfml-system.a are: armv7 armv7s arm64

The funny thing is, if I build without linking in libsfml-window, I get errors like
Undefined symbols for architecture armv7:
  "sf::Mouse::getPosition(sf::Window const&)", referenced from:
      sfMouse_getPosition(sfWindow const*) in libcsfml-window.a(Mouse.o)

Meaning sfMouse_getPosition and the rest actually was located in libcsfml-window.

10

C / Re: CSFML cmake broken?

« on: June 03, 2014, 06:26:57 pm »

Since CSFML is a static library, it doesn't link anything. So you have to link CSFML and SFML in the final binary (SFML.Net).

Hmm. I'm confused. I thought CSFML was self-containing SFML? Why do I need to link SFML also then? Anyway, after also linking libsfml-window-s.a and libsfml-graphics-s.a, libfreetype.a and libjpeg.a with mtouch i get a GL related error.

Undefined symbols for architecture i386:
  "sf::ThreadLocal::setValue(void*)", referenced from:
      sf::priv::GlContext::globalInit() in libsfml-window-s.a(GlContext.o)
      sf::priv::GlContext::initialize() in libsfml-window-s.a(GlContext.o)
      sf::priv::GlContext::setActive(bool) in libsfml-window-s.a(GlContext.o)
      sf::priv::GlContext::ensureContext() in libsfml-window-s.a(GlContext.o)
      (anonymous namespace)::getInternalContext() in libsfml-window-s.a(GlContext.o)
      sf::priv::GlContext::create() in libsfml-window-s.a(GlContext.o)
      sf::priv::GlContext::create(sf::ContextSettings const&, sf::priv::WindowImpl const*, unsigned int) in libsfml-window-s.a(GlContext.o)

I've verified that OpenGLES.framework is linked in.

myl

11

C / Re: CSFML cmake broken?

« on: June 03, 2014, 03:57:11 pm »

Ok, I had time to get into this today. Looks promising, but I am kinda stuck, maybe Laurent or someone else with better understanding of the CSFML / SFML binding has any ideas?

I'm debugging on the iOS Simulator to start off, so I have built SFML statically with the IOS 7.1 SDK and i386 architecture.  On top of that I've built CSFML from those libraries also against IOS 7.1 SDK and i386 architecture.

When mtouch is compiling my SFML.Net library natively it throws errors like this for every p invoke:

Undefined symbols for architecture i386:
  "sf::CircleShape::setPointCount(unsigned int)", referenced from:
      sfCircleShape_setPointCount(sfCircleShape*, unsigned int) in libcsfml-graphics.a(CircleShape.o)

So it seems that it links with CSFML fine enough, but can't link the C++ function underneath. What could I be missing?

myl

12

DotNet / Re: System.AccessViolation

« on: May 27, 2014, 02:31:04 pm »

Update: The last remaining AccessViolations dissappeared after I started using another texture constructor:

https://github.com/SFML/SFML.Net/pull/60

myl

Merged in master.

13

C / Re: CSFML cmake broken?

« on: May 27, 2014, 02:25:55 pm »

Unless you are referring to the blending issue?

Myl

14

C / Re: CSFML cmake broken?

« on: May 27, 2014, 02:24:54 pm »

Hey AbelToy.

I haven't had a chance to follow up on this, but I will do it sometime this week

myl

15

General discussions / Re: SFML 3 - What is your vision?

« on: May 26, 2014, 11:46:28 pm »

Maybe it's time to introduce the SFML Video module? I'm not even sure it would be that much work if based on ffmpeg

Shouldn't video playback be a basic component of a Simple and Fast Multimedia Library ?

myl