Re: Re: Which IDE do you recommend for php-src development?
| From: | Larry Garfield | Date: | Tue, 17 Sep 2024 04:38:19 +0000 |
| Subject: | Re: Re: Which IDE do you recommend for php-src development? | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-125576@lists.php.net to get a copy of this message | ||
On Mon, Sep 16, 2024, at 7:06 PM, Hans Henrik Bergan wrote:
> +1 for VSCode, I use it practically everywhere these days,
> HTML/Javascript/TypeScript/PHP/C/C++/Python/Lua, all on VSCode.
>
> On Mon, 16 Sept 2024 at 13:07, Barel <barel.barelon@gmail.com> wrote:
>>
>> On Sat, 14 Sept 2024 at 23:44, Barel <barel.barelon@gmail.com> wrote:
>>>
>>> Hi
>>>
>>> For C/C++ development I usually use CLion from Jetbrains but I tried to use it with
>>> php-src and was unable to get it to work properly. CLion really insists on using CMake and has only
>>> quite limited support for makefiles. After trying to get it to work unsuccessfully I am ready to try
>>> something else.
>>>
>>> So which IDE would you recommend for php-src development? I understand that people
>>> probably have many different preferences but I wondered if there was something that most php
>>> internals developers used. One important feature would be to easily work with the project running on
>>> a docker container
>>>
>>> Thanks in advance!
>>>
>>> Carlos
>>
>>
>> Answering myself in case someone finds this useful in the future.
>>
>> Several people recommended VSCode so decided to give it a try. I found this guide which
>> describes very well what you need to do to get VSCode working for a php-src project hosted in a
>> docker container. Works brilliantly, I am able to work with the code in the container using all
>> VSCode features, including debugging with GDB. Nice!
>>
>> https://bogomolov.tech/php-extension-development/
Please please someone capture the details of this thread somewhere on the wiki or php.net, or maybe
even in the php-src repo itself. We really need to have good "how to get from git clone to a
working C debugger" instructions.
--Larry Garfield