Concerning Wine binary package behavior with 32bit and audio

N

nphuracm

OS: FreeBSD 14.1-RELEASE amd64. (lib32.txz component not installed during FreeBSD installation.)
When I installed wine via pkg and immediately issued winecfg without additional configuration, this happened:
Code: 
/home/nphuracm/.i386-wine-pkg//usr/local/bin/wine doesn't exist!

Try installing 32-bit Wine with
    /usr/local/share/wine/pkg32.sh install wine mesa-dri

If using Poudriere, please make sure your repo is setup to use FreeBSD:14:i386
and create symlinks for
  FreeBSD:14:amd64 and
  FreeBSD:14:i386
to the relevant output directories. See pkg.conf(5) for more info.
Apparently the Wine binary package on amd64 expects a 32-bit Wine to be present simultaneously in a very specific alternate prefix to even work, even though I personally have no intentions of using 32-bit Windows programs as of now.
I have checked the Handbook and it did not cover this situation. I have followed the instructions as included in the command output but this seems to be a dirty implementation that might cripple manageability further on.

The Wine package also now depends on ALSA packages like alsa-lib and alsa-plugins, and uses the ALSA " winealsa" driver rather than simply use the OSS as included in the FreeBSD base system with wineoss, which is another situation not covered in the Handbook.

I would like to obtain further explanation of these behavior.
 
Hello,

you can use Wine without having i386 installed by using wine64 instead.

Example: wine64 winecfg

You can also link wine64 to wine so that the amd64 part gets always used.

ALSA have been choosed as default audio because our sound system has no AFMT_FLOAT support and issues with XAudio2 (and with some WASAPI? iirc) applications in Win Vista compat mode and higher.
 
You must log in or register to reply here.
Back
Top