Some potentially "stupid" questions, but:
- Do the paths "/home/username/Documents/allegro-5.0.9/build/include" and "/home/username/Documents/allegro-5.0.9/build/lib" exist? (I assume in your actual file "username" is replaced with your actual user name.)
- Is there an "allegro5" subdirectory under "/home/username/Documents/allegro-5.0.9/build/include"?
- Is liballegro.so in your "/home/username/Documents/allegro-5.0.9/build/lib" directory?
No not stupid questions at all, since these are things I could have probably overlooked if you hadn't pointed them out.
1) Yes "username" is my username, not just username. Unless the Ubuntu file system works in a weird way I don't know, those two folders should be exactly correct. I can direct the terminal from the root folder using that address anyway. Also "build/include" and "build/lib" are the build folders for when I ran CMake on the Allegro 5 library.
2) There is an "allegro5" folder in that include directory, um... but I just realized that there is no "allegro.h" in it even though it exists in the "/home/username/Documents/allegro-5.0.9/include/allegro5" directory. I can only assume I either broke the CMake run or the make compilation for the library then... I was just following along what little tutorials I could find on the subject and hadn't really thought to check.
3) Yes, "liballegro.so" exists in that lib directory.
Um, I notice under the build lib directory where "liballegro.so" is there's a folder called "Headers" which pretty much looks exactly like the pre-build include folder. Is it possible I have to link to this or is there just something fundamental I'm not understanding here?
I know when you do straight command line compilation, this tutorial says you only need to do this:
$ g++ [source file(s)] -o [output] `pkg-config --libs allegro-5.0`.
But a) I don't completely understand this either (at least the `pkg-config --libs allegro-5.0`. which doesn't seem to point to any real file) and b) I don't know how to convert this into a CMake command.