Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Qt Support?

I guess what I'm also saying is that you don't need a New Qt Project
wizard either. We can integrated it into the standard new C++ wizard,
which I also plan to clean up for CDT 8, BTW.

On Wed, Jun 16, 2010 at 2:30 PM, Marc-Andre Laperle
<malaperle@xxxxxxxxxxxxx> wrote:
> I think that's already in the Qt Eclipse Integration plug-in, no?
>
> http://qt.nokia.com/developer/eclipse-integration/
>
> Marc-Andre
>
> On 16/06/2010 2:28 PM, Doug Schaefer wrote:
>>
>> Actually, as I get more into Qt, you don't really need an additional
>> builder. The makefile ensure it keeps itself up to date.
>>
>> So all you really need then is a template to generate the .pro and run
>> the initial qmake. This is getting very close to what I did for
>> Android. I can start with that if there are no objections.
>>
>> Doug
>>
>> On Wed, Jun 16, 2010 at 1:13 PM, Doug Schaefer<cdtdoug@xxxxxxxxx>  wrote:
>>
>>>
>>> Cool. The things I've quickly thought of is a New Qt Project wizard to
>>> simplify and control project creation, a qmake builder that runs qmake
>>> when the project file has changed, and potentially a nicer qmake
>>> project file editor. And if you want to go the extra mile, some way to
>>> generate the list of source files that can be included in the project
>>> file.
>>>
>>> I think the UI designer could be left as an external tool, but if you
>>> guys have a lot of resources to put into that, you could integrate it,
>>> but then you'd always be playing catchup with the already pretty
>>> decent Qt Designer.
>>>
>>> I'm looking at how Wascana can pick up the Qt install and set the
>>> paths correctly to launch qmake and find the DLLs at debug time for
>>> Windows. That shouldn't be a problem on Linux, and I'm not sure of
>>> Mac. Qt embedded might be different though.
>>>
>>> Anyway, that's just my 2 cents. Look forward to seeing the community
>>> help on this.
>>>
>>> On Wed, Jun 16, 2010 at 12:55 PM,<ken.ryall@xxxxxxxxx>  wrote:
>>>
>>>>
>>>> Doug,
>>>>
>>>> The short answer is yes we are working on better Qt support and yes you
>>>> should get started because we want it to be a CDT community effort and
>>>> we
>>>> need your help.
>>>>
>>>> I'll let Warren give you a more detailed response since he's been
>>>> thinking
>>>> about exactly what to do.
>>>>
>>>> Regards - Ken
>>>>
>>>>
>>>>>
>>>>> From: Schaefer Doug<cdtdoug@xxxxxxxxx>
>>>>> Reply-To: "CDT General developers list."<cdt-dev@xxxxxxxxxxx>
>>>>> Date: Wed, 16 Jun 2010 17:49:00 +0200
>>>>> To: "CDT General developers list."<cdt-dev@xxxxxxxxxxx>
>>>>> Subject: [cdt-dev] Qt Support?
>>>>>
>>>>> Qt flew by my vision again today and distracted me. Having got the
>>>>> Android NDK build system integrated with CDT and enjoying the
>>>>> experience. I come back to Qt and we should do the same there. Since
>>>>> Qt is cross platform, it probably fits better under the CDT umbrella.
>>>>>
>>>>> So, question mainly to the Nokia guys, is anyone working on better Qt
>>>>> support for CDT? Or should I get started.
>>>>>
>>>>> Doug.
>>>>> _______________________________________________
>>>>> cdt-dev mailing list
>>>>> cdt-dev@xxxxxxxxxxx
>>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>>
>>>>
>>>> _______________________________________________
>>>> cdt-dev mailing list
>>>> cdt-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>>>
>>>>
>>>
>>>
>>
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>>
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>


Back to the top