November 2015 - Wine-Devel - list.winehq.org

Re: README: add a note about 64-bit Wine needing 32-bit Wine to work

by Sebastian Lackner

On 30.11.2015 06:04, Dmitry Timoshkov wrote: > Sebastian Lackner <sebastian(a)fds-team.de> wrote: > >>>> + http://wiki.winehq.org/Wine64 for details. Note that a 64-bit Wine >>>> + build will not work without also building 32-bit Wine. >>> >>> This statement is not true in general. >>> >>> Actually 64-bit Wine build works just fine without any 32-bit part. That's >>> just a useless configuration, but it's a minor detail. >>> >> >> It depends on your definion of "works just fine". Various parts of wine contain >> hardcoded paths to 32-bit executables, which can't work in a pure 64-bit build. > > By "works just fine" I mean that 64-bit Wine build is able to execute 64-bit > Windows applications and built-in Wine programs. But not if a user tries to run the built-in program with one of the shell script wrappers. ;) > >> programs/winemenubuilder/winemenubuilder.c: >> fprintf(file, "Exec=env WINEPREFIX=\"%s\" wine %s %s\n", >> >> tools/wineapploader.in >> exec wine "$appname" "$@" > > That's just a symlink to the launcher, and probably it should depend on > actual build. > >> Not sure if there is a way to express it a bit better, but I think in general it >> probably wouldn't hurt to have this documented somewhere in the source tree. > > Sure. > Actually, when I think a bit more about it, instead of adding more documentation, we probably just want to fix those few remaining symlink / wrapper script problems. Of course it will still confuse unexperienced users who want to run their 32-bit apps, but at least experienced users could use it as an (almost) fully functional standalone Wine version then - of course at their own risk. ;)

Nov. 30, 2015

Re: README: add a note about 64-bit Wine needing 32-bit Wine to work

by Dmitry Timoshkov

Sebastian Lackner <sebastian(a)fds-team.de> wrote: > >> + http://wiki.winehq.org/Wine64 for details. Note that a 64-bit Wine > >> + build will not work without also building 32-bit Wine. > > > > This statement is not true in general. > > > > Actually 64-bit Wine build works just fine without any 32-bit part. That's > > just a useless configuration, but it's a minor detail. > > > > It depends on your definion of "works just fine". Various parts of wine contain > hardcoded paths to 32-bit executables, which can't work in a pure 64-bit build. By "works just fine" I mean that 64-bit Wine build is able to execute 64-bit Windows applications and built-in Wine programs. > programs/winemenubuilder/winemenubuilder.c: > fprintf(file, "Exec=env WINEPREFIX=\"%s\" wine %s %s\n", > > tools/wineapploader.in > exec wine "$appname" "$@" That's just a symlink to the launcher, and probably it should depend on actual build. > Not sure if there is a way to express it a bit better, but I think in general it > probably wouldn't hurt to have this documented somewhere in the source tree. Sure. -- Dmitry.

Nov. 30, 2015

Re: README: add a note about 64-bit Wine needing 32-bit Wine to work

by Austin English

On Sun, Nov 29, 2015 at 10:56 PM, Dmitry Timoshkov <dmitry(a)baikal.ru> wrote: > Austin English <austinenglish(a)gmail.com> wrote: > >> >> + http://wiki.winehq.org/Wine64 for details. Note that a 64-bit Wine >> >> + build will not work without also building 32-bit Wine. >> > >> > This statement is not true in general. >> > >> > Actually 64-bit Wine build works just fine without any 32-bit part. That's >> > just a useless configuration, but it's a minor detail. >> > >> > -- >> > Dmitry. >> >> Good point. How do you feel about: >> + http://wiki.winehq.org/Wine64 for details. Note that a 64-bit Wine build >> + will not work for most applications without also building 32-bit Wine. > > Why do you need that? README already mentions 64-bit Wine and references this > wiki page. > > -- > Dmitry. Not everyone is going to bother to open a webpage. -- -Austin

Nov. 30, 2015

Re: README: add a note about 64-bit Wine needing 32-bit Wine to work

by Dmitry Timoshkov

Austin English <austinenglish(a)gmail.com> wrote: > >> + http://wiki.winehq.org/Wine64 for details. Note that a 64-bit Wine > >> + build will not work without also building 32-bit Wine. > > > > This statement is not true in general. > > > > Actually 64-bit Wine build works just fine without any 32-bit part. That's > > just a useless configuration, but it's a minor detail. > > > > -- > > Dmitry. > > Good point. How do you feel about: > + http://wiki.winehq.org/Wine64 for details. Note that a 64-bit Wine build > + will not work for most applications without also building 32-bit Wine. Why do you need that? README already mentions 64-bit Wine and references this wiki page. -- Dmitry.

Nov. 30, 2015

Re: README: add a note about 64-bit Wine needing 32-bit Wine to work

by Sebastian Lackner

On 30.11.2015 05:37, Dmitry Timoshkov wrote: > Austin English <austinenglish(a)gmail.com> wrote: > >> + http://wiki.winehq.org/Wine64 for details. Note that a 64-bit Wine >> + build will not work without also building 32-bit Wine. > > This statement is not true in general. > > Actually 64-bit Wine build works just fine without any 32-bit part. That's > just a useless configuration, but it's a minor detail. > It depends on your definion of "works just fine". Various parts of wine contain hardcoded paths to 32-bit executables, which can't work in a pure 64-bit build. programs/winemenubuilder/winemenubuilder.c: fprintf(file, "Exec=env WINEPREFIX=\"%s\" wine %s %s\n", tools/wineapploader.in exec wine "$appname" "$@" Not sure if there is a way to express it a bit better, but I think in general it probably wouldn't hurt to have this documented somewhere in the source tree.

Nov. 30, 2015

Re: README: add a note about 64-bit Wine needing 32-bit Wine to work

by Austin English

On Sun, Nov 29, 2015 at 10:37 PM, Dmitry Timoshkov <dmitry(a)baikal.ru> wrote: > Austin English <austinenglish(a)gmail.com> wrote: > >> + http://wiki.winehq.org/Wine64 for details. Note that a 64-bit Wine >> + build will not work without also building 32-bit Wine. > > This statement is not true in general. > > Actually 64-bit Wine build works just fine without any 32-bit part. That's > just a useless configuration, but it's a minor detail. > > -- > Dmitry. Good point. How do you feel about: + http://wiki.winehq.org/Wine64 for details. Note that a 64-bit Wine build + will not work for most applications without also building 32-bit Wine. -- -Austin

Nov. 30, 2015

Re: README: add a note about 64-bit Wine needing 32-bit Wine to work

by Dmitry Timoshkov

Austin English <austinenglish(a)gmail.com> wrote: > + http://wiki.winehq.org/Wine64 for details. Note that a 64-bit Wine > + build will not work without also building 32-bit Wine. This statement is not true in general. Actually 64-bit Wine build works just fine without any 32-bit part. That's just a useless configuration, but it's a minor detail. -- Dmitry.

Nov. 30, 2015

Re: contribute to wine

by Austin English

On Sun, Nov 29, 2015 at 12:35 AM, Abhijeet Panda <abpnd12(a)gmail.com> wrote: > hello everyone, > I am a undergrad student and have been using wine on my linux for a > while. I am a big fan of this program and I want to contribute a lot > to this. I have been through the getting started page. Is there anyone > who could tell me the projects which are open and I could contribute > to. > thank you Most projects are open to work on, but some require more experience/knowledge than others. We can't really give you advice without knowing what you're interested in / what skills you have. http://wiki.winehq.org/Developers is a good starting point -- -Austin

Nov. 30, 2015

Re: [v3] po: Update Simplified Chinese translation.

by Jactry Zeng

Hi Boyuan, Thanks for update! > #: oleacc.rc:99 > #, fuzzy > -#| msgid "Select" > msgctxt "object state" > msgid "selected" > msgstr "选择" I think "selected" here can be translated as "已选择". -- Regards, Jactry Zeng

Nov. 30, 2015

Re: Make a 16-bit test in wine for krnl386.exe16

by Alexandre Julliard

Bruno Jesus <00cpxxx(a)gmail.com> writes: > On Mon, Nov 30, 2015 at 2:13 AM, Nikolay Sivov <bunglehead(a)gmail.com> wrote: >> I think the main problem is to actually be able to build NE binaries, >> for that you'll need tools that support this, for example openwatcom C >> compiler, or some old enough Visual C++, maybe version 5 or 4. > > So basically it is not possible to integrate such tests in wine as a > standard test like any other. Right, that's not supported. -- Alexandre Julliard julliard(a)winehq.org

Nov. 30, 2015