On Fr, 2011-05-13 at 14:15 +0100, Gabriel Schulhof wrote:
> Hi!
> 
> I have just received access to the syncevolution repo on gitorious. I
> pushed a branch called qt-bindings, which should create the bindings
> necessary for talking to the syncevolution D-Bus server from a Qt app.
> 
> The bindings are enabled with --enable-qt-dbus from configure.

I'm in the process of merging this. I decided to reorganize the src/dbus
content first so that the glib library is in src/dbus/glib and
src/dbus/qt can be create alongside.

Regarding the Makefile rules:

        syncevo-server-full.cpp: ../dbus/interfaces/syncevo-server-full.xml
                if test -f $@; then touch $@; else qdbusxml2cpp -p $* -i 
dbustypes.h $< ; fi
        syncevo-session-full.cpp: ../dbus/interfaces/syncevo-session-full.xml
                if test -f $@; then touch $@; else qdbusxml2cpp -p $* -i 
dbustypes.h $< ; fi
        syncevo-connection-full.cpp: 
../dbus/interfaces/syncevo-connection-full.xml
                if test -f $@; then touch $@; else qdbusxml2cpp -p $* -i 
dbustypes.h $< ; fi
        syncevo-server-full.h: ../dbus/interfaces/syncevo-server-full.xml
                if test -f $@; then touch $@; else qdbusxml2cpp -p $* -i 
dbustypes.h $< ; fi
        syncevo-session-full.h: ../dbus/interfaces/syncevo-session-full.xml
                if test -f $@; then touch $@; else qdbusxml2cpp -p $* -i 
dbustypes.h $< ; fi
        syncevo-connection-full.h: 
../dbus/interfaces/syncevo-connection-full.xml
                if test -f $@; then touch $@; else qdbusxml2cpp -p $* -i 
dbustypes.h $< ; fi
        
First, repeating the same rules can be avoided by using wildcards:

        syncevo-%-full.cpp: $(srcdir)/../interfaces/syncevo-%-full.xml
                if test -f $@; then touch $@; else qdbusxml2cpp -p $* -i 
dbustypes.h $< ; fi

Second, doesn't this mean that files, once generated, will never be
regenerated even if the input .xml files change?

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.


_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to