Page 1 of 1

x64 compile attempt

Posted: Tue Feb 22, 2011 8:40 am
by pheonixstorm
trying to get the VC9 solution setup to compile both win32 and win64 binaries. So far I have not had any luck. My first compile died on posh.h because it was too old.. my 2nd attempt died in the low level networking code because posh.h was to new. I just can't seem to win... Once I get the bugs worked out between posh and the networking code.

Re: x64 compile attempt

Posted: Tue Feb 22, 2011 12:56 pm
by shenle
It's funny, because I haven't seen this error when I did compile a 64-bit binary back in December I think. Don't remember of any trouble with posh.h or any of the networking code. In fact once I got all the dependencies in a 64-bit form it compiled quite cleanly.... that was around SVN revision 12900 I think. Getting all the libraries compiled as 64bit was the hard part. I think I have posted somewhere on this forum all the 64-bit libs I made in case you want to use them (yep, right here: http://vegastrike.sourceforge.net/forum ... 5&start=45).

In other news, I'm working on getting a system to compile an OSX binary. Got OSX 10.5.7 installed on my desktop - finally found a driver for the network card that won't cause kernel panics - with Xcode 3.1.4 and Cmake. Got the local svn repository setup and most dependencies - all I'm missing now is ffmpeg and gtk2.

(edit) Grrr. Ffmpeg depends on yasm. Yasm builds with cmake and xcode, but I can't install it because I don't know how to do the equivalent of "sudo make install" in xcode.

Re: x64 compile attempt

Posted: Thu Mar 10, 2011 10:27 am
by strook
simply copy the lib and include folders to the /lib or /opt folder after you compiled it.

Re: x64 compile attempt

Posted: Fri Apr 15, 2011 9:20 pm
by strook
no, there is a setting in the xcode project settings, meaning where to copy the files to after compiling.
it does it automatically after compile.