kdevelop, php and xdebug

[santilin]

I have compiled it perfectly. Some issues:

* As I have debian and not configured a prefix por instalation in 
CMakeList.txt, it is installed on a path that is not recognized.

   # sudo make install

   Install the project...
   -- Install configuration: ""
   -- Installing: 
/usr/local/lib/x86_64-linux-gnu/plugins/kdevplatform/27/kdevxdebug.so
   -- Set runtime path of 
"/usr/local/lib/x86_64-linux-gnu/plugins/kdevplatform/27/kdevxdebug.so" 
to "/usr/local/lib/x86_64-linux-gnu"

When I open kdevelop and look into plugins, I can't see php-xdebug, so I 
think it is not loaded.

* The name of the shared library doesn't start with lib

* I don't know how to add 
/usr/local/lib/x86_64-linux-gnu/plugins/kdevplatform/27/ to KDE_DIRS or 
how to make kdevelop look into that directory.

Anyway, many thanks for upgrading this extension.


On 29/09/17 18:03, Kevin Funk wrote:
> On Friday, 29 September 2017 08:56:08 CEST santilin wrote:
>> Hi, I love developing with KDevelop and I was happy developing in PHP
>> with KDevelop4. But recently I had to update my debian to version 9 and
>> now, KDevelop5 doesn't have php-xdebug ported.
>>
>> I can spare some time (not much really) helping porting php-xdebu to
>> KDevelop5, but I must admit that although I have a lot of experience
>> with C++ and Qt, I have never used cmake nor KDevelop libraries.
> Heya Santilin,
>
> kdev-xdebug got fully ported for KDevelop 5.x now.
>
> Please try and report back.
>
> Regards,
> Kevin
>
>> I have tried to port the CMakeList.txt from php-xdebug to KDevelop5, but
>> I am not confident as I am used to the GNU autotools world.
>>
>> Then, I would like you to help me decide on the following two options:
>>
>>
>> 1) (preferred) Join kdev-xdebug with kdevelop-php so that I can start
>> coding quickly as the CMakeList.txt is already ported and I would add
>> only the relevant kdev-xdebug files and maybe some libraries
>>
>> 2) Have the kdev-xdebug CMakeList.txt ported to KDevelop5 by someone
>> with more experience and then I would follow porting the rest of the code.
>>
>>
>> The option 1 is my preferred as I have always wanted those plugins to
>> come together and I wonder why are they separated.
>>
>>
>> Kind regards
>>
>> --santilín
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20171004/f11e179e/attachment.html>