From: <ma...@dl...> - 2014-01-06 12:06:48
|
Hey Nate, sounds great - thanks for your effort here! For my current situation, I add the include directory and the *.lib files when compiling the rigControl application with hamlib on my dev-Computer. The Buildserver is using the MXE environment and currently using the -pthread flag to have a 32bit and 64bit static lib built out of a hamlib3 SVN snapshot (snapshot taken Nov.2013). Let me know if there is a specific topic that I can help looking at. Until now I have very little experience with wine - I used VirtualBox and there it worked running 32bit and 64bit host systems on a native 32bit or 64bit box. tnx, HNY to all of you on the list es 73z de Lars Am 06.01.2014 12:51, schrieb Nate Bargmann: > * On 2013 28 Dec 17:57 -0600, ma...@dl... wrote: >> - Now I would like to ask if you could enhance the support with a win64 >> version as well. - >> I´ve already compiled hamlib3 from git on mxe (thanks to the *mk file of >> Remi) for both 32 and 64bit - statically linked on my compiler farm. >> Currently I still use the -pthread flag for my application - I have >> posted that issue after the bidirectional talk with Remi couple of weeks >> ago on this list. So i think it should work to build a 64bit msvc dll >> and lib on the git webpage along with the win32 version - it would be >> great if you could add this. > Hi Lars. > > I can probably build the 64 bit executables easy enough but the 64 bit > DLL may be another matter. It is something I'll have to look into as I > would need to have a 64 bit version of Wine working and then get a 64 > bit MSVC runtime going as well. I'm not sure if that will be a problem > on a 32 bit box, though. > > 73, de Nate >> > |