Page 2 of 3

Posted: Mon Aug 23, 2010 8:39 am
by serengeor
For what are then those bunch of windows-DLLs in my system folders?
:shock:

For what does your computer has so much transistors in it ? :lol:

Posted: Mon Aug 23, 2010 10:24 am
by TomTim
serengeor wrote:For what does your computer has so much transistors in it ? :lol:
I'd explain you, but I think my english isn't good enough for that. ;)

OK, I think I have screwed it up. Somehow the compiler finds the files (I changed the VC++ directories of the Irrlicht project), but now I can't find the DLL, just a bunch of DirectX-LIBs ...

Posted: Mon Aug 23, 2010 6:11 pm
by Sylence
TomTim wrote:For what are then those bunch of windows-DLLs in my system folders?
Well that's easy. If they weren't there they'd have to included in *every* program.
If you have a program that let's say creates a blank window and closes on the click of the 'X' button.
The program needs to have access to the window handling routines (i.e. the messages windows uses to communicate with the window), the drawing routines for drawing the window on screen, the mouse input routines that will check if the 'X' button was clicked, and so on.

All this stuff in stored in the DLLs.

All the libraries and headers that you need to develop applications just tell you (or the compiler/linker) what functions are located in which DLL.

So the program can keep its small size since it doesn't need to know how the function works. It just calls the function from one of the DLLs on the system.

I know that this is a constructed example but you should get the point:
Image you would want to translate a word from one language into another. You could either take the big dictionary and look it yourself, or you could take the note with an URL on it, enter it into your browser, and let the lookup be done by someone(something) else.

The result is still the same: You know the translation of the word (or to keep at our program: we have a window that can be closed) however you didn't have to get the dictionary and look it up yourself (draw the window, check mouse input, etc.)

Posted: Mon Aug 23, 2010 6:21 pm
by TomTim
Sylence wrote:Well that's easy. If they weren't there they'd have to included in *every* program.
If you have a program that let's say creates a blank window and closes on the click of the 'X' button.
The program needs to have access to the window handling routines (i.e. the messages windows uses to communicate with the window), the drawing routines for drawing the window on screen, the mouse input routines that will check if the 'X' button was clicked, and so on.

All this stuff in stored in the DLLs.

All the libraries and headers that you need to develop applications just tell you (or the compiler/linker) what functions are located in which DLL.

So the program can keep its small size since it doesn't need to know how the function works. It just calls the function from one of the DLLs on the system.

I know that this is a constructed example but you should get the point:
Image you would want to translate a word from one language into another. You could either take the big dictionary and look it yourself, or you could take the note with an URL on it, enter it into your browser, and let the lookup be done by someone(something) else.

The result is still the same: You know the translation of the word (or to keep at our program: we have a window that can be closed) however you didn't have to get the dictionary and look it up yourself (draw the window, check mouse input, etc.)
OK, understood.

But that doesn't help me. Where is the *someselectedgermanwordsofswearing* DLL?

Posted: Mon Aug 23, 2010 9:14 pm
by serengeor
But that doesn't help me. Where is the *someselectedgermanwordsofswearing* DLL?
Do you mean irrlicht DLL ? if so, you should Compile it yourself, Or use the SDK given one in the bin folder. (Don't know how to compile? Search for tutorials! :) )

Posted: Tue Aug 24, 2010 5:36 am
by TomTim
serengeor wrote:Do you mean irrlicht DLL ? if so, you should Compile it yourself, Or use the SDK given one in the bin folder. (Don't know how to compile? Search for tutorials! :) )
Of cause I know how to compile ... do people here just read one half of my posts and try to guess the second half?

The problem is that there simply IS no Irrlicht.DLL. I searched every folder in which the engine is stored, but the is no DLL, just some DirectX.LIBs ...

Posted: Tue Aug 24, 2010 12:04 pm
by CuteAlien
Usually the Irrlicht.dll for VisualStudio is in bin/Win32-VisualStudio (and correspondingly the other sub-folders for other IDE and system combinations). But we have not yet ported to VS10 - so no idea if it works there or not.

Posted: Tue Aug 24, 2010 12:07 pm
by slavik262
Irrlicht works perfectly fine in VC++ 2010. The only problem I've ever encountered is that some of the example solutions don't convert properly, but that shouldn't be a big deal.

Posted: Tue Aug 24, 2010 12:08 pm
by TomTim
CuteAlien wrote:Usually the Irrlicht.dll for VisualStudio is in bin/Win32-VisualStudio (and correspondingly the other sub-folders for other IDE and system combinations). But we have not yet ported to VS10 - so no idea if it works there or not.
So what does that mean for me? Where is it?

Posted: Tue Aug 24, 2010 1:20 pm
by CuteAlien
TomTim wrote:
CuteAlien wrote:Usually the Irrlicht.dll for VisualStudio is in bin/Win32-VisualStudio (and correspondingly the other sub-folders for other IDE and system combinations). But we have not yet ported to VS10 - so no idea if it works there or not.
So what does that mean for me? Where is it?
I don't know. It's there if you download the official Irrlicht zip. It's also usually there if you compile Irrlicht and it finishes without error. Sorry - I do not see your screen - so I simply don't know what error messages you got, what you tried doing, etc.

Posted: Tue Aug 24, 2010 4:09 pm
by serengeor
Well I taught you used MSVC 2008, but since its 2010 I Don't really know I had encountered the same problem, but I don't remember how I fixed it (I think I changed the build directories).
Now I'm using code::blocks and I haven't encountered any problems since I switched to it.
Well actually I did encounter one problem which was not really a problem, I taught It hadn't Code completion but it does and It Rocks :)

Posted: Tue Aug 24, 2010 10:59 pm
by booe
Damn it, serengeor, I love your avatar!
THIS SHEEP IS SO CUTE!!!

Posted: Wed Aug 25, 2010 9:58 am
by TomTim
CuteAlien wrote:I don't know. It's there if you download the official Irrlicht zip. It's also usually there if you compile Irrlicht and it finishes without error. Sorry - I do not see your screen - so I simply don't know what error messages you got, what you tried doing, etc.
I GOT the official Irrlich archive. But my new compiled DLL is nowhere - just nowhere.
booe wrote:Damn it, serengeor, I love your avatar!
THIS SHEEP IS SO CUTE!!!
That has nothing to do with the topic, has it?

Posted: Wed Aug 25, 2010 2:46 pm
by hybrid
TomTim wrote:That has nothing to do with the topic, has it?
Well, you need more than 20 replies to figure out something most others can cope with right away. So I doubt there's really a problem with a little off-topic post.

Posted: Wed Aug 25, 2010 3:35 pm
by TomTim
hybrid wrote:
TomTim wrote:That has nothing to do with the topic, has it?
Well, you need more than 20 replies to figure out something most others can cope with right away. So I doubt there's really a problem with a little off-topic post.
Yeah, however. I just wanted to know how "strict" the people here are ... ;)

OK, back to my problem:

I now want to do a little "restart". Means, I wanna copy the DirectX headers, LIBs and DLLs into the folders of my compiler (I have installed the SDK, but I have figured out that they weren't installed in the folders of my compiler). But from where to where? I've got a 64 Bit OS, but some users of my program might have only a 32 Bit OS, so will I have to use the 32 Bit datas, or is the specification only important for the developer? And where do I find the DirectX DLLs, I can't find them in the SDK ...

And how about a later SDK? I mean, this DirectX version seems to be 2 years old, maybe some things are updated ... :?: