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.


Topics - Khatharr

Pages: [1]
1
General / Run SFML without a window for linux with no X11 installed
« on: March 06, 2023, 01:55:41 am »
Hello. I've used SFML in Windows to create a utility that will generate a png representation of some text data. The program does not create a window, since it's just rendering to an sf::RenderTexture and then getting the texture out of that and saving it to a file. I'm intending to use this on a Raspberry Pi 4 that's running OSMC (2022.03-1) in order to generate a background image for my media center.

I was able to install SFML and compile the program, but when I try to run the program I get the output:
Quote
Failed to open X11 display; make sure the DISPLAY environment variable is set correctly

X is not installed on this device, since the OS generates its own GUI. I'm wondering if there's something I can do to bypass the requirement for it, since SFML is not being required to draw to the screen. I'm fine with downloading the SFML source and making changes, but I'm not familiar enough with the situation to know where to start looking.

Any advice would be greatly appreciated.   :D

2
General / Stack corruption with static linkage
« on: April 06, 2015, 03:41:58 pm »
Hello.

I'm trying to get SFML 2.2 to link statically in VS2013.

I'm building in debug mode targeting x86.

I'm linking to the following libraries:
SFML:
sfml-main-d
sfml-system-s-d
sfml-network-s-d
sfml-audio-s-d
sfml-window-s-d
sfml-graphics-s-d

Misc Deps:
openal32
sndfile
freetype
glew
jpeg

OS:
ws2_32
opengl32
winmm
gdi32

I've done this with the binaries provided in the SFML 2.2 release and also with binaries I built locally by following the cmake tutorial.

I'm compiling and running the following code:
(click to show/hide)

When I run the project in the debugger, as I close it I get a notification from VS that the stack around 'window' is corrupted. Do I need to link different versions of the dependencies or is there some other problem that I'm missing here?

Pages: [1]