From d3dbfad131cf5ec53a7d0e5b1bd6a8bbb5edfa48 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20Marjam=C3=A4ki?= Date: Sun, 25 May 2014 13:24:07 +0200 Subject: [PATCH] GUI, manual: some clarifications how custom user .cfg files are used (Ticket: #5847) --- gui/projectfile.ui | 10 ++++++++++ man/manual.docbook | 16 ++++++++++++++++ 2 files changed, 26 insertions(+) diff --git a/gui/projectfile.ui b/gui/projectfile.ui index d5cec19b9..326811d15 100644 --- a/gui/projectfile.ui +++ b/gui/projectfile.ui @@ -69,6 +69,16 @@ + + + + Note: Put your own custom .cfg files in the same folder as the project file. You should see them above. + + + true + + + diff --git a/man/manual.docbook b/man/manual.docbook index 05e8061ab..649334615 100644 --- a/man/manual.docbook +++ b/man/manual.docbook @@ -713,6 +713,22 @@ Checking test.c... If you create a configuration file for a popular library, we would appreciate if you upload it to us. +
+ Using your own custom .cfg file + + You can create and use your own .cfg files for your + projects. + + The command line cppcheck will try to load custom .cfg files from + the working path - execute cppcheck from the path where the .cfg files + are. + + The cppcheck GUI will try to load custom .cfg files from the + project file path. The custom .cfg files should be shown in the + Edit Project File dialog that you open from the + File menu. +
+
Memory/resource leaks