It should be accesible from anywhere sf::Texture is... so.. everywhere, that's the problem.That's indeed the problem, your assumption is wrong ;)
You don't need it everywhere. You only need it in the part of your game which is responsible for the graphics, and in particular, sf::Texture. You don't need it for physics, audio, AI, or other game logic. So you can put your manager object in a class responsible for the graphics.Well yes, it 'should be acessible from few places in which I might need same textures'. So there are few locations one of these should be placed I can think of. I'm really struggling with structuring anything nicely in oop. ;D Apparently global singletons are bad so I'm avoiding them. Should I just let any group of classes that are likely to request same textures keep a pointer to their texture manager? Is that 'dependancy injection'?
Should I just let any group of classes that are likely to request same textures keep a pointer to their texture manager?Yes, that is a possibility.