Hi!
El sáb., 4 abr. 2020 12:22, Adam Majer escribió:
> On 2020-04-04 2:20 p.m., Lisandro Damián Nicanor Pérez Meyer wrote:
> > Hi! Just for the record, I haven't went ahead with this because I'm
> still very time constrained,
> > covid-19 is not precisely helping with that.
>
> Maybe a good
On 2020-04-04 2:20 p.m., Lisandro Damián Nicanor Pérez Meyer wrote:
> Hi! Just for the record, I haven't went ahead with this because I'm still
> very time constrained,
> covid-19 is not precisely helping with that.
Maybe a good idea here would be to split off the clang code model plugin into a
Hi! Just for the record, I haven't went ahead with this because I'm still
very time constrained, covid-19 is not precisely helping with that.
Package: qtcreator
Version: 4.11.0-2
Followup-For: Bug #952718
i just wasted about half an hour on researching this, so i'll summarize
my current understanding:
libclang-N needs to depend on libclang-common-N-dev, as otherwise it's
dysfunctional.
failing that, qtcreator needs to recommend
Hi!
I have discussed this with KDevelop's maintainer.
As Alexis states the code parser will not work with c++ projects if
the clang headers are not there. On the other hand if the c++ project
is using gcc instead of clang to build the wrong headers would be
displayed (even if the headers are
Le 14/03/2020 à 12:54, Sylvestre Ledru a écrit :
> Le 14/03/2020 à 12:45, Alexis Murzeau a écrit :
>>
>> I still think there should be a Depends (not Recommends) on
>> libclang-common-8-dev instead somewhere. (that is, directly from
>> qtcreator or indirectly)
> What is wrong with this solution?
>
Le 14/03/2020 à 12:45, Alexis Murzeau a écrit :
I still think there should be a Depends (not Recommends) on
libclang-common-8-dev instead somewhere. (that is, directly from
qtcreator or indirectly)
What is wrong with this solution?
Sorry if I missed a potential answer for this question.
S
Hi,
Le 05/03/2020 à 01:12, Nicholas D Steeves a écrit :
> Hi Lisandro,
>
> Lisandro Damián Nicanor Pérez Meyer writes:
>
>> Hi!
>>
>> On Wed, 4 Mar 2020 at 20:40, Nicholas D Steeves wrote:
>>>
>>> Hi Lisandro,
>>>
>>> Out of curiosity, could this be solved for a Debian (and derivatives)
>>>
Hi Lisandro,
Lisandro Damián Nicanor Pérez Meyer writes:
> Hi!
>
> On Wed, 4 Mar 2020 at 20:40, Nicholas D Steeves wrote:
>>
>> Hi Lisandro,
>>
>> Out of curiosity, could this be solved for a Debian (and derivatives)
>> context by changing the Recommends on clang and clang-tidy to their
>>
Le 05/03/2020 à 00:03, Lisandro Damián Nicanor Pérez Meyer a écrit :
> Hi again.
>
> On Wed, 4 Mar 2020 at 19:45, Alexis Murzeau wrote:
>>
>> Le 04/03/2020 à 22:46, Lisandro Damián Nicanor Pérez Meyer a écrit :
>>> Hi!
>>>
>>> El mié., 4 mar. 2020 18:11, Alexis Murzeau escribió:
>>>
Hi,
Hi!
On Wed, 4 Mar 2020 at 20:40, Nicholas D Steeves wrote:
>
> Hi Lisandro,
>
> Out of curiosity, could this be solved for a Debian (and derivatives)
> context by changing the Recommends on clang and clang-tidy to their
> versioned package names (eg: clang-8 and clang-tidy-8)?
No, this is not a
Hi Lisandro,
Out of curiosity, could this be solved for a Debian (and derivatives)
context by changing the Recommends on clang and clang-tidy to their
versioned package names (eg: clang-8 and clang-tidy-8)?
Cheers,
Nicholas
signature.asc
Description: PGP signature
Hi again.
On Wed, 4 Mar 2020 at 19:45, Alexis Murzeau wrote:
>
> Le 04/03/2020 à 22:46, Lisandro Damián Nicanor Pérez Meyer a écrit :
> > Hi!
> >
> > El mié., 4 mar. 2020 18:11, Alexis Murzeau escribió:
> >
> >> Hi,
> >>
> >> I've a question about whether libclang1-X should depend on
> >>
Le 04/03/2020 à 22:46, Lisandro Damián Nicanor Pérez Meyer a écrit :
> Hi!
>
> El mié., 4 mar. 2020 18:11, Alexis Murzeau escribió:
>
>> Hi,
>>
>> I've a question about whether libclang1-X should depend on
>> libclang-common-X-dev to always have the clang's builtin headers
>> available when
Hi!
El mié., 4 mar. 2020 18:11, Alexis Murzeau escribió:
> Hi,
>
> I've a question about whether libclang1-X should depend on
> libclang-common-X-dev to always have the clang's builtin headers
> available when libclang is installed.
>
Definitely not. Headers should depend upon the library, not
Hi,
I've a question about whether libclang1-X should depend on
libclang-common-X-dev to always have the clang's builtin headers
available when libclang is installed.
A bit of context:
QtCreator uses libclang for its code model. If clang's builtin headers
are not available in the system, libclang
reopen 952718
forwarded 952718 https://bugreports.qt.io/browse/QTCREATORBUG-23451
tag 952718 upstream
thanks
El vie., 28 feb. 2020 19:35, Alexis Murzeau escribió:
> Hi,
>
> On 28/02/2020 19:11, Lisandro Damián Nicanor Pérez Meyer wrote:
> >>* What outcome did you expect instead?
> >>
> >>
Subject: qtcreator: Clang code model fail to find stddef.h if
libclang-common-8-dev package is not installed
Package: qtcreator
Version: 4.11.0-2
Severity: normal
Dear Maintainer,
* What led up to the situation?
Install `qtcreator` but not the `libclang-common-8-dev` package
Note:
18 matches
Mail list logo