Most recent edit on 2006-10-14 09:21:20 by KogAdmin [refactor]
Additions:
This will no longer be a problem with the introduction of the RXTX library∞. They should have Windows, Linux, various Unix and other drivers. The JAR should be standard, all you'll need to do is install either the DLL or SO (DLL for Windows users obviously heh).
Deletions:
Due to the lovely nature of the Win API functions, my original writing of the serial server using named pipes + serial (.NET2) failed. I'm re-writing it to use sockets, which should be much easier. This does, however, involve writing a new messenger object. I'm working on cleaning up the source tree greatly and now that I've finished on some of the other projects I've been working on, this will be underway soon.
I've been working on rolling a win32 distro. So far I've built a HOG_Messenger_Win32 object, interfaced that in the Main block and I think that should be ok. I'm throwing it into testing now using a .NET TCPListener. You'll still need to have the .NET2 SDK, but there's no more interop, it's all managed code. I'll have a working package rolled as soon as I know it works. In the meantime, if you can grab the named pipe version and figure out what's going on, feel free to give me feedback. I'm throwing exceptions that I don't understand, and the API docs don't seem to be particularly clear on Named Pipes - further, named pipes are a client/server model instead of the traditional file-based Unix type pipes.
Edited on 2005-07-28 01:46:23 by KogAdmin [added info about the new win32 package]
Additions:
Due to the lovely nature of the Win API functions, my original writing of the serial server using named pipes + serial (.NET2) failed. I'm re-writing it to use sockets, which should be much easier. This does, however, involve writing a new messenger object. I'm working on cleaning up the source tree greatly and now that I've finished on some of the other projects I've been working on, this will be underway soon.
I've been working on rolling a win32 distro. So far I've built a HOG_Messenger_Win32 object, interfaced that in the Main block and I think that should be ok. I'm throwing it into testing now using a .NET TCPListener. You'll still need to have the .NET2 SDK, but there's no more interop, it's all managed code. I'll have a working package rolled as soon as I know it works. In the meantime, if you can grab the named pipe version and figure out what's going on, feel free to give me feedback. I'm throwing exceptions that I don't understand, and the API docs don't seem to be particularly clear on Named Pipes - further, named pipes are a client/server model instead of the traditional file-based Unix type pipes.
Deletions:
Due to the lovely nature of the WinAPI functions, my original writing of the serial server using named pipes + serial (.NET2) failed. I'm re-writing it to use sockets, which should be much easier. This does, however, involve writing a new messenger object. I'm working on cleaning up the source tree greatly and now that I've finished on some of the other projects I've been working on, this will be underway soon.
Edited on 2005-07-27 16:17:22 by KogAdmin [added more details]
Additions:
Due to the lovely nature of the WinAPI functions, my original writing of the serial server using named pipes + serial (.NET2) failed. I'm re-writing it to use sockets, which should be much easier. This does, however, involve writing a new messenger object. I'm working on cleaning up the source tree greatly and now that I've finished on some of the other projects I've been working on, this will be underway soon.
Deletions:
TO BE ADDED WHEN I CAN CONFIRM HOG WORKS ON WIN32!!!
Edited on 2005-07-03 00:05:05 by KogAdmin
Additions:
Heart of Gold porting - Windows
Deletions:
Heart of Gold porting - Win32
Oldest known version of this page was edited on 2005-07-03 00:04:52 by KogAdmin []
Page view:
Heart of Gold porting - Win32
TO BE ADDED WHEN I CAN CONFIRM HOG WORKS ON WIN32!!!
CategoryHeartOfGold