From: Hendrik S. <po...@he...> - 2007-07-14 08:27:15
|
Am Sonntag 24 Juni 2007 06:46 schrieb Denis Kenzior: > I wanted to see how easily OpenOBEX compiles on Visual Studio 2005. > Overall it wasn't too bad, but required a bit of effort. Attached is a > patch to make it compile. I've tested successfully with TCP transport. Yes, it requires quite some changes. After writing the CMake rule files, creating the VCExpress solution file was an easy task. I didn't manage to compile the thing, yet! This msvc compiler is just so broken and incompatible, that really sucks. Where shall I start: - doesn't know "inline" but "__inline" - says that "strncpy" is deprecated (what the f***) - needs to include io.h when using read or write - must define write as _write - must define read as _read - doesn't eat the current construct of BDADDR_ANY, must be the address of an extern variable instead .... Quite some differences, I'd say. Possible but Microsoft REALLY sucks here. Why can't the do like the rest of the world? Oh yeah, I forgot, they only support C++, not C. I did just a quick hack and got the library built (with excluded USB support). Maybe I open my own subversion respository with trac and with a complete openobex-win32 port as there is no such thing as quilt for win32 and that makes it a real pain to create fine patches when you already had to patch after checkout :-( My point is, though: the cmake files create working VC solutions files. I'll open a ticket for easier download and update. If you have a better clue about MSVC, maybe you can make the change the win32 patches and test the cmake files. OTOH, the gcc compiled lib will also work for MSVC, so the need to actually support MSVC is not that big. HS |