Dear Tony
Welcome to Wine.
After all the searches, I still do not have an overall idea of how to
create an control panel applet. From my current understanding, if I put the cpl (dll) file in "~/.wine/drive_c/windows/system32/", wine control will recognize it automatically, right?
When you add a new cpl, the wine build system does this for you.
If so, is there any instructions on how to build a simple applet under wine (even one that does nothing could work for me). I'd really like to try create and build some test applet in order to understand it better.
As always: Read the source. What you try to do (test applet) is how i started with inetcpl.cpl a while ago.
git has a web interface with a history and the first commit for inetcpl.cpl is a minimalistic control applet. ( http://source.winehq.org/git/wine.git/history/HEAD:/dlls/inetcpl.cpl )
When you add a new cpl, the wine build system does this for you.
So my question is: can I just build one cpl? Or do I need to re-build the
entire wine every time I want to test a particular cpl?
If I can just build one cpl, how should I build (compile) it and let the existing wine recognize it?
git has a web interface with a history and the first commit for inetcpl.cpl is a minimalistic control applet. ( http://source.winehq.org/git/wine.git/history/HEAD:/dlls/inetcpl.cpl )
Thanks, that helps a lot.
On 03/25/2011 11:12 AM, Tony Zhang wrote:
If I can just build one cpl, how should I build (compile) it and let the existing wine recognize it?
Yes, you can build only one dll/cpl/program:
# Assuming you are in wine source directory: $ make -C dlls/inetcpl.cpl
If you trying to use "existing Wine" [presumably an installed Wine] - it won't be that easy. It's recommended to not install Wine on a development system and run it directly from the compile directory instead..
Vitaliy.
-
Tony Zhang -
Vitaliy Margolen -
wine.dev＠web.de