Jump to content

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

Video How to build Custom Engines With Wineskin


  • Please log in to reply
19 replies to this topic

#1 soloMacOSX

soloMacOSX

    Regular Member

  • Members
  • Pip
  • 19 posts
  • Graphics Card:NVidia9400M
  • Operating System:OS X 10.8 (Mountain Lion)

Posted 27 November 2016 - 06:37 AM

Hi, currently i'm using El Capitan but I haven't got how to create custom engines with new wine sources through wineskin.

I've followed tutorials which explain how to compile my own engines, but I haven't got success.

- I've installed de sdks correctly
- I've installed gcc 4.2

But when I will compile a new wine source, I can't. Wineskin gets the error that gcc 4.2 not found. I tried many solutions but I couldn't solve it.

Someone with many experience in the management of wineskin, could make a video and upload it in youtube on how to configure wineskin? and also showing which third party software is needed to install to create custom engines? It would be very useful and will help to grow this community of testers. I've seen that some users of wineskin have created custom engines, and also stagin engines so it will be a great help for new testers.

Currently I'm a wineskin user but sometimes I feel limited because I can't build custom engines to add patches and custom configurations.

I hope for soon answer.

Thanks!!
More tutorials in english about Wineskin on soloMacOSX Youtube

#2 ScoPezz

ScoPezz

    Professional Member

  • Members
  • PipPipPipPip
  • 141 posts
  • LocationBelgium
  • Graphics Card:Intel GMA X3100
  • Operating System:Mac OS X 10.7 (Lion)

Posted 27 November 2016 - 09:20 PM

El Capitan has SIP (google it) which needs to be disabled to be able to build wineskin engines.

Use this tutorial (written by me): http://portingkit.co...php?topic=289.0

#3 ovvldc

ovvldc

    Master Member

  • Members
  • 1,072 posts
  • Graphics Card:Intel HD5000
  • Operating System:macOS 10.12 (Sierra)
  • I like to play:stories

Posted 28 November 2016 - 09:29 AM

I don't see why this should be needed. Nothing in using a Wine engine requires the changing of system files, and neither should building one. It sounds more like the build process is very messy in some way.

#4 ScoPezz

ScoPezz

    Professional Member

  • Members
  • PipPipPipPip
  • 141 posts
  • LocationBelgium
  • Graphics Card:Intel GMA X3100
  • Operating System:Mac OS X 10.7 (Lion)

Posted 28 November 2016 - 01:08 PM

View Postovvldc, on 28 November 2016 - 09:29 AM, said:

I don't see why this should be needed. Nothing in using a Wine engine requires the changing of system files, and neither should building one. It sounds more like the build process is very messy in some way.

I had the same errors that this user had. I tried without disabling SIP and just modifying the minimumsdk plist, but it didn't work. It only worked when disabling SIP. Don't ask my why, but it did. I did a lot of research on this.

#5 Zakk

Zakk

    Lurker

  • Members
  • 2 posts
  • Graphics Card:Nvidia 650M
  • Operating System:OS X 10.8 (Mountain Lion)

Posted 01 December 2016 - 12:18 PM

The build process is very messy. People are probably running afoul of SIP when the build script tries to install gcc-4.2 into /usr.

The solution is to either 1) install it somewhere else, 2) install ALL of it into /usr/local (which is exempt from SIP) or 3) just build with the apple provided compiler

#6 ovvldc

ovvldc

    Master Member

  • Members
  • 1,072 posts
  • Graphics Card:Intel HD5000
  • Operating System:macOS 10.12 (Sierra)
  • I like to play:stories

Posted 01 December 2016 - 12:29 PM

I assume that this is a feature of the build script that doh123 developed. Made sense at the time but is now overtaken by events, etc.

#7 soloMacOSX

soloMacOSX

    Regular Member

  • Members
  • Pip
  • 19 posts
  • Graphics Card:NVidia9400M
  • Operating System:OS X 10.8 (Mountain Lion)

Posted 15 December 2016 - 06:02 PM

Hi ScoPezz thanks for your answer. Indeed your guide was the guide that I had followed before I posted this discussion about how to build wineskin engines. It's the error I get after following al the steps and compiling a new engine. I've tried with different wine sources, but still I'm having the same problem. Here is an image with the error.

Posted Image

¿Is there a solution for this problem? I hope for soon answer.

Thanks for your support.
More tutorials in english about Wineskin on soloMacOSX Youtube

#8 ScoPezz

ScoPezz

    Professional Member

  • Members
  • PipPipPipPip
  • 141 posts
  • LocationBelgium
  • Graphics Card:Intel GMA X3100
  • Operating System:Mac OS X 10.7 (Lion)

Posted 15 December 2016 - 08:01 PM

View PostsoloMacOSX, on 15 December 2016 - 06:02 PM, said:

Hi ScoPezz thanks for your answer. Indeed your guide was the guide that I had followed before I posted this discussion about how to build wineskin engines. It's the error I get after following al the steps and compiling a new engine. I've tried with different wine sources, but still I'm having the same problem. Here is an image with the error.



¿Is there a solution for this problem? I hope for soon answer.

Thanks for your support.

It could be that your libs/compiler is broken. Maybe because of Homebrew or Macports.
Because it says your installed gcc version cannot be used.
So I suspect you have a custom installed version, which is messing with the version needed for Wineskin.

#9 doh123

doh123

    Wineskin Developer

  • Members
  • 4,279 posts
  • LocationOver here
  • Graphics Card:Geforce GT 650M, Intel HD 4000, Radeon 6750, Intel HD 3000, Geforce 320m (in 3 machines)
  • Operating System:OS X 10.8 (Mountain Lion)
  • I like to play:RPG and Strategy

Posted 16 December 2016 - 12:46 AM

The script wants to use Apples old gcc 4.2 (back before Apple dumped gcc), which is built to run from locations that require it... It may be the Xcode thing I mentioned in the other thread, or just SIP.

You could modify the build script where it sets what gcc executable to use to point to some other compiler you have...

#10 soloMacOSX

soloMacOSX

    Regular Member

  • Members
  • Pip
  • 19 posts
  • Graphics Card:NVidia9400M
  • Operating System:OS X 10.8 (Mountain Lion)

Posted 17 December 2016 - 05:04 AM

I have installed gcc on my mac, it's a screenshot with my version of gcc

Posted Image
I have read, that the error "checking whether the c compiler works... no" is due to I have not run gcc on my mac and agreed with it's terms of license. Which command I need to use to run gcc from the terminal?
More tutorials in english about Wineskin on soloMacOSX Youtube

#11 ovvldc

ovvldc

    Master Member

  • Members
  • 1,072 posts
  • Graphics Card:Intel HD5000
  • Operating System:macOS 10.12 (Sierra)
  • I like to play:stories

Posted 17 December 2016 - 10:35 AM

This looks like LLVM masquerading as GCC. Probably done for compatibility purposes in generic build scripts.

#12 doh123

doh123

    Wineskin Developer

  • Members
  • 4,279 posts
  • LocationOver here
  • Graphics Card:Geforce GT 650M, Intel HD 4000, Radeon 6750, Intel HD 3000, Geforce 320m (in 3 machines)
  • Operating System:OS X 10.8 (Mountain Lion)
  • I like to play:RPG and Strategy

Posted 17 December 2016 - 01:24 PM

View PostsoloMacOSX, on 17 December 2016 - 05:04 AM, said:

I have installed gcc on my mac, it's a screenshot with my version of gcc

Posted Image
I have read, that the error "checking whether the c compiler works... no" is due to I have not run gcc on my mac and agreed with it's terms of license. Which command I need to use to run gcc from the terminal?

yeah, thats clang... it should still work.I know now you can just do "xcode-select --install" which should install and fix several things... but last time I did a fresh install, and it kept saying this, i had to launch XCode.app and accept all the license agreement junk and everything before the command line stuff started working right.  I have not worked with their changed processes in the last couple of years so I'm not totally sure what to tell you.

#13 soloMacOSX

soloMacOSX

    Regular Member

  • Members
  • Pip
  • 19 posts
  • Graphics Card:NVidia9400M
  • Operating System:OS X 10.8 (Mountain Lion)

Posted 17 December 2016 - 04:13 PM

doh123 I have tried in 4 macs, and still having the same problems. I need help! I tried it in 3 iMacs 2015 late and 1 macbook 2008 late and I'm having the same problems :(

All in OSX EL Capitan
More tutorials in english about Wineskin on soloMacOSX Youtube

#14 soloMacOSX

soloMacOSX

    Regular Member

  • Members
  • Pip
  • 19 posts
  • Graphics Card:NVidia9400M
  • Operating System:OS X 10.8 (Mountain Lion)

Posted 17 December 2016 - 05:40 PM

I tried again if command lines is installed on my Mac and yes, it's installed. Also I have XCode updated. Still the same problem building engines --> "checking whether the C compiler works... no"
I will send you some screenshots:

Posted Image
Posted Image
All is installed, but I can't compile new engines :(
More tutorials in english about Wineskin on soloMacOSX Youtube

#15 ScoPezz

ScoPezz

    Professional Member

  • Members
  • PipPipPipPip
  • 141 posts
  • LocationBelgium
  • Graphics Card:Intel GMA X3100
  • Operating System:Mac OS X 10.7 (Lion)

Posted 18 December 2016 - 06:52 PM

View PostsoloMacOSX, on 17 December 2016 - 05:40 PM, said:

I tried again if command lines is installed on my Mac and yes, it's installed. Also I have XCode updated. Still the same problem building engines --> "checking whether the C compiler works... no"
I will send you some screenshots:



All is installed, but I can't compile new engines :(

Run this command: sudo xcodebuild -license
You can agree to everything using this command.

#16 soloMacOSX

soloMacOSX

    Regular Member

  • Members
  • Pip
  • 19 posts
  • Graphics Card:NVidia9400M
  • Operating System:OS X 10.8 (Mountain Lion)

Posted 19 December 2016 - 05:50 PM

View PostScoPezz, on 18 December 2016 - 06:52 PM, said:

Run this command: sudo xcodebuild -license
You can agree to everything using this command.

No success. And again I tried on a friend's Mac and still the same problem. No compiling custom engines. It's the fifth Mac I've tried and the problem stills appear.

checking whether the C compiler works... no

:(
More tutorials in english about Wineskin on soloMacOSX Youtube

#17 ScoPezz

ScoPezz

    Professional Member

  • Members
  • PipPipPipPip
  • 141 posts
  • LocationBelgium
  • Graphics Card:Intel GMA X3100
  • Operating System:Mac OS X 10.7 (Lion)

Posted 19 December 2016 - 05:58 PM

View PostsoloMacOSX, on 19 December 2016 - 05:50 PM, said:

No success. And again I tried on a friend's Mac and still the same problem. No compiling custom engines. It's the fifth Mac I've tried and the problem stills appear.

checking whether the C compiler works... no

:(

Then it seems your build environment is polluded or not installed correctly. Are you sure SIP is disabled and you installed the correct gcc version?

#18 soloMacOSX

soloMacOSX

    Regular Member

  • Members
  • Pip
  • 19 posts
  • Graphics Card:NVidia9400M
  • Operating System:OS X 10.8 (Mountain Lion)

Posted 20 December 2016 - 03:52 AM

View PostScoPezz, on 19 December 2016 - 05:58 PM, said:

Then it seems your build environment is polluded or not installed correctly. Are you sure SIP is disabled and you installed the correct gcc version?

Yes, I have disabled SIP. I followed your guide step by step in 5 Macs and I can't build custom engines. Could be a problem with OSX El Capitan?
More tutorials in english about Wineskin on soloMacOSX Youtube

#19 soloMacOSX

soloMacOSX

    Regular Member

  • Members
  • Pip
  • 19 posts
  • Graphics Card:NVidia9400M
  • Operating System:OS X 10.8 (Mountain Lion)

Posted 21 December 2016 - 08:55 PM

View PostScoPezz, on 19 December 2016 - 05:58 PM, said:

Then it seems your build environment is polluded or not installed correctly. Are you sure SIP is disabled and you installed the correct gcc version?

ScoPezz I think I've found the problem, but I don't know how to solve it. I researched on google and found that GCC must be installed on /usr/local/bin and the wineskin script installed GCC on another directory /usr/bin. Here is a thumbnail of my actual install directory. How can I change the GCC install directory to /usr/local/bin ? for this reason I think that terminal is not finding the C compiler. Hope for your soon answer.

Posted Image
More tutorials in english about Wineskin on soloMacOSX Youtube

#20 ovvldc

ovvldc

    Master Member

  • Members
  • 1,072 posts
  • Graphics Card:Intel HD5000
  • Operating System:macOS 10.12 (Sierra)
  • I like to play:stories

Posted 21 December 2016 - 10:07 PM

Maybe a few symlinks can fix the problem? Possibly with some additions to PATH




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users