SFML in Netbeans

[Laurent]

for me it was te easiest way.

Which doesn't mean the cleanest
And it's always good to know how to use the IDE, rather than finding workarounds. SFML is most likely not the only library that these guys will use with NetBeans.

[Travnick]

Which doesn't mean the cleanest

If u know how to do that on windows i will be grateful, because i had always had problems with it ;] My solution was install every lib into the Cygwin, or MinGW directories. On linux is the same, all libs are in one directory

[Laurent]

On Windows it depends on what IDE you use.

On Linux, all libraries are installed at the same place (/usr) because they are installed by the package manager. If you install libraries manually you won't put them in /usr; at least in /usr/local or even in /home/dev/libs/whatever.

[Travnick]

but as far as I know main place for non default things is /usr/local

[Laurent]

Yep, but this is still not the compiler's install directory. It's a shared place for libraries.

Anyway, don't try to compare, Windows behaves totally differently (= it sucks) with shared libraries.

[Silvah]

Anyway, don't try to compare, Windows behaves totally differently (= it sucks) with shared libraries.

Could you explain why do you think that the way Windows handles shared libraries suck?

[Laurent]

Simple, Windows doesn't handle shared libraries at all.

There's no standard way of installing one, there's no shared location to put them, there's no way to handle several versions of the same library properly, no way to manage dependencies between libraries, etc.

[Silvah]

There's no standard way of installing one, there's no shared location to put them, there's no way to handle several versions of the same library properly, no way to manage dependencies between libraries, etc.

There is, there is, there is, I think there is but I don't know if I understood correctly.

People just don't know that Windows actually handles shared libraries well, they love repeating old myths without checking whether they're true in the first place. These issues were fixed in Windows XP by introduction of side-by-side assemblies, people just don't realize that the problems don't exist anymore.

[Laurent]

Really? I'd be glad to know more about that. Can you explain how Windows XP solves all these problems?

[Silvah]

It's very well explained on MSDN, I don't think I could do any better

[Laurent]

That's a lot to read, I'll try to find some free time to read it all

But is it really used anyway? I've never seen any software library providing side-by-side assemblies, or handling anything at all related to versioning on Windows.

[Silvah]

But is it really used anyway?

In Vista and
7, it's widely used internally...

I've never seen any software library providing side-by-side assemblies, or handling anything at all related to versioning on Windows.

...but most third-party programs don't use this, since most programmers don't even know that such thing exists. Visual Studio 2005 and 2008 runtime libraries use SxS, though, so even the programs that don't otherwise care about SxS have to include the manifest file when compiled by these tools.

[Niall]

So if I move the include folder into C:\cygwin\usr\include I can get it showing up in the suggestions for '#include <>'. I moved the lib folder into C:\cygwin\lib\SFML\ but what does this change my command line options to? Still getting nonspecific errors to do with not being able to find -lsfml-system ):

[Travnick]

try selecting your libs manually in project settings

(project)->properties->build->linker->libraries->add library file

[Niall]

I've been doing that the whole time, as well as using the -L... stuff. Is it one or the other?