Jump to content

  • Log in with Facebook Log in with Twitter Log In with Google      Sign In   
  • Create Account

Wine STAGING & CSMT Builds - Engines Available


  • Please log in to reply
664 replies to this topic

#121 Slice

Slice

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 305 posts
  • Graphics Card:AMD Radeon HD6670, GTX650
  • Operating System:OS X 10.11 (El Capitan)
  • I like to play:Heroes III
    4x4 Evolution
    made Heroes VI working!

Posted 15 June 2015 - 09:13 AM

View Postjtnix, on 15 June 2015 - 02:26 AM, said:

A quick update: I was able to get Wine-Staging to compile on OS X 10.10.3 - I believe it was because I had tried from the latest git master on June 3rd, instead of grabbing an official release. After I started from the official Wine Staging 1.7.44, everything compiled fine - I used the 10.8 SDK to be sure as I saw it was suggested to be necessary.

The only issue I notice so far is:

err:menubuilder:convert_to_native_icon error 0x80004005 getting frame 0
libpng warning: Application was compiled with png.h from libpng-1.6.14
libpng warning: Application  is  running with png.c from libpng-1.4.11
libpng warning: Incompatible libpng version in application and library


I used normal Wineskin to compile with build script only altered to use native gcc (6.1.0 LLVM for clang) and pipes.  So I am thinking it is using the 10.8 SDK headers but defaulting to the included X11 C library at build time?  Or how else could an older library would be visible like that?

Other than that it is a dream with SWTOR and the Everquests, and it's the best Neverwinter Online has looked yet!
See headers in WIneskin engine base. It contains libpng 14 with headers.

#122 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 15 June 2015 - 09:57 AM

View PostSlice, on 15 June 2015 - 08:56 AM, said:

Look into sources /include/config.h
this file is autogenerated during compilation.
Search the library libtxc_dxtn.
What will you find?
1. "libtxc_dxtn.so"
2. "libtxc_dxtn.dylib"
3. "not found"
4. something else?
for example
I tried now to watch  at latest wine-patched-master folder of staging for linux...

In the "include" folder  the only file named as "config" is the file "config.h.in"

If I search in it the "libtxc_dxtn" string, the only line that it found is this:

http://s3.postimg.or...trfamb/info.png

Posted Image


so how this info could help me to understand what? :huh:

#123 Slice

Slice

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 305 posts
  • Graphics Card:AMD Radeon HD6670, GTX650
  • Operating System:OS X 10.11 (El Capitan)
  • I like to play:Heroes III
    4x4 Evolution
    made Heroes VI working!

Posted 15 June 2015 - 06:41 PM

View PostNRG90, on 15 June 2015 - 09:57 AM, said:

for example
I tried now to watch  at latest wine-patched-master folder of staging for linux...

In the "include" folder  the only file named as "config" is the file "config.h.in"

If I search in it the "libtxc_dxtn" string, the only line that it found is this:

http://s3.postimg.or...trfamb/info.png




so how this info could help me to understand what? :huh:
It means you never compiled wine-stage by yourself?
/* include/config.h.  Generated from config.h.in by configure.  */
/* include/config.h.in.  Generated from configure.ac by autoheader.  */


#124 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 15 June 2015 - 08:19 PM

View PostSlice, on 15 June 2015 - 06:41 PM, said:

It means you never compiled wine-stage by yourself?
/* include/config.h.  Generated from config.h.in by configure.  */
/* include/config.h.in.  Generated from configure.ac by autoheader.  */

I  compiled 1.7.44-STAGING and 1.7.45-STAGING with the same metod that Gurqn ,the autor of this tread, explained  at the first post, downloading the full patched wine staging for linux and compiling it with wineskin build engine and SDK 8...

What is wrong in that?!?  :mellow:


Before that, I had never compiled anything ... :wub:

#125 Slice

Slice

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 305 posts
  • Graphics Card:AMD Radeon HD6670, GTX650
  • Operating System:OS X 10.11 (El Capitan)
  • I like to play:Heroes III
    4x4 Evolution
    made Heroes VI working!

Posted 16 June 2015 - 04:09 AM

I said you to look onto include/config.h
The file will appear only after compilation.

#126 Slice

Slice

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 305 posts
  • Graphics Card:AMD Radeon HD6670, GTX650
  • Operating System:OS X 10.11 (El Capitan)
  • I like to play:Heroes III
    4x4 Evolution
    made Heroes VI working!

Posted 16 June 2015 - 06:56 AM

With wine-staging in MacOSX you should see the message
fixme:d3d:wined3d_dxtn_init Wine cannot find the txc_dxtn library, DXTn software support unavailable.
It works only in Linux

#127 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 16 June 2015 - 07:57 AM

View PostSlice, on 16 June 2015 - 04:09 AM, said:

I said you to look onto include/config.h
The file will appear only after compilation.
Sorry Slice, but with my poor English it's  difficult to understand for me...
You told me to look in source file... So I taken the linux source folder  of full patched staging (wine-patched-master), before compiling it for mac os x... and this source folder only contains  include/config.h.in... After I compiled it for  mac by wineskin build engine I obtain the compressed file of the engine (WS9Wine1.7.45-STAGING.tar.7z) and I don't know where to find the config.h file...

#128 Slice

Slice

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 305 posts
  • Graphics Card:AMD Radeon HD6670, GTX650
  • Operating System:OS X 10.11 (El Capitan)
  • I like to play:Heroes III
    4x4 Evolution
    made Heroes VI working!

Posted 16 June 2015 - 10:08 AM

View PostNRG90, on 16 June 2015 - 07:57 AM, said:

Sorry Slice, but with my poor English it's  difficult to understand for me...
You told me to look in source file... So I taken the linux source folder  of full patched staging (wine-patched-master), before compiling it for mac os x... and this source folder only contains  include/config.h.in... After I compiled it for  mac by wineskin build engine I obtain the compressed file of the engine (WS9Wine1.7.45-STAGING.tar.7z) and I don't know where to find the config.h file...
When you compile by wineskin winery you must point to source folder where your sources located.
For example /User/xxx/wine/
In this folder you have to look for folder include/

#129 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 16 June 2015 - 10:27 AM

View PostSlice, on 16 June 2015 - 10:08 AM, said:

When you compile by wineskin winery you must point to source folder where your sources located.
For example /User/xxx/wine/
In this folder you have to look for folder include/


I decompressed my source folder on my desktop and as I said it's named "wine-patched-master"; you can download it directly from here...
So this is the folder that I point into wineskin winery to build staging engine for mac...
Posted Image



and as I said it contains the  folder "include" , but not "config.h" file, while it contains "config.h.in"... You can check by yourself:

https://github.com/w...io/wine-patched


View Postmanky1, on 23 February 2015 - 09:48 PM, said:

I have downloaded the latest Wine Staging version from the location below.

https://github.com/w...io/wine-patched

This is the full Wine Staging version 1.7.xx, not just the patches. It compiled fine using Wineskin Winery's 'Custom build an engine' option ....
The engine works well for me. I have tried Train Simulator 2015 and World of Subways 3 and both run well.


#130 Slice

Slice

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 305 posts
  • Graphics Card:AMD Radeon HD6670, GTX650
  • Operating System:OS X 10.11 (El Capitan)
  • I like to play:Heroes III
    4x4 Evolution
    made Heroes VI working!

Posted 16 June 2015 - 11:20 AM

View PostNRG90, on 16 June 2015 - 10:27 AM, said:

I decompressed my source folder on my desktop and as I said it's named "wine-patched-master"; you can download it directly from here...
So this is the folder that I point into wineskin winery to build staging engine for mac...
Posted Image



and as I said it contains the  folder "include" , but not "config.h" file, while it contains "config.h.in"... You can check by yourself:

https://github.com/w...io/wine-patched
Yes, it is not containing the file config.h UNTIL you make compilation.
Press "BUILD" and then look the folder again.

#131 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 16 June 2015 - 12:35 PM

View PostSlice, on 16 June 2015 - 11:20 AM, said:

Yes, it is not containing the file config.h UNTIL you make compilation.
Press "BUILD" and then look the folder again.

that is, to have information for the purpose of a good compilation for mac, I must first compile it (25-30minutes)  ?!? :huh:


View PostSlice, on 15 June 2015 - 08:56 AM, said:

Look into sources /include/config.h
this file is autogenerated during compilation.
Search the library libtxc_dxtn.
What will you find?
1. "libtxc_dxtn.so"
2. "libtxc_dxtn.dylib"
3. "not found"
4. something else?

Could me explain what is the point for each one of these 4 points?

#132 dankoB

dankoB

    Legendary Member

  • Super Moderators
  • 3011 posts
  • LocationNew Brunswick, Canada
  • Graphics Card:MacBook Pro 11,3
    Core i7 16GB
    NVIDIA GeForce GT 750M
    2GB GDDR5 vRAM
  • Operating System:macOS 10.12 (Sierra)
  • I like to play:la rockitar
Author

Posted 16 June 2015 - 03:12 PM

View PostNRG90, on 16 June 2015 - 12:35 PM, said:



that is, to have information for the purpose of a good compilation for mac, I must first compile it (25-30minutes)  ?!? :huh:

View PostSlice, on 15 June 2015 - 08:56 AM, said:

Look into sources /include/config.h
this file is autogenerated during compilation.
Search the library libtxc_dxtn.
What will you find?
1. "libtxc_dxtn.so"
2. "libtxc_dxtn.dylib"
3. "not found"
4. something else?


Could me explain what is the point for each one of these 4 points?


Those are the Unix version of the S3 Texture Compression (DXTn) libraries...as for how they work, or an explanation on how Wine uses them? No idea.

https://en.wikipedia...ure_Compression

Compiling the engine is only half of the task I believe. The files will be created before the build starts.

You should see this about two to three minutes after the Wineskin Winery "BUILD" process starts...which includes the configuration of the files, the compiling, and then the actual build and then .bundle packaging process.

Posted Image
free image uploader

#133 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 16 June 2015 - 03:39 PM

Hi DankoB, I restarted compiling latest patched staging and after one minute the file config.h it's generated, so I stopped the compiling and I explored it; when I searched libtxc_dxtn in this file, the only response I obtained is the same I had in config.h.in file:

Posted Image

So how can I use this info?!? :mellow:

View PostSlice, on 15 June 2015 - 08:56 AM, said:

Look into sources /include/config.h
this file is autogenerated during compilation.
Search the library libtxc_dxtn.
What will you find?
1. "libtxc_dxtn.so"
2. "libtxc_dxtn.dylib"
3. "not found"
4. something else?


#134 dankoB

dankoB

    Legendary Member

  • Super Moderators
  • 3011 posts
  • LocationNew Brunswick, Canada
  • Graphics Card:MacBook Pro 11,3
    Core i7 16GB
    NVIDIA GeForce GT 750M
    2GB GDDR5 vRAM
  • Operating System:macOS 10.12 (Sierra)
  • I like to play:la rockitar
Author

Posted 16 June 2015 - 04:37 PM

I'm really not sure...I believe that library can only be built on linux. That's why the option is greyed out in the Staging WineCfg.

edit***Oh wait...you are building on linux aren't you

I have 0 linux experience.

***edit again...sorry, I was mistaking DXTn for DXVA2 in the WineCfg

#135 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 16 June 2015 - 05:04 PM

View PostDankoB, on 16 June 2015 - 04:37 PM, said:

I'm really not sure...I believe that library can only be built on linux. That's why the option is greyed out in the Staging WineCfg.

edit***Oh wait...you are building on linux aren't you

I have 0 linux experience.

***edit again...sorry, I was mistaking DXTn for DXVA2 in the WineCfg

no no I'm building on OS X by wineskin... I used only the source patched on linux by the STAGING TEAM...

#136 dankoB

dankoB

    Legendary Member

  • Super Moderators
  • 3011 posts
  • LocationNew Brunswick, Canada
  • Graphics Card:MacBook Pro 11,3
    Core i7 16GB
    NVIDIA GeForce GT 750M
    2GB GDDR5 vRAM
  • Operating System:macOS 10.12 (Sierra)
  • I like to play:la rockitar
Author

Posted 16 June 2015 - 05:17 PM

Yeah, okay...The icon in the top of the window kind of threw me off and I thought you may have had some sort of Mac theme installed.   :rolleyes:

View PostNRG90, on 15 June 2015 - 09:57 AM, said:


I can't remember any specifics, but when it was first being implemented into Wine I believe that OSX support was being left out because they wanted to build a stable version on one or two specific distributions to verify stability before implementing it throughout all distros.

I could be completely wrong about it...but I did come across this project, https://github.com/BKcore/crunch-osx ....So I assume it is possible on OS X.

I'm sure Slice could give you a much more accurate response.

#137 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 16 June 2015 - 06:09 PM

View PostDankoB, on 16 June 2015 - 05:17 PM, said:

.The icon in the top of the window kind of threw me off and I thought you may have had some sort of Mac theme installed.   :rolleyes:
It's the icon of the app I used to open config.h file:
http://macromates.com/
I use textmate to open many text files
  


View PostDankoB, on 16 June 2015 - 05:17 PM, said:

I can't remember any specifics, but when it was first being implemented into Wine I believe that OSX support was being left out because they wanted to build a stable version on one or two specific distributions to verify stability before implementing it throughout all distros.

I could be completely wrong about it...but I did come across this project, https://github.com/BKcore/crunch-osx ....So I assume it is possible on OS X.

I'm sure Slice could give you a much more accurate response.

I hope so, so far I have not understood anything,  :unsure:   nor as to why I had to look for that string nor on why I should use the information received from the config.h file

#138 dankoB

dankoB

    Legendary Member

  • Super Moderators
  • 3011 posts
  • LocationNew Brunswick, Canada
  • Graphics Card:MacBook Pro 11,3
    Core i7 16GB
    NVIDIA GeForce GT 750M
    2GB GDDR5 vRAM
  • Operating System:macOS 10.12 (Sierra)
  • I like to play:la rockitar
Author

Posted 16 June 2015 - 08:52 PM

If I'm not mistaken, there are source files that Slice used to compile DXTn support into the libraries he's been building to unofficially update Wineskin for us. The compilation of his source file, config.h.in (or whichever source files are included), placed into the Staging source would produce an entry in config.h that would provide a message similar to:

[code]/* Define to the soname of the libtxc_dxtn library. */
#define SONAME_LIBTXC_DXTN "libtxc_dxtn.dylib"

...but unfortunately yours is coming up as undefined, although the build knows to look for the source files, they simply aren't there to be compiled into the build.

@Slice,
Unless you are referring to simply renaming libtxc_dxtn.dylib to libtxc_dxtn.so and simply placing it into the wswine.build. I have used this method by renaming the .so file to .dll in order to simplify an issue but I don't know how the libraries are implemented into the wrapper and how they interact with the hardware.

#139 jtnix

jtnix

    Experienced Member

  • Members
  • PipPip
  • 44 posts
  • LocationUSA
  • Graphics Card:10.11.6: AMD Radeon R9 M295X 4G Retina 27
    10.11.5: AMD 6750M 512M MBP 15
  • Operating System:Other OS/Not specified
  • I like to play:Star Wars: The Old Republic, Everquest, Everquest II, Neverwinter Online

Posted 16 June 2015 - 09:12 PM

Doh! I completely missed the WrapperUpdate.zip - I wrongly assumed they were part of the engine updates you were sending.  

After I got that missing piece the rest was easy to update my own staging builds:

1. Copied the libpng.16.16 and libtxc_dxtn dylib files from your WrapperUpdate on previous page into my Library/Application Support/Wineskin/EngineBase/W2.5.5v1EngineBase/lib folder
2. Built a new Wine engine from my patched 1.7.44 staging src folder using Wineskin
3. Switched to new engine using Wineskin inside my SWTOR Wineskin package
4. Then I had to do the step you referenced earlier, which was to copy the same dylibs from your WrapperUpdate into the Contents/Frameworks/ folder of my SWTOR Wineskin package  

I *think* this last step could also be fixed by using the Advanced Wineskin setup tool feature: Update Wrapper.  My assumption is that Update Wrapper would synchronize any libraries and other files with what is contained from the selected EngineBase, but I have not tested this yet.  This is wrong, check my next post for update on how to get Update Wrapper to update with new dylibs, too.

These steps allowed my wrapper to see the new dylibs and use the new png16 c code as well as the libtxc_dxtn features, which I verified in the log output.

#140 jtnix

jtnix

    Experienced Member

  • Members
  • PipPip
  • 44 posts
  • LocationUSA
  • Graphics Card:10.11.6: AMD Radeon R9 M295X 4G Retina 27
    10.11.5: AMD 6750M 512M MBP 15
  • Operating System:Other OS/Not specified
  • I like to play:Star Wars: The Old Republic, Everquest, Everquest II, Neverwinter Online

Posted 16 June 2015 - 09:38 PM

I realized I had a duplicate of the same package on my external HD, so I tried my Update Wrapper Wineskin option to see what happens, and was wrong in my assumption before.   We also must copy the same dylib files you want in your new Wrappers into your Library/Application Support/Wineskin/Wrappers/2.6.0/Contents/Frameworks folder as this is the folder that is copied to all new wrapper Contents/Frameworks folders.  The EngineBase lib folder is library reference for new engine builds only, so you need to copy your dylibs to both locations for fully automated Wineskin build and deployment sweetness.

The only thing I had to do is confirm not once, but twice (smart!) before updating the Wrapper.  I knew I had the 2.6.0 wrapper on my existing wrapper, so I wasn't put off by the warnings - full steam ahead!  And then the Update Wrapper option worked, copying the new dylib files into my wrapper as well.  Success!

#141 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 17 June 2015 - 06:16 AM

View Postjtnix, on 16 June 2015 - 09:12 PM, said:

Doh! I completely missed the WrapperUpdate.zip - I wrongly assumed they were part of the engine updates you were sending.  

After I got that missing piece the rest was easy to update my own staging builds:

1. Copied the libpng.16.16 and libtxc_dxtn dylib files from your WrapperUpdate on previous page into my Library/Application Support/Wineskin/EngineBase/W2.5.5v1EngineBase/lib folder
2. Built a new Wine engine from my patched 1.7.44 staging src folder using Wineskin
3. Switched to new engine using Wineskin inside my SWTOR Wineskin package
4. Then I had to do the step you referenced earlier, which was to copy the same dylibs from your WrapperUpdate into the Contents/Frameworks/ folder of my SWTOR Wineskin package  

These steps allowed my wrapper to see the new dylibs and use the new png16 c code as well as the libtxc_dxtn features, which I verified in the log output.

View Postjtnix, on 16 June 2015 - 09:38 PM, said:

   We also must copy the same dylib files you want in your new Wrappers into your Library/Application Support/Wineskin/Wrappers/2.6.0/Contents/Frameworks folder as this is the folder that is copied to all new wrapper Contents/Frameworks folders.  The EngineBase lib folder is library reference for new engine builds only, so you need to copy your dylibs to both locations for fully automated Wineskin build and deployment sweetness.

Now It's more comprensible (I hope) why slice told me those things... Thank's jtnix...



What I want to be clear in this tread, Where do I want to replicate the unaltered versions STAGING made for linux, is how can I make sure that all the features and patches for linux are loaded also on OS X ...

For this purpose, then does it's best to compile any new Staging engine with "all" the libraries contained in the collection of Slice (WrapperUpdate) already copied into the two paths?

Library/Application Support/Wineskin/EngineBase/W2.5.5v1EngineBase/lib

Library/Application Support/Wineskin/Wrappers/2.6.0/Contents/Frameworks


In doing so, will,  each new engine that we build in the future, be fully complete and identical to the linux counterparty  and ready to be loaded without any problems in each new wrapper ?!?

Quote

/* Define to the soname of the libtxc_dxtn library. */
#define SONAME_LIBTXC_DXTN "libtxc_dxtn.dylib"

...but unfortunately yours is coming up as undefined, although the build knows to look for the source files, they simply aren't there to be compiled into the build.


Yes That 's right:

Posted Image

#142 Slice

Slice

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 305 posts
  • Graphics Card:AMD Radeon HD6670, GTX650
  • Operating System:OS X 10.11 (El Capitan)
  • I like to play:Heroes III
    4x4 Evolution
    made Heroes VI working!

Posted 17 June 2015 - 07:48 AM

At the begin of the discussion I wanted to show you that unmodified WineStage+unmodified Wrapper == not success because WIneStage is developed and supported for linux and developers didn't care about MacOSX specific problems.
See bugs 25486, 29586, 14939, 29598 for DXTn absent support.
It's a pity using my version of libtxc_dxtn with pure WineStage also in not full solution. See what you have
"   libtxc_dxtn (compatibility....)"
this is wrong. It must be a file name  without comments "libtxc_dxtn.dylib", no spaces, no version, no braces.
Check LastWineRun.log for messages about this library.

libtxc_dxt.dylib != libtxc_dxtn.so because of different compilation flags. In original sources flag "-dynamic" is absent.

I don't know how to correct configure.ac to create more correct file name so I did compilation in two steps.
First for configure and creating config.h
Second edit config.h and final build.

In my project Sherry I decided just embed this library at source level so I need no more this dylib.
Wine developer can't accept DXTn support because they afraid license problem. I account there in no problem.

#143 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 17 June 2015 - 02:16 PM

View PostSlice, on 17 June 2015 - 07:48 AM, said:

... It must be a file name  without comments "libtxc_dxtn.dylib", no spaces, no version, no braces.
Check LastWineRun.log for messages about this library.

libtxc_dxt.dylib != libtxc_dxtn.so because of different compilation flags. In original sources flag "-dynamic" is absent.

I don't know how to correct configure.ac to create more correct file name so I did compilation in two steps.

First for configure and creating config.h
Second edit config.h and final build.

Once again my bad English did not make me understand a lot ... :)

Thinking of doing as you wrote in step 2, I hand wrote the right name in the file config.h

/* Define to the soname of the libtxc_dxtn library. */
#define SONAME_LIBTXC_DXTN "libtxc_dxtn.dylib"

and then compiled the engine...
Before that, I copied libtxc_dxtn.dylib in the two paths written above by @jtnix  :

Quote

Library/Application Support/Wineskin/EngineBase/W2.5.5v1EngineBase/lib

Library/Application Support/Wineskin/Wrappers/2.6.0/Contents/Frameworks



After that I tried the engine so builded and my  LastRunWine.log  file give me this:

fixme:d3d:wined3d_dxtn_init Wine cannot find the txc_dxtn library, DXTn software support unavailable.
and also
err:avicap:query_video_device Video 4 Linux support not enabled

The game worked but probably It didn't need to use DXTn... However the same wineskin does not seem to use it ...

View PostSlice, on 17 June 2015 - 07:48 AM, said:

... I decided just embed this library at source level so I need no more this dylib.

How can we  replicate this?!?

#144 jtnix

jtnix

    Experienced Member

  • Members
  • PipPip
  • 44 posts
  • LocationUSA
  • Graphics Card:10.11.6: AMD Radeon R9 M295X 4G Retina 27
    10.11.5: AMD 6750M 512M MBP 15
  • Operating System:Other OS/Not specified
  • I like to play:Star Wars: The Old Republic, Everquest, Everquest II, Neverwinter Online

Posted 18 June 2015 - 03:16 AM

View PostSlice, on 17 June 2015 - 07:48 AM, said:

At the begin of the discussion I wanted to show you that unmodified WineStage+unmodified Wrapper == not success because WIneStage is developed and supported for linux and developers didn't care about MacOSX specific problems.
See bugs 25486, 29586, 14939, 29598 for DXTn absent support.
It's a pity using my version of libtxc_dxtn with pure WineStage also in not full solution. See what you have
"   libtxc_dxtn (compatibility....)"
this is wrong. It must be a file name  without comments "libtxc_dxtn.dylib", no spaces, no version, no braces.

I don't know how to correct configure.ac to create more correct file name so I did compilation in two steps.
First for configure and creating config.h
Second edit config.h and final build.

Ahh, I see what you mean.  The configure script has quite a funky little sed replace script trying to extract the dylib name from the actual library itself - very strange.  I wrote a simple patch for the configure script so I could keep using the Wineskin Build Engine feature.  Of course this is not the best solution, but here is the patch anyway if someone is interested:
Spoiler

Put that in a file
wine-staging-1.7.44-libtxc_dxtn_configure.patch
in your wine staging src folder (made for 1.7.44 staging release, but will probably work on other recent staging versions) and then run
patch -p1 < wine-staging-1.7.44-libtxc_dxtn_configure.patch

I also noticed that I had to overwrite the libpng.dylib link in the EngineBase Frameworks folder to the new libpng.16.16.dylib I placed in there, or the compile would not link the correct library, despite being explicitly declared in the created config.h !  

I wish I could get my darn linker to create a .dylib for libtxc_dxtn.  I have libtxc_dxtn compiling to an .so no problem, but no matter seemingly where or how I add the -dynamiclib flag to CFLAGS CPPFLAGS or CXXFLAGS, it has no effect, even after
make distclean
.  Slice, I know you mentioned the flag '-dynamic' and I tried that too, but all the online references I've found say to use -dynamiclib.  Either way - I get no .dylib build love. =(

Happy to use yours, though - I just played a few missions in Everquest II and it is the smoothest yet - no libtxc_dxtn or libpng errors in the log file!  Thanks for the WrapperUpdate!!

#145 Slice

Slice

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 305 posts
  • Graphics Card:AMD Radeon HD6670, GTX650
  • Operating System:OS X 10.11 (El Capitan)
  • I like to play:Heroes III
    4x4 Evolution
    made Heroes VI working!

Posted 18 June 2015 - 06:46 AM

Great you patch the configure script!

About libtxc_dxtn compilation I did the follow
#!/bin/sh
CC -m32 -c -fPIC -o txc_compress_dxtn.o txc_compress_dxtn.c -arch i386 -Os -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk -mmacosx-version-min=10.6 -I/opt/Wineskin/include -I/opt/local/include

CC -m32 -c -fPIC -o txc_fetch_dxtn.o txc_fetch_dxtn.c -arch i386 -Os -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk -mmacosx-version-min=10.6 -I/opt/Wineskin/include -I/opt/local/include

CC -arch i386 -dynamiclib -o libtxc_dxtn.dylib txc_compress_dxtn.o txc_fetch_dxtn.o

To reproduce my sources I can share diff sherry vs wine-hq but older version. It contains all stage patches as well.
https://www.dropbox....05.txt.zip?dl=0
It can be applied to newer version but then I afraid manual corrections needed.
More recent sources are not ready for release.

#146 dankoB

dankoB

    Legendary Member

  • Super Moderators
  • 3011 posts
  • LocationNew Brunswick, Canada
  • Graphics Card:MacBook Pro 11,3
    Core i7 16GB
    NVIDIA GeForce GT 750M
    2GB GDDR5 vRAM
  • Operating System:macOS 10.12 (Sierra)
  • I like to play:la rockitar
Author

Posted 18 June 2015 - 01:36 PM

I'm pretty excited for the most recent work you've been doing. Thanks for joining our community Slice!

#147 jtnix

jtnix

    Experienced Member

  • Members
  • PipPip
  • 44 posts
  • LocationUSA
  • Graphics Card:10.11.6: AMD Radeon R9 M295X 4G Retina 27
    10.11.5: AMD 6750M 512M MBP 15
  • Operating System:Other OS/Not specified
  • I like to play:Star Wars: The Old Republic, Everquest, Everquest II, Neverwinter Online

Posted 18 June 2015 - 03:21 PM

I'm going to 2nd that shout out to Slice, without your persistence in your Sherry project, I would not have had the guts to keep working on my own Wineskin Engine to success!  Thanks for sharing your work!!

Also, Slice, can I post your libtxc_dxtn.dylib and libpng16.16.dylib to my public github to share with others when used in my own Engines?  I will of course give you full credit!

#148 jtnix

jtnix

    Experienced Member

  • Members
  • PipPip
  • 44 posts
  • LocationUSA
  • Graphics Card:10.11.6: AMD Radeon R9 M295X 4G Retina 27
    10.11.5: AMD 6750M 512M MBP 15
  • Operating System:Other OS/Not specified
  • I like to play:Star Wars: The Old Republic, Everquest, Everquest II, Neverwinter Online

Posted 19 June 2015 - 01:50 PM

Slice, thanks for those manual compile instructions.  I was trying to use CFLAGS, etc and the provided configure script with libtxc_dxtn but that obviously didn't work.

I used your instructions but compiled against the 10.8 SDK and GL headers, and it produced the exact same .dylib as yours, so there obviously isn't much going on in there that is depending on the ext linked libs.  

Did you have to manually compile every one of your WrapperUpdate dylib files? Or did some / most of them work with CFLAGS having -dynamiclib in there and produce a .dylib file along with so, etc.?  My guess is it has to do with the -o flag specifying the .dylib ext and the configure script just doesn't understand that OS X nuance.

Thanks, Jt

#149 Slice

Slice

    Veteran Member

  • Members
  • PipPipPipPipPip
  • 305 posts
  • Graphics Card:AMD Radeon HD6670, GTX650
  • Operating System:OS X 10.11 (El Capitan)
  • I like to play:Heroes III
    4x4 Evolution
    made Heroes VI working!

Posted 19 June 2015 - 02:11 PM

I made these dylibs by MacPort, not manual compilation. Except libtxc_dxt which I need no more as it included into Sherry. Included as sources.
No problem if you share these libraries with other users. Its have no relation to me. I just collect them.

#150 NRG

NRG

    Champion Member

  • Members
  • 679 posts
  • Graphics Card:Nvidia 9800m GTS
  • Operating System:OS X 10.10 (Yosemite)

Posted 29 June 2015 - 09:49 AM

NEWS!

Quote

from  Wine Staging Team


Mac OS X

Starting with Wine Staging 1.7.46 we provide prebuilt packages for Mac OS X 10.8+.
Those packages should be considered as beta version for now. They contain only the Wine files including the native winemac driver (+ dependencies), but no graphical tools for Wine prefix management. For now it is necessary to manually download and install the new package on each new release. We might implement an auto updater in the future.

In order to use the package, you first need to install XQuartz 2.7.7 or higher. This is necessary because various binaries are linked against libraries from the XQuartz package.

To install Wine Staging simply grab the latest .pkg from our repository and run the installer. The files will be placed under /opt/wine-staging. You may want to run /opt/wine-staging/bin/wine --check-libs after the installation to make sure that all necessary dependencies can be found (except libnetapi and libodbc which are not essential).
For more information about how to use Wine Staging please refer to our Usage Wiki page.




Release 1.7.46

Wine Staging Team - Sun, 28 Jun 2015


In the past two weeks we improved the Mac OS X compatibility and worked on upstreaming patches.
Most of the Wine Staging developers and contributors use Wine on Linux based systems. This leads to the problem that some features are not directly available or might contain bugs on other unix based systems. This release however focuses mostly on Mac OS X. We fixed several smaller bugs and issues regarding cross compiling and the loading of libraries. Besides code fixes, we now also provide prebuilt packages for Mac OS X 10.8+. Further information can be found in the installation instructions.
Besides the Mac OS X work, we got 28 patches upstream and added the following features: As usual you can find all the changes in our changelog.



Unfortunately, all this can only be used as Wine (without wrapper) because the package is not compiled for Wineskin ... I Tried to compile the package for linux in the the usual way  and I got this error:

Posted Image

there is a way to find and compile it with a libXcursor.dylib library?


EDIT: I tried to compile it with --without-xcursor argument, but now others errors come:

Spoiler

and next also this:

Spoiler

and then these:

Spoiler


Spoiler





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users