LaserShark 3DP for windows 7 64bit

[cutecheng]

Hi, Jeff, I finally solved the problem 
In Zadig, I should use "libusb-win32(v1.2.6.0)" in stead of the default setting (WinUSB). Now i'm able to communicate properly with the board, thanks for all your help!

[Macpod]

I'm glad some of those suggestions helped you out and thanks for pointing out what you needed to do to get things up and going. Others will certainly appreciate it.

Please feel free to share what you end up doing with the kit. Also if there's something that can be easily added to the build script (i.e. better windows support when searching for dependencies) let me know and I can try and add them to the code base on github.

[cutecheng]

I created a console project in microsoft visual studio with the default setting, then imported "LaserShark.h" and "LaserShark.cpp". A lot of libraries are not supported in windows, for example, "thread", "atomic", "mutex", they need to be removed from the code until the project can be compiled.

Zadig was used for the driver installation, but the trick is windows does not support "WinUSB" well, we can use either "libusb-win32(v1.2.6.0)" or "libusbK".
Zadig: http://zadig.akeo.ie/

The latest "libusb" library can be downloaded here:libusb: http://sourceforge.net/projects/libusb/?source=dlp. Both the static library and dynamic library work well in the Visual Studio environment.

[Macpod]

Those are all standard with c++11 which should be cross platform compatible(this is why I'm using them). Instead of whatever compiler microsoft visual studio uses you could try using MinGW's under Windows.
http://www.mingw.org/

For this system to work as design (with json-rpc-cpp aspects... I know you aren't using these portions) use of threads, mutexes and atomic variables are necessary so those can't really be removed.

[Stimpy]

hello all

The new release from macpod i can make it also in windows 7 64bit.
I will make a post how to compile everyhting so you can do it by your self.
I think it will be online toonight.

Greetings all