Jump to content

  • Log In with Google      Sign In   
  • Create Account


Engines, wrappers, and libraries


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
2 replies to this topic

#1 RellekWVU   Members   -  Reputation: 107

Like
0Likes
Like

Posted 13 May 2012 - 02:02 AM

I am a seasoned programmer and have recently decided to put my skills to use in game development. I have done a good amount of research but I am having trouble disseminating the difference between a game engine, a wrapper for say OpenGL or DirectX, and libraries. How does it all fit together? Any input, even just definitions (in regards to game dev) would be awesome!

Regards,

Rellek

Sponsor:

#2 haegarr   Crossbones+   -  Reputation: 4107

Like
0Likes
Like

Posted 13 May 2012 - 03:28 AM

A game engine is a piece of software that supports the implementation of a more or less specific kind of game. Having an engine means that you have a framework that allows you to build the actual games on top of it with noticeable less effort. The amount of functionality of a game engine is not defined; it may cover really anything a game is dealing with.

A library is a collection of related stuff. Especially software libraries are a collection of software functions. Software libraries may be linked to a software program statically or dynamically (and then usually are called DLLs ("dynamically linked library" or SOs "shared object"). A related description of how and when to invoke which function, including any necessary structure, is called an API ("application programming interface").

Now, OpenGL is a graphics programming environment. Strictly speaking it is just an API. Implementations of this API are numerous. However, in real life often the belonging libraries are meant when saying "OpenGL".

A wrapper in this context is a piece of software that gives the wrapped piece of software another API. This is usually done to hide implementation specifics of a library from a framework, enabling to easily switch to another library without altering the framework itself. E.g. a wrapper around OpenGL and a wrapper around Direct3D may be written to yield in an own single API for both, so that an engine can deal with any of these graphics using just that single API.

#3 incertia   Crossbones+   -  Reputation: 777

Like
0Likes
Like

Posted 13 May 2012 - 08:53 AM

A game engine is pretty much defined to be a layer of code that a game runs off of. It will usually consist of multiple smaller modules, such as a renderer or an input system. A wrapper is usually just a set of functions that make things easier. Say you had to call around 10 functions from a library to do a certain task. You could write a function, pass in all the variables you need, and have one function do that task for you. That is the general idea behind a wrapper, just with more functions around more components of a library.

A library is usually just a large collection of code. They are usually found in DLLs and may be linked to dynamically for functions a programmer doesn't feel like writing. Suppose somebody wrote a system of 3+1d vectors for homogenous coordinates and doesn't want to replicate the entire set of functions in all his future programs. He can export those functions inside a DLL so they become a library of functions. You just look inside the library for what you want, and use it.

Strictly speaking, OpenGL and DirectX are APIs/application programming interfaces. They are just a set of libraries that provide lower level code that will get the job done, and nothing more. This is also a reason for creating wrappers and engines. They will usually hide the lower level DirectX/OpenGL code and make things easier for the dev and allow for more readable code.
what




Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS