From 3b1405169d66e029912f53d10c2880c46f5ed159 Mon Sep 17 00:00:00 2001
From: Timothy Pearson <kb9vqf@pearsoncomputing.net>
Date: Wed, 16 Nov 2011 13:51:39 -0600
Subject: Additional renaming of kde to tde

---
 kunittest/runner.h       |  2 +-
 kunittest/samplemodule.h |  2 +-
 kunittest/tester.h       | 10 +++++-----
 3 files changed, 7 insertions(+), 7 deletions(-)

(limited to 'kunittest')

diff --git a/kunittest/runner.h b/kunittest/runner.h
index 1e0c1ec72..5ed386b00 100644
--- a/kunittest/runner.h
+++ b/kunittest/runner.h
@@ -40,7 +40,7 @@ using namespace std;
 #include <tqasciidict.h>
 #include <tqstring.h>
 
-#include <kdelibs_export.h>
+#include <tdelibs_export.h>
 
 #include "tester.h"
 
diff --git a/kunittest/samplemodule.h b/kunittest/samplemodule.h
index b9def68fd..b5fd2bcd4 100644
--- a/kunittest/samplemodule.h
+++ b/kunittest/samplemodule.h
@@ -27,7 +27,7 @@
 #define SAMPLETESTMODULE_H
 
 #include "tester.h"
-// Outside of kdelibs you would use: #include <kunittest/tester.h>
+// Outside of tdelibs you would use: #include <kunittest/tester.h>
 
 class SampleTester : public KUnitTest::Tester
 {
diff --git a/kunittest/tester.h b/kunittest/tester.h
index 0b4dc382f..278f0d18d 100644
--- a/kunittest/tester.h
+++ b/kunittest/tester.h
@@ -53,9 +53,9 @@
  * You are responsible for what you do with it though. It
  * is licensed under a BSD license - read the top of each file.
  *
- * All the GUI related stuff is in kdesdk/kunittest, the core libraries are in kdelibs/kunittest.
+ * All the GUI related stuff is in tdesdk/kunittest, the core libraries are in tdelibs/kunittest.
  * A simple example modules is in kdelisbs/kunittest/samplemodule.{h,cpp}, however more examples
- * can be found in kdesdk/kunittest/example.
+ * can be found in tdesdk/kunittest/example.
  *
  * There are roughly two ways to use the KUnitTest library. Either you create dynamically
  * loadable modules and use the kunittestmodrunner or kunittestguimodrunner programs to run
@@ -67,7 +67,7 @@
  * them.
  * @li runnergui.{h,cpp} - the GUI wrapper around the runner. The GUI neatly organizes the
  *   test results. With the kunittest helper script it can even add the debug output
- *   to the test results. For this you need to have the kdesdk module installed.
+ *   to the test results. For this you need to have the tdesdk module installed.
  * @li tester.h - which holds the base of a pure test object (Tester).
  * @li module.h - defines macros to create a dynamically loadable module.
  *
@@ -314,7 +314,7 @@ SampleTest - 1 test passed, 1 test failed
  * @li kunittestmod --folder [folder] --query [query] : Loads and runs all modules in the folder matching the query. Use a GUI.
  * @li kunittest_debughelper [dcopobject] : A PERL script that is able to redirect debug output to a RunnerGUI instance.
  *
- * These scripts are part of the kdesdk/kunittest module.
+ * These scripts are part of the tdesdk/kunittest module.
  */
 
 /*!
@@ -329,7 +329,7 @@ using namespace std;
 #include <tqstringlist.h>
 #include <tqasciidict.h>
 
-#include <kdelibs_export.h>
+#include <tdelibs_export.h>
 
 /*! @def CHECK(x,y)
  * Use this macro to perform an equality check. For example
-- 
cgit v1.2.1