Re: wxEuphoria vs Win32EuLib ?
- Posted by mattlewis (admin) Jun 11, 2009
- 1049 views
I read this: http://euwiki.ayo.biz/Wrapping
How will pgmr know if a '.dll/.so' is needed?
A dll/so (dynamically loaded library / shared object) is just some code that someone has written and compiled into a form that can be used by other programs. So it's really a matter of wanting to use something that exists in a dll.
For example, in order to access the Win32 API, in order to create windows, etc, Windows provides many different dlls that do different things. The most common are kernel32.dll and user32.dll. There are many others.
If feature is not available in wx, then it needs a '.dll/.so' for each feature missing ?
Would it also need a '.dll/.so' (per feature) for each target operating system?
I'm not sure exactly what you mean here. Are you talking about a feature of wxWidgets that wxEuphoria does not yet provide?
Different features could be built into a single dll, just like you can put more than one euphoria source code file into a program. Each operating system will need a different dll, as they all have slightly different file formats, as well as underlying libraries that the dll will need to use.
And what would the file extension be for a '.dll/.so' ?
"dll" and "so", respectively. 
Well, Ok, sometimes on windows, you'll get .ocx files, which are ActiveX components, and are really dlls, though they also have to follow some additional conventions.
Actually, sometimes, on unix-like systems, you'll get extra version information appended after the .so. wxEuphoria does this to make it easier to figure out which version of the library you're using:
libwxeu.so.13 libwxeu.so.14 ...etcThere's often also a symbolic link without the version information that points to (usually the latest, or current stable) the so. This allows users to not have to worry about the version number (assuming that different versions are compatible, of course).
Matt
