Hi Mateus, I would suggest to *not* install the CM executable, but run it from an IDE. During development you'll want to debug the application (set breakpoints and so on) so you'll need to either run from IDE or attach debugger.
Even better, I would suggest you to make a "bundle" with TelepathyQt, CM and resiprocate library in a single project. This way you'll be able to debug any of TelepathyQt <-> CM <-> Resiprocate at same time. I made a script [1] to setup such "bundle" for TpQt + Morse/TelegramQt + Nonsense/QXmpp. You can base on it, if you want. Take a note that once you'll have things work in your IDE, you'll still have to test everything via proper installation. [1] https://github.com/TelepathyQt/telepathy-qt/wiki/Project-with-CMs-as-examples On Sun, May 22, 2016 at 2:04 AM, Daniel Pocock <dan...@pocock.pro> wrote: > > > On 21/05/16 20:54, Mateus Bellomo wrote: >> Hello, >> >> I'm using telepathy-resiprocate and I want to keep killing and >> restarting the process because I'm doing some changes in the code. >> >> I noticed that when I kill the telepathy-resiprocate process it starts >> again by itself (without me executing the telepathy-resiprocate >> executable). So I wonder if there is a way to kill the process in a way >> that only I could start it again later. >> > > > That is probably because you used this script: > > https://github.com/resiprocate/resiprocate/blob/master/apps/telepathy/deploy-properties > > If you remove the files it installed and restart mission-control again > then it won't keep trying to start telepathy-resiprocate for you. > _______________________________________________ > telepathy mailing list > telepathy@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/telepathy _______________________________________________ telepathy mailing list telepathy@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/telepathy
