E
E
Evgeny Koryakin2021-09-05 03:19:18
Wine
Evgeny Koryakin, 2021-09-05 03:19:18

How to make Wine run faster on macOS?

Hello!
I quite often "build" applications for Windows using only those utilities that are available exclusively for Windows, but I'm sitting on macOS (it's more convenient for me).
Yes, I'm currently using wine-crossover(wine32on64) .

But when building, it constantly "restarts" its environment, for example:

Log
➜  ~ wine32on64 /Volumes/\[C\]\ Windows\ 11.hidden/Program\ Files\ \(x86\)/Inno\ Setup\ 5/Compil32.exe 
000b:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
000d:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0010:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0017:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
001d:err:plugplay:process_IOService_Device object 0x8c03
001d:err:plugplay:process_IOService_Device object 0x8a07
001d:err:plugplay:process_IOService_Device object 0x7307
001d:err:plugplay:process_IOService_Device object 0x7607
001d:err:plugplay:process_IOService_Device object 0x8807
001d:err:plugplay:process_IOService_Device object 0x7a07
001d:err:plugplay:process_IOService_Device object 0x8507
001d:err:plugplay:process_IOService_Device object 0x7e07
001d:err:plugplay:process_IOService_Device object 0x8307
001d:err:plugplay:process_IOService_Device object 0x8007
001d:err:plugplay:process_IOService_Device object 0x15407
001d:err:plugplay:process_IOService_Device Unable to create plug in interface for USB deviceobject 0x1540b
001d:err:plugplay:process_IOService_Device Unable to create plug in interface for USB deviceobject 0x1540f
001d:err:plugplay:process_IOService_Device Unable to create plug in interface for USB deviceobject 0x15413
001d:err:plugplay:process_IOService_Device Unable to create plug in interface for USB deviceobject 0x15417
001d:err:plugplay:process_IOService_Device object 0x15213
001d:err:plugplay:process_IOService_Device object 0x14f03
001f:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0025:fixme:thread:create_user_shared_data_thread Creating user shared data update thread.
0009:fixme:process:SetProcessDEPPolicy (1): stub
0009:fixme:shcore:SetCurrentProcessExplicitAppUserModelID L"JR.InnoSetup.IDE.5": stub
0009:fixme:process:RegisterApplicationRestart (L"",11)
0009:fixme:win:WINNLSEnableIME hwnd 0x1012e enable 0: stub!
0009:fixme:win:WINNLSEnableIME hwnd 0x1012e enable -1: stub!

After that, a successful build occurs and the process ends accordingly, but how to make it so that it does not end, but "continues" to wait for the next command without restarting its environment?

Answer the question

In order to leave comments, you need to log in

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question