[Qt-interest] Proper way to develop shared library for two QT applications

Johann MacDonagh johann at macdonaghs.com
Wed Jan 21 06:11:25 CET 2009


Hi all,

The project I'm currently developing is composed of three different
projects. The server component, the client component, and a shared
library between the two. The shared library will primarily have a few
classes that will handle communication serialization / deserialization
between the server and the client. All three are being developed at
the same time.

You can imagine my directory structure is:
/server
/client
/library

My question is, what's the best way of setting up my project files to
make development easy? Essentially, i want a main .pro file which will
build all three projects (first the library, then the server, then the
client). That's easy enough to do with the subdirs project type. I'd
like the server project to try and reference the .so and the .h files
from the /library directory if available (e.g. the user build the
library from the subversion repo). However, if the library is not
built, then it should try and grab from the standard locations.

Should I be approaching it from this angle? I don't want a ton of half
finished libraries clogging up my library install locations.

Thanks,
Johann



More information about the Qt-interest-old mailing list