Hi Lukas, If you build your ContactBook project into a static library, you can then link to it from your test project. This way you do not have to compile contact.cpp twice.
In your example, I would split the code into three CodeLite projects: - ContactBook (static lib, generates libcontactbook.a from contact.o) - ContactBookApp (main app exe, uses -lcontactbook) - ContactBookTests (console exe, uses -lcontactbook) If you organize your projects this way, you can share the same lib between the App and the Test. This is what I do on my own projects. I do not use CodeLite so I can't help you with setting this up, but it should be easy. Hope this helps, Ben. -------------------------------------------------- From: "lukas plachta" <[email protected]> Sent: Saturday, April 17, 2010 5:49 PM To: <[email protected]> Subject: [unittest-cpp-devel] including tested objects > > Hi, Im new to UnitTest++, > I have a question about including tested objects... [...] > I hope, this is better way, but I dont know, how to make it work like > that. > Is it possible ? ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ unittest-cpp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel
