Summary: | Fix autoconf build for windows | ||
---|---|---|---|
Product: | dbus | Reporter: | Marcus Brinkmann <marcus.brinkmann> |
Component: | core | Assignee: | Ralf Habacker <ralf.habacker> |
Status: | RESOLVED FIXED | QA Contact: | John (J5) Palmieri <johnp> |
Severity: | normal | ||
Priority: | medium | CC: | walters |
Version: | 1.3.x (devel) | ||
Hardware: | Other | ||
OS: | Windows (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Consistently include config.h in all C source fiels.
Define dbus_1_EXPORTS Do not use DBUS_WIN in a public header file |
Description
Marcus Brinkmann
2010-03-19 04:57:51 UTC
Created attachment 34236 [details] [review] Consistently include config.h in all C source fiels. Include <config.h> first in all .c files, but in no .h files. Created attachment 34237 [details] [review] Define dbus_1_EXPORTS This defines dbus_1_EXPORTS where needed for autoconf based builds. Created attachment 34238 [details] [review] Do not use DBUS_WIN in a public header file Use _WIN32 instead DBUS_WIN in public header file. Alternative would be extending dbus-arch-deps.h, probably by this (untested): #if @DBUS_WIN@ #define DBUS_WIN 1 #else #undef DBUS_WIN #endif Hi Colin, do you see any problems with the first patch ? The other two does not make any problem as far as I can see. patch 1 depends on the wince patch (..glue file). I can apply without the related fix, which should be added to the wince patch diff --git a/dbus/dbus-sysdeps-wince-glue.c b/dbus/dbus-sysdeps-wince-glue.c index 38b59c6..204e719 100644 --- a/dbus/dbus-sysdeps-wince-glue.c +++ b/dbus/dbus-sysdeps-wince-glue.c @@ -26,6 +26,7 @@ * */ +#include <config.h> #include "dbus-internals.h" #include "dbus-sysdeps.h" #include "dbus-sysdeps-win.h" I tried building with cmake/msvc on windows, no other problems detected. patches tested with cmake and msvc + mingw without any errors - applied |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.