We're trying to determine if winelib can help us get our Windows software product working for OS X users at a low development cost.
We're following the winemaker "Getting Started" section of the winelib-guide, doing the development and testing on an OS X El Capitan system.
We first installed the 1.9.15 Staging package for OS X.
Then we realized we need to build the developer code for x86 and x64. But after building it we did not install it (it's possible this has led to some of the problems).
In trying to follow the documentation, we've built the notepad program with winelib, though it took a lot more effort to get the makefile working than the winemaker documentation implied. We had, for example, to add a whole bunch of explicit paths. But we did finally get it to build.
However, unless we include the WINE package components in the system's PATH, when we try to run the notepad.exe example program built with winelib we just get this message:
Code: Select all
OSXVM:notepad NoelC$ ./notepad.exe
./notepad.exe: line 36: exec: wine: not foundOur initial assumption is that building Windows sources using winelib should result in the creation of a standalone program that will run on an OS X system that has not had WINE installed. Is this valid?
Asked another way, what does it take (assuming it's possible) to build a full, standalone OS X App using Windows sources and Winelib?
Thank you very much in advance for wisdom you're willing to share.
-Noel
