DLL file
What do you mean by "files made with Irrlicht"?
If you mean code written that is using the Irrlicht Graphic Engine then yes, the project could be made to be a DLL file though you would still need the Irrlicht DLL (if you do dynamic linking).
A little advice: When asking questions you have the best chance of getting the right answer by being as much specific as possible or give as much details as you can about your problem so we would know exactly what's the problem and find the best solution.
If you mean code written that is using the Irrlicht Graphic Engine then yes, the project could be made to be a DLL file though you would still need the Irrlicht DLL (if you do dynamic linking).
A little advice: When asking questions you have the best chance of getting the right answer by being as much specific as possible or give as much details as you can about your problem so we would know exactly what's the problem and find the best solution.
Dev State: Abandoned (For now..)
Requirements Analysis Doc: ~87%
UML: ~0.5%
Cool i actualy made my engine be able to use the same stuff. Thereu can programm the Game/Application without linking to anything(really noob friendly) then just drop the dll onto theexe and the game/application runs. Of course there is support for the traditional way of linking the gameengine and compiling the gamecode into a exe. but to answer your question of course this is possible!
We're programmers. Programmers are, in their hearts, architects, and the first thing they want to do when they get to a site is to bulldoze the place flat and build something grand. We're not excited by renovation:tinkering,improving,planting flower beds.
- Reduce compile times,
- Modify parts of the engine without recompiling the whole (think about how many updates are done to a 3D engine in its life. saves brandwidth somewhere),
- Expose parts of the engine to C++ mod developers, without scripting language.
- Keep projects small, easyer to maintain and develop.
There are many more advantages. One sure thing, 3D apps are quite large : smaller modular parts enhance the architecture of the application.
- Modify parts of the engine without recompiling the whole (think about how many updates are done to a 3D engine in its life. saves brandwidth somewhere),
- Expose parts of the engine to C++ mod developers, without scripting language.
- Keep projects small, easyer to maintain and develop.
There are many more advantages. One sure thing, 3D apps are quite large : smaller modular parts enhance the architecture of the application.
Sorry maybe I did not really get your points, but all you said are quite true for any exe/dll distribution.Katsankat wrote:- Reduce compile times,
- Modify parts of the engine without recompiling the whole (think about how many updates are done to a 3D engine in its life. saves brandwidth somewhere),
- Expose parts of the engine to C++ mod developers, without scripting language.
- Keep projects small, easyer to maintain and develop.
There are many more advantages. One sure thing, 3D apps are quite large : smaller modular parts enhance the architecture of the application.
If you use the exe provided by a library vendor, then it is quite that together with the possible benefits, lots of dependencies will be introduced.
I am not saying the method not good, but it is better think twice before using it for serious application.
Regards,
Jiang