Help installing THOR and SFGUI.

[greenk]

Hi there,
I'm having trouble getting the thor and sfgui libraries to work. I'm using latest versions of SFML and both libraries. Xcode recognises that these libraries exist (autocomplete works), but whenever I try and compile a project I get the message:

>> Undefined symbols for architecture i386:

I think I must have done something wrong during installation. I ran cmake on both libraries with settings copied from their respective tutorials. I then dragged the .o and src files to usr/local/lib and the headers to usr/local/include.

Can anyone guide me through the installation, or link me information to help demystify the process?
Please be patient if I forgot to mention something.

[Nexus]

Concerning Thor, have you read the tutorial? You should probably install the libraries, not just copy the files.

But I don't have an OSX system to test Thor, so it may be that some things don't work immediately. As far as I know, there are a few other people using Thor on OSX, so you might want to search a bit...

Concerning SFGUI, things look probably similar, but there are other people who are definitely more familiar with it

[greenk]

Thank you for your response.

>> Concerning Thor, have you read the tutorial?
>> You should probably install the libraries, not just copy the files.

I followed the tutorial but it didn't work: xcode could not recognise the #includes until I dragged the files in manually. I don't really know where to begin because the entire process feels like black magic to me: calling out incantations found on internet tutorials and hoping. Is there a straightforward way of installing c++ libraries that 'just works'?

[Jesper Juhl]

... I don't really know where to begin because the entire process feels like black magic to me: calling out incantations found on internet tutorials and hoping. Is there a straightforward way of installing c++ libraries that 'just works'?

It is by no means "black magic". It is actually quite simple. Let me try to explain:

First you get the source code; either by simply cloning the git repository or by extracting some archive file (zip file, tar+gz file or whatever).
Then you use cmake (with appropriate options) to generate build files (nmake files, make files, Visual Studio Project files or whatever) that suit your environment/compiler.
Then you use your native build tools to build the library according to the files cmake just generated for you.
Once the library is compiled, you install it - again using your native toolchain in combination with the build files that cmake already generated.
Then you use the library.

On a Linux system, the above is usually as simple as:
git clone (or "git pull" if you already have a clone)
cmake
make
sudo make install

Takes all of 5minutes - how much easier do you want it?
The official tutorials even explain it in great detail (much more than I do here).

[Hiura]

I then dragged the .o and src files to usr/local/lib

I can only strongly suggest you read very carefully the different official tutorial. It's completely wrong, sorry.

If you have a specific question about the tutorial, please ask.

[Strelok]

It's always amusing when people using apple software expect to be hand held through every single thing, even with a tutorial Dark magic

[greenk]

It is by no means "black magic". It is actually quite simple. Let me try to explain:

First you get the source code; either by simply cloning the git repository or by extracting some archive file (zip file, tar+gz file or whatever).
Then you use cmake (with appropriate options) to generate build files (nmake files, make files, Visual Studio Project files or whatever) that suit your environment/compiler.
Then you use your native build tools to build the library according to the files cmake just generated for you.
Once the library is compiled, you install it - again using your native toolchain in combination with the build files that cmake already generated.
Then you use the library.

On a Linux system, the above is usually as simple as:
git clone (or "git pull" if you already have a clone)
cmake
make
sudo make install

Takes all of 5minutes - how much easier do you want it?
The official tutorials even explain it in great detail (much more than I do here).

Do you speak mandarin? It really is quite simple. Why, even millions of little children can do it.
Seriously though, I did as you say yet still get the following error:
>> Undefined symbols for architecture i386:

I will repeat the steps I took:
1) downloaded the source from github
2) used cmake to build files
3) went into repository and 'sudo make install'

Where did I err? For those who linked to the SFML tutorial: I already have SFML installed, I am trying to install other libraries. Thanks for helping.

[Laurent]

>> Undefined symbols for architecture i386:

It would certainly help to see the list of undefined symbols (should be right below in your compiler output).

I ran cmake on both libraries with settings copied from their respective tutorials. I then dragged the .o and src files to usr/local/lib and the headers to usr/local/include.

I'm pretty sure that the OS X tutorial for SFML explains a totally different way of installing it. Because this one is wrong

[greenk]

It would certainly help to see the list of undefined symbols (should be right below in your compiler output).

Is this what you were referring to?

Undefined symbols for architecture i386:
  "thor::Timer::start()", referenced from:
      _main in main.o
  "thor::Timer::Timer()", referenced from:
      _main in main.o
  "thor::Timer::~Timer()", referenced from:
      _main in main.o
ld: symbol(s) not found for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)

I'm pretty sure that the OS X tutorial for SFML explains a totally different way of installing it. Because this one is wrong

Again, I am not installing SFML (see previous post).

Does anyone have any suggestions?

[Nexus]

Again, I am not installing SFML (see previous post).

This is equally wrong for any library. You cannot link to source or object files*.

How are you linking Thor? Are you really sure that you follow every step in the tutorial?


_______
* Of course object files generated from the source are combined in the linker step. But that's not the way to use external libraries.

[Laurent]

Again, I am not installing SFML (see previous post).

Ah, sorry. I confused SFML and SGFUI.

[greenk]

Again, thanks to everybody for trying to help me out.

This is equally wrong for any library. You cannot link to source or object files*.

Heh?

How are you linking Thor? Are you really sure that you follow every step in the tutorial?

From my previous post:
1) downloaded the source from github
2) used cmake to build files
3) went into repository and typed 'sudo make install' into terminal

It's very frustrating when posters (above) say:

It is actually quite simple.. use your native build tools to build the library according to the files cmake just generated for you.
Once the library is compiled, you install it - again using your native toolchain in combination with the build files that cmake already generate

You kind of skipped a few steps there mate. "Again using your native toolchain".. what?

You explanation assumes way too much. As I have posted repeatedly, I don't understand how this whole process works. Can someone walk me through this step-by-step? And yes, I have read the tutorial. I know how to search google. I would not be asking if I hadn't put considerable effort into making this work myself first.

[Laurent]

From my previous post:
1) downloaded the source from github
2) used cmake to build files
3) went into repository and typed 'sudo make install' into terminal

That's how you compiled and installed it. We're asking you how you link it to your own project.

You explanation assumes way too much. As I have posted repeatedly, I don't understand how this whole process works.

Some good reading about compilation / linking steps (from a general point of view, then specifically for your development tools) may be worth it

[Jesper Juhl]

I'll try to find the time to write a better explanation later tonight.

[Nexus]

I asked because it looks like you just forgot a -l flag or chose the wrong one. Thus again, how are you linking Thor? This is explained on the website, but since you don't mention the link step and instead talk about dragging .o files around, we have to assume you did not link the library correctly. And yes, reading about the C++ compilation and linking model in general would definitely be a good idea

Jesper Juhl, I don't know whether that's worth the effort, since the tutorial says already everything... and if it doesn't, you should rather point out where it could be improved, so that we can help also in other cases