Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Thu 21 Nov 2019, 08:59
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Virtualization
Wine - run Windows programs in Linux
Post new topic   Reply to topic View previous topic :: View next topic
Page 27 of 27 [397 Posts]   Goto page: Previous 1, 2, 3, ..., 25, 26, 27
Author Message
version2013

Joined: 08 Sep 2013
Posts: 450
Location: Florida, USA

PostPosted: Tue 01 Oct 2019, 18:28    Post subject: wine64-4.16  

My attempt at compiling wine64
This is a WOW64 build.
https://wiki.winehq.org/Building_Wine#Shared_WoW64

[wine-4.16 mirrors]

wine64-4.16_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.16.pet __________ tahrpup64 6.0.5
wine64_DOC-4.16.pet __________ tahrpup64 6.0.5

----------------------------
tahrpup64 6.0.5
----------------------------

When compiling in tahrpup64 6.0.5, I used:
Code:
configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --enable-win64 --libdir=/usr/lib64 CFLAGS="-O2"


https://wiki.winehq.org/Packaging#WoW64_Workarounds
For the 32-bit wine build, I used files from 'wine-4.16_v3.1.pet' from the previous forum post.
----------------------------------------------------------------------------------------------------------
The 32-bit wineserver is included, just in case it is needed.
It is a hidden file ".wineserver"

I do not have any 64-bit applications to test.
I can only do minimal testing because my AMD graphics driver is not functioning properly.
I may have to learn to compile Mesa to do any more detailed testing of 32-bit applications with this wine build.
I am relying on others to test this wine version.
Back to top
View user's profile Send private message Visit poster's website 
version2013

Joined: 08 Sep 2013
Posts: 450
Location: Florida, USA

PostPosted: Thu 10 Oct 2019, 21:22    Post subject: wine-4.17  

My attempt at compiling wine-4.17

[wine-4.17 mirrors]

2.x failed to compile because of a bug

wine-4.17_v3.1.pet _________ tahrpup 6.0.5 PAE [stripped=true]
wine-4.17_v3.2.pet _________ tahrpup 6.0.5 PAE [stripped=false]
wine_DEV-4.17_v3.1.pet ____ tahrpup 6.0.5 PAE
wine_DEV-4.17_v3.2.pet ____ tahrpup 6.0.5 PAE

wine_DOC-4.17.pet

wine_extras-v2.1.pet __________ menu entries | mirrors
md5.txt and hashdeep.txt ____ checksums/hashes | mirrors

----------------------------------------------------------------
Notes for my webpage
http://version2013.yolasite.com/page1.php

The ">" character points to a directory of download links, or an individual download link.
example:
> __ wine/4.17/
> _____wine-4.17_v1.1.pet

----------------------------------------------------------------

For general use, I recommend packages that are 'stripped=true'.
For submitting bug reports to WineHQ, I recommend packages that are 'stripped=false'.
When submitting bug reports to WineHQ, it appears a 'stripped=false' Wine provides more information than a 'stripped=true' Wine.
[references: post]

The first post has links to:
pet to sfs scripts, menu entry utilities, and Wine usage tips.

----------------------------------------------------------------------------------------------------------

----------------------------
tahrpup 6.0.5 PAE
----------------------------

I installed the following files before compiling.
Support for these files (dependencies) are compiled into wine.
The files are not included in the wine .pet.
They still need to be installed in puppy for wine to use their features.
The dev files are only needed when compiling.

[mirrors]
mpg123/1.25.10/mpg123-1.25.10_v1.1.pet
mpg123/1.25.10/mpg123_DEV-1.25.10.pet

[mirrors]
openal-soft/1.13/openal-soft-1.13-i486_v1.1.pet
openal-soft/1.13/openal-soft_DEV-1.13-i486_v1.pet

----------------------------------------

When compiling in tahrpup 6.0.5 PAE, I used:
v3.1
Code:
configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i486 -mtune=i686"

v3.2
Code:
configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-g -O0 -fno-optimize-sibling-calls -fno-omit-frame-pointer -fno-inline -march=i486 -mtune=i686"


----------------------------------------------------------------------------------------------------------

Menu entries, Color Setter, and other stuff I got from the file 'winegoodies.tar.gz' [post] provided by forum member 'technosaurus'.
I only made a few changes to the contents of that file.

----------------------------------------------------------------------------------------------------------

updated links at my homepage. see below.

Last edited by version2013 on Sun 13 Oct 2019, 22:00; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website 
version2013

Joined: 08 Sep 2013
Posts: 450
Location: Florida, USA

PostPosted: Thu 10 Oct 2019, 21:22    Post subject: wine64-4.17  

My attempt at compiling wine64
This is a WOW64 build.
https://wiki.winehq.org/Building_Wine#Shared_WoW64

[wine-4.17 mirrors]

wine64-4.17_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.17.pet __________ tahrpup64 6.0.5
wine64_DOC-4.17.pet __________ tahrpup64 6.0.5

----------------------------
tahrpup64 6.0.5
----------------------------

When compiling in tahrpup64 6.0.5, I used:
Code:
configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --enable-win64 --libdir=/usr/lib64 CFLAGS="-O2"


https://wiki.winehq.org/Packaging#WoW64_Workarounds
For the 32-bit wine build, I used files from 'wine-4.17_v3.1.pet' from the previous forum post.
----------------------------------------------------------------------------------------------------------
The 32-bit wineserver is included, just in case it is needed.
It is a hidden file ".wineserver"

I do not have any 64-bit applications to test.
I can only do minimal testing because my AMD graphics driver is not functioning properly.
I may have to learn to compile Mesa to do any more detailed testing of 32-bit applications with this wine build.
I am relying on others to test this wine version.
Back to top
View user's profile Send private message Visit poster's website 
version2013

Joined: 08 Sep 2013
Posts: 450
Location: Florida, USA

PostPosted: Sat 02 Nov 2019, 23:00    Post subject: Wine-4.18  

My attempt at compiling wine-4.18

[wine-4.18 mirrors]

2.x failed to compile because of a bug

wine-4.18_v3.1.pet _________ tahrpup 6.0.5 PAE [stripped=true]
wine-4.18_v3.2.pet _________ tahrpup 6.0.5 PAE [stripped=false]
wine_DEV-4.18_v3.1.pet ____ tahrpup 6.0.5 PAE
wine_DEV-4.18_v3.2.pet ____ tahrpup 6.0.5 PAE

wine_DOC-4.18.pet

wine_extras-v2.1.pet __________ menu entries | mirrors
md5.txt and hashdeep.txt ____ checksums/hashes | mirrors

----------------------------------------------------------------
Notes for my webpage
http://version2013.yolasite.com/page1.php

The ">" character points to a directory of download links, or an individual download link.
example:
> __ wine/4.18/
> _____wine-4.18_v1.1.pet

----------------------------------------------------------------

For general use, I recommend packages that are 'stripped=true'.
For submitting bug reports to WineHQ, I recommend packages that are 'stripped=false'.
When submitting bug reports to WineHQ, it appears a 'stripped=false' Wine provides more information than a 'stripped=true' Wine.
[references: post]

The first post has links to:
pet to sfs scripts, menu entry utilities, and Wine usage tips.

----------------------------------------------------------------------------------------------------------

----------------------------
tahrpup 6.0.5 PAE
----------------------------

I installed the following files before compiling.
Support for these files (dependencies) are compiled into wine.
The files are not included in the wine .pet.
They still need to be installed in puppy for wine to use their features.
The dev files are only needed when compiling.

[mirrors]
mpg123/1.25.10/mpg123-1.25.10_v1.1.pet
mpg123/1.25.10/mpg123_DEV-1.25.10.pet

[mirrors]
openal-soft/1.13/openal-soft-1.13-i486_v1.1.pet
openal-soft/1.13/openal-soft_DEV-1.13-i486_v1.pet

----------------------------------------

When compiling in tahrpup 6.0.5 PAE, I used:
v3.1
Code:
configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i486 -mtune=i686"

v3.2
Code:
configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --libdir=/usr/lib32 CFLAGS="-g -O0 -fno-optimize-sibling-calls -fno-omit-frame-pointer -fno-inline -march=i486 -mtune=i686"


----------------------------------------------------------------------------------------------------------

Menu entries, Color Setter, and other stuff I got from the file 'winegoodies.tar.gz' [post] provided by forum member 'technosaurus'.
I only made a few changes to the contents of that file.

----------------------------------------------------------------------------------------------------------

updated links at my homepage. see below.
Back to top
View user's profile Send private message Visit poster's website 
version2013

Joined: 08 Sep 2013
Posts: 450
Location: Florida, USA

PostPosted: Sat 02 Nov 2019, 23:01    Post subject: Wine64-4.18  

My attempt at compiling wine64
This is a WOW64 build.
https://wiki.winehq.org/Building_Wine#Shared_WoW64

[wine-4.18 mirrors]

wine64-4.18_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.18.pet __________ tahrpup64 6.0.5
wine64_DOC-4.18.pet __________ tahrpup64 6.0.5

----------------------------
tahrpup64 6.0.5
----------------------------

When compiling in tahrpup64 6.0.5, I used:
Code:
configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x --enable-win64 --libdir=/usr/lib64 CFLAGS="-O2"


https://wiki.winehq.org/Packaging#WoW64_Workarounds
For the 32-bit wine build, I used files from 'wine-4.18_v3.1.pet' from the previous forum post.
----------------------------------------------------------------------------------------------------------
The 32-bit wineserver is included, just in case it is needed.
It is a hidden file ".wineserver"

I do not have any 64-bit applications to test.
I can only do minimal testing because my AMD graphics driver is not functioning properly.
I may have to learn to compile Mesa to do any more detailed testing of 32-bit applications with this wine build.
I am relying on others to test this wine version.
Back to top
View user's profile Send private message Visit poster's website 
don570


Joined: 10 Mar 2010
Posts: 5374
Location: Ontario

PostPosted: Wed 06 Nov 2019, 19:43    Post subject:  

I was able to use this audio player when using WINE
https://mpesch3.de/1by1.html
___________________________________________________
Back to top
View user's profile Send private message 
version2013

Joined: 08 Sep 2013
Posts: 450
Location: Florida, USA

PostPosted: Fri 15 Nov 2019, 14:08    Post subject: wine-4.19  

2.x failed to compile because of a bug
3.x failed to compile because of a bug
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 27 of 27 [397 Posts]   Goto page: Previous 1, 2, 3, ..., 25, 26, 27
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Virtualization
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.2057s ][ Queries: 12 (0.1026s) ][ GZIP on ]