On 04/20/2018 02:28 PM, Elvis Stansvik wrote:
Roland, I think when you said in your original mail that the problem
occurred "When typing in the editor and compiling", everyone though
you meant you were getting compilation errors (so not just an
auto-completion issue).
If this is only about au
On 04/23/2018 02:15 AM, Thiago Macieira wrote:
On Friday, 20 April 2018 05:19:40 PDT Roland Hughes wrote:
DO NOT write that. The correct line for libusb is:
#include
If that file is not in your default search path, then add it to
INCLUDEPATH or via pkg-config.
PKGCONFIG += libusb-1.0
The
On Fri, 20 Apr 2018 14:28:01 -0500
Roland Hughes wrote:
> On 04/20/2018 08:28 AM, Christian Kandeler wrote:
> >> Yes, there is a force here. Having to inform the environment about a
> >> directory underneath /usr/include is a force. By design all directories
> >> in that tree are searched.
> >
On Friday, 20 April 2018 12:17:06 PDT Roland Hughes wrote:
> My understanding is completely correct and the test posted in this
> thread proved it. Manually creating aa directory under /usr/include had
> aa show up in QtCreator. Manually creating a.a does not appear in QtCreator.
That may be, but
2018-04-20 21:28 GMT+02:00 Elvis Stansvik :
> 2018-04-20 21:17 GMT+02:00 Roland Hughes :
>>
>>
>> On 04/20/2018 08:04 AM, Konstantin Tokarev wrote:
>>>
>>>
>>> 20.04.2018, 16:01, "Roland Hughes" :
On 04/20/2018 07:55 AM, Konstantin Tokarev wrote:
>
> 20.04.2018, 15:19, "Roland H
2018-04-20 21:17 GMT+02:00 Roland Hughes :
>
>
> On 04/20/2018 08:04 AM, Konstantin Tokarev wrote:
>>
>>
>> 20.04.2018, 16:01, "Roland Hughes" :
>>>
>>> On 04/20/2018 07:55 AM, Konstantin Tokarev wrote:
20.04.2018, 15:19, "Roland Hughes" :
>
> On 04/20/2018 06:40 AM, Thiago Ma
On 04/20/2018 08:28 AM, Christian Kandeler wrote:
Yes, there is a force here. Having to inform the environment about a
directory underneath /usr/include is a force. By design all directories
in that tree are searched.
What makes you think that?
Christian
30+ years in IT and the test posted e
On 04/20/2018 08:04 AM, Konstantin Tokarev wrote:
20.04.2018, 16:01, "Roland Hughes" :
On 04/20/2018 07:55 AM, Konstantin Tokarev wrote:
20.04.2018, 15:19, "Roland Hughes" :
On 04/20/2018 06:40 AM, Thiago Macieira wrote:
On Wednesday, 18 April 2018 10:18:05 PDT Konstantin Tokarev wro
On Friday, 20 April 2018 05:19:40 PDT Roland Hughes wrote:
> > DO NOT write that. The correct line for libusb is:
> >
> > #include
> >
> > If that file is not in your default search path, then add it to
> > INCLUDEPATH or via pkg-config.
> >
> > PKGCONFIG += libusb-1.0
>
> The problem isn't th
On Fri, 20 Apr 2018 08:00:56 -0500
Roland Hughes wrote:
> Yes, there is a force here. Having to inform the environment about a
> directory underneath /usr/include is a force. By design all directories
> in that tree are searched.
What makes you think that?
Christian
_
20.04.2018, 16:01, "Roland Hughes" :
> On 04/20/2018 07:55 AM, Konstantin Tokarev wrote:
>> 20.04.2018, 15:19, "Roland Hughes" :
>>> On 04/20/2018 06:40 AM, Thiago Macieira wrote:
On Wednesday, 18 April 2018 10:18:05 PDT Konstantin Tokarev wrote:
> #include
DO NOT write that.
On 04/20/2018 07:55 AM, Konstantin Tokarev wrote:
20.04.2018, 15:19, "Roland Hughes" :
On 04/20/2018 06:40 AM, Thiago Macieira wrote:
On Wednesday, 18 April 2018 10:18:05 PDT Konstantin Tokarev wrote:
#include
DO NOT write that. The correct line for libusb is: #include If that
file is n
20.04.2018, 15:19, "Roland Hughes" :
> On 04/20/2018 06:40 AM, Thiago Macieira wrote:
>> On Wednesday, 18 April 2018 10:18:05 PDT Konstantin Tokarev wrote:
>>> #include
>>
>> DO NOT write that. The correct line for libusb is: #include If
>> that file is not in your default search path, then ad
On 04/20/2018 06:40 AM, Thiago Macieira wrote:
On Wednesday, 18 April 2018 10:18:05 PDT Konstantin Tokarev wrote:
#include
DO NOT write that. The correct line for libusb is:
#include
If that file is not in your default search path, then add it to INCLUDEPATH or
via pkg-config.
PKGCONFIG
On Wednesday, 18 April 2018 10:18:05 PDT Konstantin Tokarev wrote:
> #include
DO NOT write that. The correct line for libusb is:
#include
If that file is not in your default search path, then add it to INCLUDEPATH or
via pkg-config.
PKGCONFIG += libusb-1.0
--
Thiago Macieira - thiago.macie
On 04/18/2018 12:18 PM, Konstantin Tokarev wrote:
18.04.2018, 20:03, "Roland Hughes" :
On 04/18/2018 11:52 AM, Konstantin Tokarev wrote:
18.04.2018, 19:43, "Roland Hughes" :
All, KDE Neon all updates applied. QtCreator 4.4.1 Qt 5.9.3 from repos. Also installed
libusb packages from repos. r
18.04.2018, 20:03, "Roland Hughes" :
> On 04/18/2018 11:52 AM, Konstantin Tokarev wrote:
>> 18.04.2018, 19:43, "Roland Hughes" :
>>> All, KDE Neon all updates applied. QtCreator 4.4.1 Qt 5.9.3 from repos.
>>> Also installed libusb packages from repos.
>>> roland@roland-I5-HP-Compaq-8300-Elite-
On 04/18/2018 11:52 AM, Konstantin Tokarev wrote:
18.04.2018, 19:43, "Roland Hughes" :
All,
KDE Neon all updates applied. QtCreator 4.4.1 Qt 5.9.3 from repos. Also
installed libusb packages from repos.
roland@roland-I5-HP-Compaq-8300-Elite-SFF-PC:~$ ls /usr/include/libusb-1.0/
libusb.h
18.04.2018, 19:43, "Roland Hughes" :
> All,
>
> KDE Neon all updates applied. QtCreator 4.4.1 Qt 5.9.3 from repos. Also
> installed libusb packages from repos.
>
> roland@roland-I5-HP-Compaq-8300-Elite-SFF-PC:~$ ls /usr/include/libusb-1.0/
>
> libusb.h
>
> When typing in the editor and compilin
All,
KDE Neon all updates applied. QtCreator 4.4.1 Qt 5.9.3 from repos. Also
installed libusb packages from repos.
roland@roland-I5-HP-Compaq-8300-Elite-SFF-PC:~$ ls /usr/include/libusb-1.0/
libusb.h
When typing in the editor and compiling, libusb.h is not found. Other
headers from other d
20 matches
Mail list logo
