On Friday January 25 2008 04:21:37 Aryeh M. Friedman wrote: >> Don't try to use DLLs from Windows without reason. By definition, if you >> just want replace all WINE DLLs with Windows DLLs you should use Windows in >> virtual machine (because WINE will never support use of ALL Windows DLLs). >> And of course native DLLs will not help you to compile or install WINE >> anyway. > A. Techinical that is incorrect as far I can tell since winlib is > meant to read and run any DLL right? WINE is not designed to run any *Windows* DLLs. For example you by definition cannot run directx DLLs, ntdll, kernel32 and some others from Windows. There is (low-level) technical reasons for this. BTW, do not confuse *Windows* DLLs and application's DLLs *for Windows* (like mfc42.dll and many others, or like custom DLLs). This is different things. Main difference is that use of native Windows DLLs isn't supported by WINE team (you should use builtin ones instead). > >> 2. When I do a make (I am not installing as a port) I get: > >> > >> actxprxy_servprov_p.c:272:2: error: #error Currently only Wine and > >> WIN32 are supported. > > > > You can find instructions about how to compile/install WINE on FreeBSD > > here: > > http://www.codeweavers.com/support/docs/wine-user/getting-wine-package#GE > >TTING-FREEBSD > > > > and http://www.freshports.org/emulators/wine/ . > > Those are the exact procedures that caused the errors I listed. I can suggest to contact with maintainer of FreeBSD package. Sorry, I cannot help more because I know very little about FreeBSD. Maybe other people on the list can help... _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
