DLL Engines..

What? Why would you want to do that to a half-way-decent 3d engine?

Have you tried searching MSDN for "__declspec(dllexport)"?

I was looking at an article on this yesterday....
*searches history*

..Here we go

Marsupial Rodentia: you would want to do this for several reasons... e.g. if you have a D3D & an OGL renderer.. only one is going to be used at any given time, so you only need to load one DLL in instead of wasting memory with everything hardcoded for both APIs.

Saw that one.. it''s on here too.

My problem is I want to give the source to the DLLs out so people can make mods. I don''t want them to have access to the sorce for my basic commands (such as renderworld or sendnetmessage, cause it could be used to cheat online).

So I need someway to call hardcoded functions from a DLL... I was hopeing a tutorial would include info on how to do such things..

What quake does is during the initial loading of the DLL, it populates a structure of function pointers in the dll with the address of the actual function back in the main executable. When the DLL calls the function, it is doing it indirectly via the function pointers.

Tim

if you used a C++ class to "wrap" the engine, you could simply
export the class. This is probably the most clean way.



ill-lusion.com

ziggy@ill-lusion.com

Wrap??

One other problem is if I put OpenGL calls in a DLL it goes nuts!
Like 9000 errors (not of my doing. all in the gl.h files).