On Thu, May 05, 2016 at 07:54:53AM -0400, william.croc...@analog.com wrote:
>
> >
> >>I have never been able to get creator to work. The 5 series won't even run
> >>under my versions of VNC and the NX virtual desktops. This apparently due
> >>to a
> >>dependency on new visual fluff.
> >
> >Qt Q
I have never been able to get creator to work. The 5 series won't even run
under my versions of VNC and the NX virtual desktops. This apparently due to a
dependency on new visual fluff.
Qt Quick doesn't indeed not work well over VNC. The common workaround is to
not load Quick based plugins
On Thu, May 05, 2016 at 06:53:54AM -0400, Bill Crocker wrote:
> >>I am trying to port my Qt project to a cmake based build so I can use CLion
> >>for debugging.
> >
> >Why is CLion preferable for you to do Qt debugging, opposed to e.g. using Qt
> >Creator?
> >
>
> Because CLion works out of the bo
On 05/05/2016 06:08 AM, Jean-Michaël Celerier wrote:
I am almost there, but when it links there are symbols undefined.
From my experience the symbols I am seeing are typical of missing moc files.
You should still post your error messages I think, maybe it's some library that
Qt links automati
05.05.2016, 13:54, "Bill Crocker" :
>>> I am trying to port my Qt project to a cmake based build so
>>> I can use CLion for debugging.
>>
>> Why is CLion preferable for you to do Qt debugging, opposed to
>> e.g. using Qt Creator?
>
> Because CLion works out of the box and I am assuming
> that
I am trying to port my Qt project to a cmake based build so
I can use CLion for debugging.
Why is CLion preferable for you to do Qt debugging, opposed to
e.g. using Qt Creator?
Because CLion works out of the box and I am assuming
that I can use it to debug my app once I get it to build
wit
> I am almost there, but when it links there are symbols undefined.
> From my experience the symbols I am seeing are typical of missing moc
files.
You should still post your error messages I think, maybe it's some library
that Qt links automatically but
that you have to link by hand with CMake ?
On 05/04/2016 01:07 PM, Thiago Macieira wrote:
On quarta-feira, 4 de maio de 2016 10:08:27 PDT Bill Crocker wrote:
From my experience the symbols I am seeing are typical of missing moc
files. I know I have all of my #include "abc.moc" statements in place
because my project builds fine with qm
On quarta-feira, 4 de maio de 2016 10:08:27 PDT Bill Crocker wrote:
> From my experience the symbols I am seeing are typical of missing moc
> files. I know I have all of my #include "abc.moc" statements in place
> because my project builds fine with qmake.
That probably is. You need to tell cmake
Hello:
I am trying to port my Qt project to a cmake based build so
I can use CLion for debugging.
I am almost there, but when it links there are symbols undefined.
From my experience the symbols I am seeing are typical of missing moc files.
I know I have all of my #include "abc.moc" statements i
10 matches
Mail list logo
