[Qt-interest] Rebuilding app when linked staticlib is changed [resolved]

[Bastian Bense]

Hey again,
I kind of resolved this by conditionally creating a shared library (.so)
(when qmake is called in debug mode) from my common code project, then link
it in my test application.Later when I want to release the code, I'll call
qmake in "release" mode and generate a static library instead.

~ Bastian

2009/7/28 Bastian Bense <bastibense at gmail.com>

> Hey everyone,
> I am experimenting a lot with libraries recently, and decided to use a
> staticlib project to implement a lot of core functionality that I'll need in
> a number of modules and then link it into the specific application to access
> it.
>
> Since the core functionality in the lib is changing a lot and I'm debugging
> it, my workflow is usually as follows:
>
> 1) change staticlib code
> 2) compile the test application that links the lib in
> 3) test the code
> 4) (repeat)
>
> Unfortunately in most cases the test application is not re-compiled/linked
> when the staticlib changes (probably because the app code itself did not
> change).
>
> I'm using Qt Creator snapshot right now, and I was wondering if there is a
> way to automate the re-linking of the test application after the library
> changed?
>
>
-- 
Best regards,
Bastian Bense
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20090728/715473f9/attachment.html