Skip to main content
gamedev.net
🔒 Locked

SDL on Linux

Started by RFLAGG Jun 27, 2004 at 2:57 PM 4 replies 1k views
Original Post
RFLAGG
RFLAGG
Okay, I decided to write an engine for a FPS in SDL so I could port it to OSX and windows easily. (running linux now) After spending a day working out the errors (I wrote about 3000 lines of code without testing to see if it would compile) when I linked it I got the error: /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/../../../../i486-slackware-linux/bin/ld: cannot find -latk-1.0 collect2: ld returned 1 exit status Anyone know how to fix this? I'm going to install windows later today and work on the windows port, because I couldn't fix this and I can't find anything on google except two pages, and they don't help me.
www.openwar.netwww.openwar.net/members/forums/
Monder
Monder
Well you're trying to link the atk-1.0 libary and it ain't in any of the linkers default libary directories. For it to work it needs to find the file libatk-1.0.a in one of the lib directories it uses (the location of which depends upon your system setup).
C-Junkie
C-Junkie
why are you trying to link atk? that's the accessability framework for gtk applications, and you don't (normally) use gtk with SDL...
RFLAGG
RFLAGG
hmm fixed it, thanks (lol when I saw latk I didn't see "lib" and "atk", just some weird word that looked like lake)
www.openwar.netwww.openwar.net/members/forums/
hogosha
hogosha
slacks install of kdev is horrible, uninstall it and install it fresh
Xori
Xori
In case you did not know, putting pkg-config atk --cflags --libs (those are backticks) on your gcc line will help you out there, as long as your pkg database is not malformed. Works for alot of other packages as well (do a pkg-config --list-all). It helps when moving code straight over to another machine which may have a different *nix or distribution so you do not have to figure out where the libraries are on every machine you build your code on.

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.

Sign in to reply to this topic.