IPlug - compiling for Mac with PC?

[captain caveman]

Hi

I am using VS 2008 Express and have 32 bit projects working on PC.

How would I go around compiling Mac versions using this?

Thanks, as always, for any help.

edit: I should mention it's just Mac VST.

[Tale]

To compile for Mac OS X you will need Xcode, which (as far as I know) only runs on Mac OS X. In other words, you will need a Mac.

[captain caveman]

Oooh, that's disappointing. So your command line thing to compile for all platforms is on a Mac using XCode?

[Tale]

Nope, the command line thing is for Windows, because I refuse to install Visual Studio.

[captain caveman]

Now I'm confused. :)

I'll give it a bash anyway when I get access to a Mac.

[Tale]

Now I'm confused. :)
IMHO Visual Studio is way too bloated, and the Express edition doesn't do 64-bit (not "out of the box" anyway). So I use the free Windows 7 SDK. It contains the same build tools as Visual Studio, but without the editing environment and other bloated stuff, and with full 64-bit support. This does mean you need to do everything from the command line, e.g. using NMAKE and makefiles.

On Mac OS X I am not as experienced, so I wouldn't really know how to compile from the command line. Fortunately Apple's Xcode is less bloated. And besides, on my MacBook Pro I don't really care, because I only use it for browsing the web anyway.

[Jeffos]

IMHO Visual Studio is way too bloated
Just switched to x64 and experienced that.. crazy dependencies: "bloated" is the word, I agree! I tried to hard limit the install of VC++ but it still requires like 5 Go and it was of course installed on C: even if I asked for D:! I really hallucinate (especially as my C: is a SSD drive). This is unnacceptable.

So I'm tempted by Tale's "free SDK" approach but, my only prob is the debugger: how can you debug things then ? traces only ?

[Tale]

So I'm tempted by Tale's "free SDK" approach but, my only prob is the debugger: how can one you debug things then ? traces only ?
Well, thusfar I haven't really needed a debugger. I have installed DebugView (http://technet.microsoft.com/en-us/sysinternals/bb896647) though, so I can print things to the debug "console" using OutputDebugString().

[olilarkin]

in the new example project i've made for wdl-ce i have a vs2010 file but there is also batch file to compile it from the command line using msbuild (and not have to open that bloat-fest vs2010). When i need to debug or add files to the project though, i open VS. I prefer codeblocks, but it seems like a bit of a PITA to get it working with the MS compiler in order to do 64bit

[Jeffos]

Thanks for the tips (DebugView looks handy) ! I've uninstalled all the "bloat-fest". BTW, the same unacceptable thing goes for the unintall: had to do that manually (many SQL jokes for an "Intellisense" that doesn't really work, .NET crap for the IDE and so on and so on.. x86 + x64 of course!).

I'll dev on a win32 PC and only compile (+debugview) x64 things on the new one using the Windows 7 SDK.

[Tale]

Mind you, the Windows SDK does also require .NET Framework 4, so it's not entirely "bloatless".

[Jeffos]

DANG!! Can someone tell me how comes on earth a SDK has such a dependency ? This wouldn't be a "SDK", then.
Pfff.. I was about to download/install it this morning, I'm already sure the D: install will turn into a C: one (but I won't report back: let this thread die before a linux guy notices it and laugh at us ;-)

[liteon]

you can strip down the 3.5 sdk as follows:


- get setup.exe from here:
http://www.microsoft.com/downloads/en/details.aspx?FamilyId=E6E1C3DF-A74F-4207-8586-711EBE331CDC&displaylang=en

(notice what the title says: Windows SDK for Windows Server 2008
_and_ .NET Framework 3.5)

- destination "somedrive:\sdk_tmp"

- install only the following components:
developer tools -> windows headers and libraries
developer tools -> compilers

- copy "program files\microsoft visual studio x.x" to "somedrive:\msvc"
- copy "somedrive:\sdk_tmp" to "somedrive:\sdk"
- goto "somedrive:\sdk" and delete everything but "lib" and "include"

- inspect the files "somedrive:\msvc\vc\bin\vcvars*.bat"

- set path to "somedrive:\msvc\vc\bin"
- set your environment variables "lib", "include", "windowssdkdir",
"vsinstalldir" etc..

- strip further libraries and compilers you don't need (e.g. for IA64).

- uninstall the 3.5 sdk



depending on what you have deleted and kept you will end up witha footprint of 100-400mb, which is a realistic size for a set of cross-compilers and libraries.

on low level debugging:
- find a older build of windbg (6.11.1 or something) (~20mb)
- include debug symbols with /Zi (or linker /debug) in your object code.
- follow trivial debug procedures...
reports in the category of addr2line should be available

or use alternative debuggers / methods...

---------
(edit) on topic:

you can purchase a recent osx version dvd and install it on a virtualbox. here is a guide:
http://www.sysprobs.com/install-mac-snow-leopard-1063-oracle-virtualbox-32-apple-intel-pc

since virtualbox is based on qemu, you should be able to run different architectures from the one of the host computer.

in theory, with a target specific compiler and the appropriate libraries you can build for osx / mac from any other place...

--