build BCI2000 win7 x64

[ageronimo]

I am trying to build 64 bit executables of BCI2000 on windows 7. from the "Building BCI2000" wiki page, i saw that vc++2008 and windows 7 64 bit were known to be stable.

I have installed visual c++ express 2008, cmake 2.8.12.1, and ran "Make VS2008 Win64 Project Files.bat". It ran through, using qt-4.8.4 in the BCI2000 distribution.

When i try to open the BCI2000 solution in vc++2008, i get this error -- "The project consists entirely of configurations that require support for platforms which are not installed on this machine"

I tried following the instructions on this forum for making vc++2008 express compatible with x64 solution files (http_nospam_www.bci2000.org/phpbb/viewt ... 6271#p6271), but i do not have any of the amd64/64 config or bat files that they refer to in my installation folders. I gave up on this.

I also tried compiling with vc++2010 express, using "Make VS10 Project Files.bat". Cmake created a (32 bit?) solution file for this and I was able to open in vc++2010 express. I followed the instuctions I found on the microsoft site for compiling 64 bit programs in vs2010 (http_nospam_msdn.microsoft.com/en-us/li ... 4317s.aspx). I followed these instructions, but could not compile many of the projects. (errors like "could not find kernel32.lib", "could not find CL.exe") Should I expect this to work at all without a "Make VS10 Win 64.bat" option?

Very frustrated here. I currently have a successfully built 32 bit version which works on the 64 bit system, except that the gusbamp drivers are 64 bit and i get an error that cannot run a 32 bit executable with the amplifiers that use 64 bit drivers.

Any advice/best route to go? I would be happy with getting anything to work on my 64 bit system (like somehow installing 32 bit gusbamp drivers to go with the functional 32 bit BCI2000 executables, or succeeding in building 64 bit BCI2000 programs)

Thanks in advance!
-Andrew

[dlg332drexel]

Have you resolved this issue? I'd like to use BCI2000 on a Windows 7 64 bit machine too and am having problems.

[ageronimo]

I never got a x64 version to compile. I got the 32 bit version to work for me, by installing the both the 32- and 64-bit g.usbamp drivers. Didnt think this would work, but so far so good!

[boulay]

Andrew,

I'm sorry no one answered you previously. I didn't see this thread until now.

Using the 32 bit drivers on a 64-bit system is the preferred way to do it. There are several posts on this BBS about how to do that. Hint: The gUSBampSource module will use whatever gusbamp.dll file it has in its own directory; if none, the 32-bit module will search C:\Windows\SysWOW64 and the 64-bit module will search C:\Windows\System32\drivers.

I haven't tried to do the 64-bit compilation in over a year. I'm not sure who, if anyone, tests that.

Could you please elaborate on what you meant by

but i do not have any of the amd64/64 config or bat files that they refer to in my installation folders

?
Does that mean you had trouble with the "Setting up the toolchain" part of that linked Blender doc?
Those instructions are only for VS2008 Express, because it does not come with 64-bit enabled. The Pro version does (I think!) and is available with a free trial. You might have better luck with that.

As for getting it to work with VS2010, I think you'll need to make your own config script.

Anyway, it seems you got it to work with the 32-bit drivers. That should work well for you indefinitely. The only other instance I can think of where 64-bit binaries were ever necessary for me was for connecting BCI2000 to a 64-bit Matlab. In almost all other cases, 32-bit hardware drivers placed in C:\Windows\SysWOW64 did the trick.