On Tue, Sep 22, 2009 at 11:27:03AM -0700, KC Jones wrote:
> The discussion of separate include and src directories raises a few
> questions:
> 
> First:
> Has the issue of building hierarchical projects using SUBDIRS been solved?
> Specifically the issue where changes to sources of a static library do not
> trigger a relink of the dependent application.  I missed a few threads about
> SUBDIRS support, so sorry if this has been discussed.  I might be willing to
> upgrade to a HEAD version if this problem has been addressed.  Having to
> remember to touch some source in the main app project is a major pain...

Can you please post a (really minimal) project that exposes the problem?
I have a hard time reproducing your troubles. I.e. given 

        -- foo.cpp --
        int foo() { return 42; }

        -- foo.pro --
        TEMPLATE = lib
        CONFIG += staticlib
        SOURCES += foo.cpp

        -- bar.cpp --
        int foo();
        int bar() { return foo() + 1; }

        -- bar.pro --
        TEMPLATE = lib
        CONFIG += staticlib
        SOURCES += bar.cpp

        -- main.cpp -- 
        int bar();
        int main() { return bar(); }

        -- main.pro --
        SOURCES += main.cpp
        PRE_TARGETDEPS = libfoo.a libbar.a
        LIBS += -L$$PWD -lbar -lfoo

        -- all.pro --
        TEMPLATE = subdirs
        SUBDIRS = foo.pro bar.pro main.pro
        CONFIG += ordered

running 

        qmake -r && make 

followed by

  touch foo.cpp && make 

rebuilds libfoo.a and main.

> Second, not really a Creator question, but it impacts my use of Creator
> significantly:
> Is there some trick to using LUPDATE on projects or subprojects where the
> sources are not in the same directory as the .PRO/.PRI files?  So far I have
> not been able to make it work.  I have a .PRO with something like:
> 
> HEADERS += include/XXX/Version.h \
>     src/XXXApplication.h \
>     src/foobar.h
> SOURCES += src/XXXApplication.cpp \
>     src/foobar.cpp
> 
> And LUPDATE fails on this completely.

Again, please make this a minimal, reproducible example.
 
> Third, onto the wishing:
> Is there any thought to integrating Qt translation tools into Creator?

There is such thought, but as the gain would be minimal and there are
more pressing needs all over the place it ranks pretty low.

This might change, of course, if someone would come up with a
ready-to-integrate implementation ;-)

Andre'
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-creator

Reply via email to