First, thanks again for all this help.
> ...as expected. Try to somehow link the LMMS binary
> ${CMAKE_BINARY_DIR}/lmms to the shared library.
>
Ok, I'll try that, but the function names on the errors seem to suggest
RemoteVstPlugin rather than LMMS or am I wrong? (see output here:
https://gist.github.com/anonymous/10388146)
> Next I started looking at the CMake script again and it looks like Linux
> > builds a RemoteVstPlugin library using wineg++?
>
That's right.
>
Ok, the CMake doesn't have a wineg++ entry for APPLE, which is easy enough
to work-around for now by removing LMMS_BUILD_LINUX from this line:
https://github.com/LMMS/lmms/blob/stable-1.0/plugins/vst_base/CMakeLists.txt#L23,
which of course is where I hit the header file errors.
> These are part of WINE and or the WINE development packages. You
> should never need to download files manually especially as they
> probably won't work as they're missing WINE specifics.
>
So after looking into this, it appears the wineg++ on OSX is 100% clang.
I'm wondering if MacPorts is leaving out the source or if I'm just too
blind to find it. Not much on the internet about this. :)
As you've suggested, I was working under the assumption these would already
be on my machine. I searched high and low for the headers on the local
filesystem to no avail and I'm not sure how to retrieve them manually.
MacPorts has a wine and wine-devel package, but no dice finding these
headers anywhere in /opt/local, which is where I believe all of MacPorts
installs to.
I did notice the mingw source has these headers, but that didn't help
either and there seems to be some syntax issues compiling them against
clang.
I looked at the WineHQ instructions for building wine (assuming these
headers may be part of the MacPorts guide) and it makes specific mention
about incompatibility with clang recommending ./configure
CC="gcc-apple-4.2" instead.
http://wiki.winehq.org/MacOSX/Building#head-f6eb9d865f21b525ac313d62cbb73ca36e07a0a3)
Quote from WineHQ:
> Note that the default compiler is llvm-gcc, which won't work for wine.
> Clang can compile wine, but it miscompiles winemac.drv (and potentially
> other stuff). gcc-apple-4.2 is known to work.
> Finally, be sure make your ~/.profile look similar to the following,
> making sure to modify the path set up by MacPorts to point to your wine git
> install, as well as to dynamically link to the proper libraries upon Wine
> execution:
But all this is moot if the headers are missing, right?
So.. I downloaded the wine source (1.7) but these specific headers aren't'
there. Shot in the dark here, but are there some specific includes that we
are using that is telling Clang we need headers that wouldn't be available?
I looked up the winegcc man page and tried adding some switches to
build.make such as "-mno-cygwin", "-nodefaultlibs", "-nostartfiles" but
this seemed to do nothing to help the missing header errors.
Thanks again for reading this lengthy email...
-Tres
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
LMMS-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmms-devel
