Talk:Mac OS X Build Instructions

From Aleph One Wiki

Jump to: navigation, search

[edit] Descriptions

Would it be possible to get some small descriptions on what each of these are for? Understandably, the source is the code, and SDL is a required library, but the only other one I recognize is Lua. The best description I can come up with for Lua that it is a scripting language (partially?) embedded into Aleph One to allow for more complex mapping features. Thanks.  ;) MrHen 17:25, 3 December 2006 (CST)

Not sure I understand what you mean. Small description on what each of what are for? You mean like links to the library home pages? treellama 11:30, 4 December 2006 (CST)
What is Boost? What is it used for, why is it needed to Build Aleph One? A link to their home pages would work, I guess. The basic problem is this: I have no idea what Boost or Speex even are and only have a small knowledge of what Lua is. I am assuming that they are used by Aleph One in some regard or there would be no need to download them in order to build Aleph One.
From the Speex website: "Speex is an Open Source/Free Software patent-free audio compression format designed for speech." So it appears that Speex enables audio chatting in Aleph One. So all I would be looking for is a sentence like: "Speex enables audio chatting Aleph One." Nothing complicated. MrHen 11:55, 4 December 2006 (CST)
OK, maybe we should have a page separate from the OS X build instructions with those descriptions, since they apply to all sets of build instructions. I tend to think the web pages for all the libraries are self explanatory, and it doesn't really matter why they're needed if they're required for build. The optional ones might have a better description maybe treellama 12:01, 4 December 2006 (CST)
Sure, that works. Obviously, this is not extremely important, I just thought it would be helpful to the new guys like me. I like to know why I am downloading libraries I have never heard of.  :) A page that simply lists the libraries used by Aleph One would work. Adding a simple link at the beginning of the build instructions page would clear up all of the confusion. Again, this is not extremely important, so do not sweat it. I mostly put the comment there as a todo note for myself when I become more familiar with things. MrHen 13:08, 4 December 2006 (CST)