Hi, Andy. Would be nice if you will do it.
I stopped committing to that branch because I added some features needed only by my application thus my (local) fork went far away from Hypertable roadmap. So I had no time to support the legacy Windows port :( In few days I will review the latest changes and backport the Windows-specific ones (if any) to the 'windows' branch on github. 2010/5/7, Andy <[email protected]>: > Hi Doug, > > based on Masha's excellent work I managed to build Hypertable 0.9.3.0 > for windows x86 using: > > * http://github.com/conferno/hypertable/tree/windows > * VS2010 > * boost 1.42 > * Berkley DB 5.0.21 > > build and tests have been made on a 32-bit Windows 7. > > This brings me to a few questions: > > * Is there any interest to officially support windows 32/64-bit in the > near future? > > * Should I fork the git repository github.com/conferno/hypertable/tree/ > windows in order to pull in > my few changes? Just 14 files have been changed - or should I send > the changes via > email or file upload? > > * I'd like to continue my work with > > 1) a Hypertable.Service component, a windows service for Hypertable > - launch, watch and shutdown the servers > (as a mixed mode assembly targeting .NET 2.0) > > 2) a .NET client, based on the c++ client (also mixed mode, > therefore only for windows) > > any interest on those components? Opening a /contrib/.NET/... ? > > -Andy > > > On Mar 14, 6:51 pm, Doug Judd <[email protected]> wrote: >> Hi Masha, >> >> This is great! Thank you. For me to pull it in, you'll have to fill out >> the Hypertable Contributor >> Agreement<http://www.hypertable.org/pub/HypertableContributor.pdf> . >> It gives us both rights to do whatever we want with the code. You can >> either fax it to 650-230-7176, or scan it and e-mail it to me, or send it >> to >> my home address: 2999 Canyon Rd. Burlingame CA 94010. Thanks. >> >> - Doug >> >> On Sat, Mar 13, 2010 at 3:01 PM, Masha <[email protected]> wrote: >> > Hi. >> >> > I managed to port the client part of Hypertable (the shell and python >> > bindings), in order to entirely avoid using Thrift. >> > The sources are here:http://github.com/conferno/hypertable/tree/windows >> > Porting the server part and the test suite seems to be trivial, except >> > of hyperspace's part which relies on extended file attributes. >> > Perhaps I will do it next weekends. >> >> > Some notes: >> >> > 1. Usage of errno and duality of file and socket handles are slightly >> > different on Windows. >> > Some solution should be developed later. >> > May be types like OsFileHandle, OsSocketHandle and functions like >> > last_file_error(), last_socket_error(). >> > Or may be we should start using boost::filesystem. >> > At the moment there are just a lot of "#ifdef _WIN32" (platform >> > specific) and "#ifdef _MSC_VER" (compiler specific) that, I guess, is >> > not nice. >> >> > 2. Fortunately, the event model you have developed is very close to IO >> > Completion Ports, thus HyperComm got smaller. >> >> > 3. CMAKE has some problems on Windows. >> > Porting CMAKE's scrips is a separate (and not so small) task, so I >> > gave up and wrote a simple makefile for a while. >> >> > 4. Only two of the 3rd party libraries (BerkeleyDB and Boost) can be >> > installed similar way as '*-devel' packages in linux: headers, >> > libraries, and predictable location. >> > I included Bzip2, Expat, Log4cpp, Sigar and Zlib into the >> > Hypertable source tree for simplicity and to get some benefit of link >> > time code generation. >> >> > 5. Visual C++ has very different hash_map. >> > Should we support both hash_map or put hash_map header into >> > Hypertable source tree ? >> > At the moment the windows branch supports both, with "#ifdef _MSC_VER" >> >> > 6. Visual C++ shows much more warnings than GCC. >> > Mainly unsafe 64-to-32-bit casts. >> > They have to be fixed in the main branch eventually. >> >> > 7. Minimum Windows XP is required (ConnectEx is used for asynchronous >> > connects). >> > I do need Windows 2000 support on clients and will fix it later >> > somehow (by making connects synchronous on that platform or by >> > developing some workaround). >> >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "Hypertable Development" group. >> > To post to this group, send email to [email protected]. >> > To unsubscribe from this group, send email to >> > [email protected]<hypertable-dev%[email protected]> >> > . >> > For more options, visit this group at >> >http://groups.google.com/group/hypertable-dev?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Hypertable Development" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/hypertable-dev?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Hypertable Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hypertable-dev?hl=en.
