Hi,
I spent over 4 hours debugging why on hell codelite crashes when using the protocol way (the Windows way) and at the end I have decided that since on linux forking new process is very cheap, we can use this implementation rather than the daemon approach. On Windows spawning new process is an expensive and very slow operation, so making a daemon make sense there - on Linux its not the case.
For you question: On Linux, you just need to save the settings and on the next invocation they will be used, while on winodws a restart is required (m_cppcheckProcess->Terminate())
Eran
CppCheck plugin
-
eranif
- CodeLite Plugin
- Posts: 6372
- Joined: Wed Feb 06, 2008 9:29 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: CppCheck plugin
Make sure you have read the HOW TO POST thread
-
jfouche
- CodeLite Guru
- Posts: 351
- Joined: Mon Oct 20, 2008 7:26 pm
- Genuine User: Yes
- IDE Question: C++
- Location: France
- Contact:
Re: CppCheck plugin
OK, here is a patch. As I do not have Linux (nor Mac), I didn't test my modification on those plateforms). Have look.
You do not have the required permissions to view the files attached to this post.
Jérémie
-
eranif
- CodeLite Plugin
- Posts: 6372
- Joined: Wed Feb 06, 2008 9:29 pm
- Genuine User: Yes
- IDE Question: C++
- Contact:
Re: CppCheck plugin
Applied. Some minior modifications were needed for Linux. Committed in SVN 3024jfouche wrote:OK, here is a patch. As I do not have Linux (nor Mac), I didn't test my modification on those plateforms). Have look.
Eran
Make sure you have read the HOW TO POST thread