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 Sun 15 Dec 2019, 16:35
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 26 of 27 [401 Posts]   Goto page: Previous 1, 2, 3, ..., 24, 25, 26, 27 Next
Author Message
version2013

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

PostPosted: Thu 25 Jul 2019, 18:26    Post subject: Wine-4.12.1  

My attempt at compiling wine-4.12.1

1.x and 2.x failed to compile because of bug

[wine-4.12.1 mirrors]

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

wine_DOC-4.12.1.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.12.1/
> _____wine-4.12.1_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 Thu 25 Jul 2019, 18:36; 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: 455
Location: Florida, USA

PostPosted: Thu 25 Jul 2019, 18:26    Post subject: Wine64-4.12.1  

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

[wine-4.12.1 mirrors]

wine64-4.12.1_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.12.1.pet __________ tahrpup64 6.0.5
wine64_DOC-4.12.1.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.12.1_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 
davids45


Joined: 26 Nov 2006
Posts: 1237
Location: Chatswood, NSW

PostPosted: Mon 05 Aug 2019, 21:12    Post subject: 64-bit Pups
Subject description: Cannot run in-built Wine progs nor add programs
 

G'day version2013,

Thanks for your continued work making Wine available in Puppy.
Working well in 32-bit Pups for many years and, with the right libraries, the 32-bit Wine runs in some 64-bit Pups.

But I think I need to I have a working Wine64 as this seems to be the eventual future - 64-bit OSs only.

I have not had any luck with your Wine64-4.xx pet. It installs from the pet and will "winecfg" in a terminal.
Notepad will then open but no other in-built windows application starts (e.g. winemine).
Trying to install a Windows-based application program also gets no response.

I appreciate your stated problem with 64-bit testing on your machine, but can you get, say, winemine, running as a test? I see its .exe file in two sub-directories in windows, system32 and systemwow64. I don't know which is more likely to work.

If you haven't seen it,
http://www.murga-linux.com/puppy/viewtopic.php?p=1030483#1030483
looks interesting as I too prefer to use an sfs over a pet so if I get a Wine64 pet to run, I'll turn it into an sfs for sharing to all my 64-bit Pups (as I do for the 32-bit Wine to my 32-bit Pups).

Thanks for any advice.

David S.
Back to top
View user's profile Send private message 
Mike Walsh


Joined: 28 Jun 2014
Posts: 5672
Location: King's Lynn, UK.

PostPosted: Tue 06 Aug 2019, 12:05    Post subject:  

@ David:-

I was having a read of something the other night which surprised me, in relation to WOW64, system32, etc. Were you aware that in a 64-bit Windows release, SysWOW64 apparently contains 32-bit executables/dlls, and the 64-bit ones are all found in system32?

No idea if that'll be of any use or not, but perhaps it may give you some clues.....check 'Properties' on some of these things, and see what ELF class you get showing in which directory. Sure sounds as confusing as hell..! Very Happy

This article from MakeUseOf.com tells the tale...

https://www.makeuseof.com/tag/windows-system32/

".....<snip> On 64-bit versions of Windows, you’ll notice a few folder differences, like the separate Program Files (x86) directory. Something similar occurs with System32. In the C:\Windows folder on a 64-bit system, you’ll find a folder called SysWOW64 in addition to System32.

Take a look, and you’ll see that the two folders contain many files with identical names. Like Program Files (x86), Windows includes these two separate directories for compatibility with 32-bit programs. If a 32-bit program tried to load a 64-bit DLL, it would crash."



Now; naturally enough, you'd expect the system32 folder to contain the 32-bit stuff, and SysWOW64 to contain the 64-bit stuff, yes? Not so! Read on...


"But what’s strange is that on 64-bit systems, System32 has 64-bit files, while SysWOW64 contains 32-bit files. As it turns out, WoW64 stands for Windows 32-bit on Windows 64-bit. This is a service that allows the OS to properly run 32-bit programs, even on a 64-bit system.

Part of how it accomplishes this is by automatically redirecting 32-bit processes to use the proper folders. A 32-bit program, not even knowing that 64-bit software exists, will naturally try to access the System32 folder. But WoW redirects it to use the SysWOW64 instead. The same happens with Program Files.

Since many old 32-bit programs were hard-coded to access System32 and Program Files, this redirecting method allows 32-bit and 64-bit programs to both work on one system with ease. It’s a bit confusing, but now you know the reason for it.</snip>.......


Food for thought, perhaps?


Mike. Wink

_________________
MY 'PUPPY' PACKAGES

Back to top
View user's profile Send private message 
version2013

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

PostPosted: Sat 17 Aug 2019, 18:42    Post subject: Wine-4.13  

My attempt at compiling wine-4.13

[wine-4.13 mirrors]

wine-4.13_v1.1.pet _________ puppy 431 [stripped=true]
wine-4.13_v1.2.pet _________ puppy 431 [stripped=false]
wine_DEV-4.13_v1.1.pet ____ puppy 431
wine_DEV-4.13_v1.2.pet ____ puppy 431

wine-4.13_v2.1.pet _________ racy 5.5 [stripped=true]
wine-4.13_v2.2.pet _________ racy 5.5 [stripped=false]
wine_DEV-4.13_v2.1.pet ____ racy 5.5
wine_DEV-4.13_v2.2.pet ____ racy 5.5

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

wine_DOC-4.13.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.13/
> _____wine-4.13_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.

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

----------------
puppy 431
----------------

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]
bison/3.3/bison-3.3_v1.2.pet
bison/3.3/bison_DEV-3.3_v1.2.pet

[mirrors]
fontconfig/2.7.1/fontconfig-2.7.1-i486-pup4.pet
fontconfig/2.7.1/fontconfig_DEV-2.7.1-i486-pup4.pet

[mirrors]
gmp/6.1.1/gmp-6.1.1-i486_v1.2.pet
gmp/6.1.1/gmp_DEV-6.1.1-i486_v1.2.pet

[mirrors]
gnutls/3.5.2/gnutls-3.5.2_v1.2.pet
gnutls/3.5.2/gnutls_DEV-3.5.2.pet

[mirrors]
lcms2/2.8/lcms2-2.8_v2.pet
lcms2/2.8/lcms2_DEV-2.8_v2.pet

[mirrors]
libelf/0.8.13/libelf-0.8.13-i486_v2.pet
libelf/0.8.13/libelf_DEV-0.8.13-i486_v2.pet

[mirrors]
libgcrypt/1.4.6/libgcrypt-1.4.6-i486-431.pet
libgcrypt/1.4.6/libgcrypt_DEV-1.4.6-i486-431.pet

[mirrors]
libgpg-error/1.10/libgpg-error-1.10-i486-431.pet
libgpg-error/1.10/libgpg_DEV-error-1.10-i486-431.pet

[mirrors]
libgphoto2/2.5.0/libgphoto2-2.5.0-i486_v2.pet
libgphoto2/2.5.0/libgphoto2_DEV-2.5.0-i486.pet

[mirrors]
libtasn1/4.8/libtasn1-4.8-i486_v1.2.pet
libtasn1/4.8/libtasn1_DEV-4.8-i486_v1.2.pet

[mirrors]
libusb/1.0.9/libusb-1.0.9-i486_v2.pet
libusb/1.0.9/libusb_DEV-1.0.9-i486_v2.pet

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

[mirrors]
nettle/3.2/nettle-3.2_v1.2.pet
nettle/3.2/nettle_DEV-3.2_v1.2.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

[mirrors]
openldap/2.4.13/openldap-2.4.13-i486.pet
openldap/2.4.13/openldap_DEV-2.4.13-i486.pet

[mirrors]
prelink/20130503/prelink-20130503-i486_v2.pet

[mirrors]
xorg/7.3/xorg_xorg_full_dri-7.3.pet
xorg/7.3/xorg_xorg_full_dri_DEV-7.3.pet

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

When compiling in puppy 431, I used:
v1.1
Code:
configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --x-includes=/usr/X11R7/include --x-libraries=/usr/X11R7/lib --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i486 -mtune=i686"

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


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

------------
racy 5.5
------------

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]
bison/3.3/bison-3.3_v1.2.pet
bison/3.3/bison_DEV-3.3_v1.2.pet

[mirrors]
fontconfig/2.8.0/fontconfig-2.8.0-w5c.pet
fontconfig/2.8.0/fontconfig_DEV-2.8.0-w5c.pet

[mirrors]
gmp/6.1.1/gmp-6.1.1-i486_v1.2.pet
gmp/6.1.1/gmp_DEV-6.1.1-i486_v1.2.pet

[mirrors]
gnutls/3.5.2/gnutls-3.5.2_v1.2.pet
gnutls/3.5.2/gnutls_DEV-3.5.2.pet

[mirrors]
lcms2/2.8/lcms2-2.8_v2.pet
lcms2/2.8/lcms2_DEV-2.8_v2.pet

[mirrors]
libelf/0.8.13/libelf-0.8.13-i486_v2.pet
libelf/0.8.13/libelf_DEV-0.8.13-i486_v2.pet

[mirrors]
libgcrypt/1.4.6/libgcrypt-1.4.6-i486-431.pet
libgcrypt/1.4.6/libgcrypt_DEV-1.4.6-i486-431.pet

[mirrors]
libgpg-error/1.10/libgpg-error-1.10-i486-431.pet
libgpg-error/1.10/libgpg_DEV-error-1.10-i486-431.pet

[mirrors]
libtasn1/4.8/libtasn1-4.8-i486_v1.2.pet
libtasn1/4.8/libtasn1_DEV-4.8-i486_v1.2.pet

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

[mirrors]
nettle/3.2/nettle-3.2_v1.2.pet
nettle/3.2/nettle_DEV-3.2_v1.2.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

[mirrors]
openldap/2.4.13/openldap-2.4.13-i486.pet
openldap/2.4.13/openldap_DEV-2.4.13-i486.pet

[mirrors]
prelink/20130503/prelink-20130503-i486_v2.pet

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

When compiling in racy 5.5, I used:
v2.1
Code:
configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --x-includes=/usr/X11R7/include --x-libraries=/usr/X11R7/lib --with-x --libdir=/usr/lib32 CFLAGS="-O2 -march=i486 -mtune=i686"

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


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

----------------------------
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: 455
Location: Florida, USA

PostPosted: Sat 17 Aug 2019, 18:43    Post subject: Wine64-4.13  

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

[wine-4.13 mirrors]

wine64-4.13_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.13.pet __________ tahrpup64 6.0.5
wine64_DOC-4.13.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.13_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: 455
Location: Florida, USA

PostPosted: Sat 17 Aug 2019, 22:22    Post subject: Re: 64-bit Pups
Subject description: Cannot run in-built Wine progs nor add programs
 

davids45 wrote:
G'day version2013,

I have not had any luck with your Wine64-4.xx pet. It installs from the pet and will "winecfg" in a terminal.
Notepad will then open but no other in-built windows application starts (e.g. winemine).
Trying to install a Windows-based application program also gets no response.

I appreciate your stated problem with 64-bit testing on your machine, but can you get, say, winemine, running as a test? I see its .exe file in two sub-directories in windows, system32 and systemwow64. I don't know which is more likely to work.

David S.

I installed wine64-4.13_v4.1.pet into the puppy distro: tahr64-6.0.5.

(creates a 64bit prefix)
# WINEPREFIX=/mnt/home/temp/wine winecfg

# WINEPREFIX=/mnt/home/temp/wine wine notepad
# WINEPREFIX=/mnt/home/temp/wine wine64 notepad

# WINEPREFIX=/mnt/home/temp/wine wine winemine
# WINEPREFIX=/mnt/home/temp/wine wine64 winemine


(creates a 32bit prefix) wiki
# WINEARCH=win32 WINEPREFIX=/mnt/home/temp/wine32 winecfg

# WINEPREFIX=/mnt/home/temp/wine32 wine notepad
# WINEPREFIX=/mnt/home/temp/wine32 wine winemine

All commands above appear to function as expected.

As expected, this fails to function:
# WINEPREFIX=/mnt/home/temp/wine32 wine64 winemine

I am unsure exactly why your wine install is problematic.
Back to top
View user's profile Send private message Visit poster's website 
josejp2424


Joined: 01 Aug 2010
Posts: 520

PostPosted: Sun 18 Aug 2019, 13:55    Post subject: Re: Wine64-4.13
Subject description: Dpupbuster64
 

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

[wine-4.13 mirrors]

wine64-4.13_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.13.pet __________ tahrpup64 6.0.5
wine64_DOC-4.13.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.13_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.


hi version2013 .
I was testing on dpupbuster 64 and it works very well.
They will only need 32-bit libraries.

32bit_compatibilty_dpupbuster64

_________________
Shiba Inu | Pupjibaro jessie | My Blog
Back to top
View user's profile Send private message Visit poster's website 
josejp2424


Joined: 01 Aug 2010
Posts: 520

PostPosted: Sun 18 Aug 2019, 14:28    Post subject: MIME-types
Subject description: MIME-types
 

you must change the MIME-types
Code:
 /root/Choices/MIME-types/application_x-ms-dos-executable
.

the new puppy is in
Code:
/etc/xdg/rox.sourceforge.net/MIME-types


in root there is now a symbolic link from the MIME-types folder
and with its package it cancels the link, and the other MIME-type stops working.
I would advise that the application_x-ms-dos-executable script, ,
created by a pinstall.sh with that it would not delete the folder, and it would work on all puppies.

Something like this .

Code:
#!/bin/sh
echo "#!/bin/sh
exec wine "$@"
" >/root/Choices/MIME-types/application_x-ms-dos-executable && chmod +x /root/Choices/MIME-types/application_x-ms-dos-executable &

_________________
Shiba Inu | Pupjibaro jessie | My Blog
Back to top
View user's profile Send private message Visit poster's website 
version2013

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

PostPosted: Mon 26 Aug 2019, 21:58    Post subject: Re: MIME-types
Subject description: MIME-types
 

josejp2424 wrote:
you must change the MIME-types
Code:
 /root/Choices/MIME-types/application_x-ms-dos-executable
.

the new puppy is in
Code:
/etc/xdg/rox.sourceforge.net/MIME-types


in root there is now a symbolic link from the MIME-types folder
and with its package it cancels the link, and the other MIME-type stops working.
I would advise that the application_x-ms-dos-executable script, ,
created by a pinstall.sh with that it would not delete the folder, and it would work on all puppies.

Something like this .

Code:
#!/bin/sh
echo "#!/bin/sh
exec wine "$@"
" >/root/Choices/MIME-types/application_x-ms-dos-executable && chmod +x /root/Choices/MIME-types/application_x-ms-dos-executable &

Interesting that there are multiples locations MIME-types can be found in puppies:
/root/Choices/MIME-types/
/root/.config/rox.sourceforge.net/MIME-types/
/etc/xdg/rox.sourceforge.net/MIME-types/

In the few puppy distros I have looked in, these locations appear to be present in all of the them.

I thought the default behavior for installing/copying files would be to follow the symlinks, not overwrite them.

In future wine compiles, I can put the file 'application_x-ms-dos-executable' in /etc/xdg/rox.sourceforge.net/MIME-types/
Back to top
View user's profile Send private message Visit poster's website 
version2013

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

PostPosted: Fri 13 Sep 2019, 21:27    Post subject: wine-4.14  

My attempt at compiling wine-4.14

[wine-4.14 mirrors]

2.x failed to compile because of a bug

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

wine_DOC-4.14.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.14/
> _____wine-4.14_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, 21:58; 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: 455
Location: Florida, USA

PostPosted: Fri 13 Sep 2019, 21:27    Post subject: wine64-4.14  

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

[wine-4.14 mirrors]

wine64-4.14_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.14.pet __________ tahrpup64 6.0.5
wine64_DOC-4.14.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.14_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: 455
Location: Florida, USA

PostPosted: Tue 17 Sep 2019, 18:37    Post subject: wine-4.15  

My attempt at compiling wine-4.15

[wine-4.15 mirrors]

2.x failed to compile because of a bug

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

wine_DOC-4.15.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.15/
> _____wine-4.15_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, 21:59; 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: 455
Location: Florida, USA

PostPosted: Tue 17 Sep 2019, 18:38    Post subject: wine64-4.15  

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

[wine-4.15 mirrors]

wine64-4.15_v4.1.pet _________ tahrpup64 6.0.5 [stripped=true]
wine64_DEV-4.15.pet __________ tahrpup64 6.0.5
wine64_DOC-4.15.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.15_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: 455
Location: Florida, USA

PostPosted: Tue 01 Oct 2019, 18:27    Post subject: wine-4.16  

My attempt at compiling wine-4.16

[wine-4.16 mirrors]

2.x failed to compile because of a bug

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

wine_DOC-4.16.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.16/
> _____wine-4.16_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, 21:59; edited 1 time in total
Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 26 of 27 [401 Posts]   Goto page: Previous 1, 2, 3, ..., 24, 25, 26, 27 Next
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.1456s ][ Queries: 12 (0.0555s) ][ GZIP on ]