I am trying to get Tux Typing (http://www.geekcomix.com/dm/tuxtype/) to compile
in BeOS. However, when I compile, I get that it is missing the pthreads library.
Now I am using SDL, SDL_mixer, and SDL_image, and since I do not specifically
use pthreads in my app, I am assuming that pthreads is used in some varying
fashion by SDL/SDL_mixer/SDL_image (a ps under my linux box shows that when I
run the game there are 3 “tuxtype” processes, I am assuming this is due to
SDL_mixer).
Anyway, BeOS doesn’t have pthreads, and a question posed on the BeDev mailing
list a little while ago showed me a few projects which use work arounds in
their code. These work arounds don’t seem to really apply to me, as my code
does not use pthreads directly.
So, what do I do? Anyone encountered this problem and have a suggestion?
(Forgive me if this has already been hashed out before. I had to take aound 6
months off from subscribing to the list due to a contract I had with Intel, and
I may have missed the discussion…)–
Sam “Criswell” Hart <@Sam_Hart>
AIM, Yahoo!, MSN:
Homepage: http://www.geekcomix.com/snh/
I am trying to get Tux Typing (http://www.geekcomix.com/dm/tuxtype/) to compile
in BeOS. However, when I compile, I get that it is missing the pthreads library.
SDL doesn’t use pthreads on BeOS.
?
See ya,
-Sam Lantinga, Lead Programmer, Loki Entertainment Software
I am trying to get Tux Typing (http://www.geekcomix.com/dm/tuxtype/)
to compile
in BeOS. However, when I compile, I get that it is missing the
pthreads library.
Now I am using SDL, SDL_mixer, and SDL_image, and since I do not
specifically
use pthreads in my app, I am assuming that pthreads is used in some
varying
fashion by SDL/SDL_mixer/SDL_image (a ps under my linux box shows that
when I
run the game there are 3 “tuxtype” processes, I am assuming this is
due to
SDL_mixer).
Anyway, BeOS doesn’t have pthreads, and a question posed on the BeDev
mailing
list a little while ago showed me a few projects which use work
arounds in
their code. These work arounds don’t seem to really apply to me, as my
code
does not use pthreads directly.
So, what do I do? Anyone encountered this problem and have a
suggestion?
It seems to be a problem with “configure” and “makefile” it produces.
It looks like the -lpthreads is hidden somewhere in the makefile…
I also had a few other problems when trying to use the configure/
makefile route.
The good news is that I reied to build Tuxtype using a BeIDE project,
and this succeeded with no problems.
Sam, I’ll e-mail you the .proj file and game binary (to your e-mail
address) separately.
You should go ahead and add TuxType to BeBits now - it looks pretty
cool.
It seems to be a problem with “configure” and “makefile” it produces.
It looks like the -lpthreads is hidden somewhere in the makefile…
I also had a few other problems when trying to use the configure/
makefile route.
Actually, I use Kdevelop as my IDE, and I was just looking back over the SDL &
Kdevelop page:
On this page it says to add -lpthread in the ‘Additional Libraries’ text box.
That’s apparently what I did (probably a good year ago, when I first set it up).
Anyone have any reason why this document would say that? Is it correct, or
should I take it out?
The good news is that I reied to build Tuxtype using a BeIDE project,
and this succeeded with no problems.
Kewl!
Sam, I’ll e-mail you the .proj file and game binary (to your e-mail
address) separately.
You should go ahead and add TuxType to BeBits now - it looks pretty
cool.
On this page it says to add -lpthread in the ‘Additional Libraries’ text box.
That’s apparently what I did (probably a good year ago, when I first set it up).
Anyone have any reason why this document would say that? Is it correct, or
should I take it out?
Ahhhhhhh. This is for Linux. I didn’t know you could run Kdevelop on BeOS.
Anyway, I didn’t write the page and can’t update it, but use the output of
sdl-config --libs instead of hardcoding -lpthread in.
See ya!
-Sam Lantinga, Lead Programmer, Loki Entertainment Software
On this page it says to add -lpthread in the ‘Additional Libraries’ text box.
That’s apparently what I did (probably a good year ago, when I first set it up).
Anyone have any reason why this document would say that? Is it correct, or
should I take it out?
Ahhhhhhh. This is for Linux. I didn’t know you could run Kdevelop on BeOS.
