[Qt-creator] CMake and Include Files
Mike Jackson
imikejackson at gmail.com
Wed Jul 15 15:27:28 CEST 2009
I think Creator was using the CodeBlocks generator and not the KDevelop
one that I stated earlier.
As far as the include paths go CMake will find all the include paths
that are listed out in the CMakeLists.txt file. Usually through calls
like "include_directories" in the CMakeLists.txt files. In the
CodeBlocks generated XML file I think some of those were missing maybe
which is why we went looking in the visual studio xml files to see if
there were a more complete list, which there is.
In the end it is probably going to take someone intimate with both
CMake and Creator (or a collaboration between kitware and nokia
software) to get this done.. or someone else with a _lot_ of time on
their hands.
I would like to help but I am buried in other work currently.
Mike Jackson
On 2009-07-14 13:55:35 -0400, James <agnosticpope at gmail.com> said:
>
> I've tried this more or less -- in fact I have my own parser for the current
> XML file generated from cmake code blocks option. Haven't messed around
> with creating my own XML file with cmake though.
>
> So, I guess what I don't understand, is that it seems like the
> CMakelists.txt files are themselves incomplete and while one could write
> another parser for them in Cmake, then how would you find the headers?
> Wouldn't they still be missing? Or does cmake find them in some way? After
> all, cmake is a build manager, not a code manager, and at some basic level,
> it only cares about include paths, not include files. I wrote my own native
> cmakelist.txt parser for creator a while back (and still have it somewhere),
> so I'm somewhat familiar with the problem/question.
>
> If you'd like, I can post my current solution for parsing which seems to do
> a reasonably good job, based off of the current XML file from codeblocks.
> I'm using it to work on a fairly large project (a few hundred source files,
> some UI files, multiple directories) and the results are much better than
> the current release, IMHO, but it's not perfect, since in the end, I use a
> heuristic to try and find headers that aren't in cmakelists.
>
> --James
>
>
> On Tue, Jul 14, 2009 at 12:15 PM, Mike Jackson <imikejackson at gmail.com>wrote:
>
>> At some point Creator would actually generate a KDevelop project file
>> from your cmake based project by actually invoking CMake from creator.
>> This created an XML based file that Creator would then parse to gain
>> information about what/where to build things. This was slow and error
>> prone and tended to be missing information. There was a discussion on
>> the IRC channel that basically said there needs to be a "QtCreator"
>> option for CMake. CMake would then generate an XML File that has all
>> the information that QtCreator would need to create a project. It was
>> stated in the same IRC conversation that the only thing closest to what
>> was needed was the Visual studio project/solution files (since they are
>> XML). Using the Visual Studio Generator as a starting point for
>> creating a "QtCreator Generator" was then born. Of course once you have
>> cmake generating some XML files then you need QtCreator to be able to
>> parse the information contained in them.
>>
>> So to get started you would need to do the following:
>> Pull the Latest CVS version of CMake.
>> Study the code to figure out what needs to be done to create a new
>> generator.
>> Write the new generator for QtCreator (or append to the KDevelop one).
>> Test said generator on a project.
>>
>> Clone the latest version of QtCreator.
>> Find where the parsing of the XML files is happening
>> Add code to parse more detailed information from the new xml files that
>> were generated earlier.
>> Compile QtCreator
>> Test it out with the new project xml files that were generated with
>> CMake from above.
>>
>>
>> There is also the idea to have CMake generate .pro files but this was
>> quickly passed off as being too labor intensive/difficult to create.
>>
>> Of course the third option would be for Qt to drop qmake and go with
>> CMake instead ;-)
>>
>> Mike Jackson
>>
>> On 2009-07-13 22:40:50 -0400, James <agnosticpope at gmail.com> said:
>>
>>>
>>> The idea of creating a new CMake parsers sounds interesting, but how
>> would
>>> that work exactly? Part of the problem is that include files aren't
>>> contained in the CMake files, so you're still left, at some level, with
>>> parsing the actual c++ files or just adding everything ending in .h.
>>>
>>> How does visual studio xml work with CMake? I took a look, but couldn't
>>> find a single header file mentioned in anything...perhaps I'm looking in
>> the
>>> wrong place (I'm not terribly familiar with VS though).
>>>
>>> --James
>>>
>>> On Fri, Jul 10, 2009 at 8:28 AM, Mike Jackson <imikejackson at gmail.com
>>> wrote:
>>>
>>>> I tried Creator with CMake but there was _too_ much that I still had to
>>>> do on my own for each project to get things to work.
>>>> I know that several ideas had been discussed (mainly in the irc
>>>> channel) like creating a new generator for CMake that would produce xml
>>>> files that had all the needed information. I don't think this is going
>>>> anywhere as it really needs someone with the time to jump into the
>>>> catch-22 loop and start coding it up, both in CMake and in Creator.
>>>>
>>>> You need CMake to generate a QtCreator readable XML file. And you
>>>> need Creator to be able to parse it. I think after that a lot of the
>>>> issues with code completion would be mitigated as all the proper
>>>> include directories would be listed in the xml file that cmake produced.
>>>>
>>>> The Visual Studio XML files are pretty close to what is needed as
>>>> they have the most information. So starting with a clone of the Visual
>>>> Studio CMake Generator code might be a good start.
>>>>
>>>> Just my thoughts..
>>>>
>>>> Mike Jackson
>>>>
>>>> On 2009-07-07 22:28:33 -0400, James <agnosticpope at gmail.com> said:
>>>>
>>>>>
>>>>> Since I've been using Creator (1.0), cmake support has gotten much
>>>> better.
>>>>>
>>>>> Unfortunately, unless there's some step I'm missing, it still doesn't
>>>> parse
>>>>> files for autocompletion information. Additionally, since CMake files
>>>> don't
>>>>> necessarily include all the headers, the project tree itself may not
>> even
>>>> be
>>>>> complete.
>>>>>
>>>>> While I've been using it, I was maintaining a small modification that
>>>> looked
>>>>> for a foo.h whenever parsing a foo.c++ (and if found added it) and also
>>>> used
>>>>> the file extension to sort the headers from the source files.
>>>>> Unfortunately, things started behaving strangely this Monday as I think
>>>> the
>>>>> most recent mod broke my change;)
>>>>>
>>>>> I'm not wholly happy with my solution, and I'd be more than happy to
>> help
>>>> or
>>>>> write a proper solution to better accommodate CMake. IMHO, there's two
>>>>> issues: adding all headers properly and properly catagorizing the files
>>>> so
>>>>> that they can be parsed. There's various ways of doing this, none of
>>>> which
>>>>> are very good. There's my current solution, which misses files. It'd
>>>> also
>>>>> be possible to parse every source file and look for includes, maybe
>> with
>>>>> some assumption about having them at the beginning, but probably would
>> be
>>>>> very slow. A third would be to just look in every directory parsed for
>>>>> header files, which, again, may get stuff that's unused.
>>>>>
>>>>> What are the community/trolltech's thoughts on this? Or am I the only
>>>> one
>>>>> who uses Creator with CMake;)
>>>>>
>>>>> --James
>>>>
>>>> _______________________________________________
>>>> Qt-creator mailing list
>>>> Qt-creator at trolltech.com
>>>> http://lists.trolltech.com/mailman/listinfo/qt-creator
>>>>
>>>
>>>
>>> The idea of creating a new CMake parsers sounds interesting, but how
>> would =
>>> that work exactly?=A0 Part of the problem is that include files
>> aren't =
>>> contained in the CMake files, so you're still left, at some level,
>> with=
>>> parsing the actual c++ files or just adding everything ending in .h.<br>
>>> <br>How does visual studio xml work with CMake?=A0 I took a look, but
>> could=
>>> n't find a single header file mentioned in anything...perhaps I'm
>> l=
>>> ooking in the wrong place (I'm not terribly familiar with VS
>> though).<b=
>>> r>
>>> <br>--James<br><br><div class=3D"gmail_quote">On Fri, Jul 10, 2009 at
>> 8:28 =
>>> AM, Mike Jackson <span dir=3D"ltr"><<a href=3D"mailto:
>> imikejackson at gmail=
>>> .com">imikejackson at gmail.com</a>></span> wrote:<br><blockquote
>> class=3D"=
>>> gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin:
>> 0p=
>>> t 0pt 0pt 0.8ex; padding-left: 1ex;">
>>> I tried Creator with CMake but there was _too_ much that I still had
>> to<br>
>>> do on my own for each project to get things to work.<br>
>>> =A0I know that several ideas had been discussed (mainly in the irc<br>
>>> channel) like creating a new generator for CMake that would produce
>> xml<br>
>>> files that had all the needed information. I don't think this is
>> going<=
>>> br>
>>> anywhere as it really needs someone with the time to jump into the<br>
>>> catch-22 loop and start coding it up, both in CMake and in Creator.<br>
>>> <br>
>>> =A0You need CMake to generate a QtCreator readable XML file. And you<br>
>>> need Creator to be able to parse it. I think after that a lot of the<br>
>>> issues with code completion would be mitigated as all the proper<br>
>>> include directories would be listed in the xml file that cmake
>> produced.<br=
>>>>
>>> <br>
>>> =A0The Visual Studio XML files are pretty close to what is needed as<br>
>>> they have the most information. So starting with a clone of the
>> Visual<br>
>>> Studio CMake Generator code might be a good start.<br>
>>> <br>
>>> =A0Just my thoughts..<br>
>>> <br>
>>> Mike Jackson<br>
>>> <div><div></div><div class=3D"h5"><br>
>>> On 2009-07-07 22:28:33 -0400, James <<a href=3D"mailto:
>> agnosticpope at gmai=
>>> l.com">agnosticpope at gmail.com</a>> said:<br>
>>> <br>
>>> ><br>
>>> > Since I've been using Creator (1.0), cmake support has gotten
>> much=
>>> better.<br>
>>> ><br>
>>> > Unfortunately, unless there's some step I'm missing, it
>> still =
>>> doesn't parse<br>
>>> > files for autocompletion information. =A0Additionally, since CMake
>> fil=
>>> es don't<br>
>>> > necessarily include all the headers, the project tree itself may not
>> e=
>>> ven be<br>
>>> > complete.<br>
>>> ><br>
>>> > While I've been using it, I was maintaining a small modification
>> t=
>>> hat looked<br>
>>> > for a foo.h whenever parsing a foo.c++ (and if found added it) and
>> als=
>>> o used<br>
>>> > the file extension to sort the headers from the source files.<br>
>>> > Unfortunately, things started behaving strangely this Monday as I
>> thin=
>>> k the<br>
>>> > most recent mod broke my change;)<br>
>>> ><br>
>>> > I'm not wholly happy with my solution, and I'd be more than
>> ha=
>>> ppy to help or<br>
>>> > write a proper solution to better accommodate CMake. =A0IMHO,
>> there=
>>> 9;s two<br>
>>> > issues: adding all headers properly and properly catagorizing the
>> file=
>>> s so<br>
>>> > that they can be parsed. =A0There's various ways of doing this,
>> no=
>>> ne of which<br>
>>> > are very good. =A0There's my current solution, which misses
>> files.=
>>> =A0It'd also<br>
>>> > be possible to parse every source file and look for includes, maybe
>> wi=
>>> th<br>
>>> > some assumption about having them at the beginning, but probably
>> would=
>>> be<br>
>>> > very slow. =A0A third would be to just look in every directory
>> parsed =
>>> for<br>
>>> > header files, which, again, may get stuff that's unused.<br>
>>> ><br>
>>> > What are the community/trolltech's thoughts on this? =A0Or am I
>> th=
>>> e only one<br>
>>> > who uses Creator with CMake;)<br>
>>> ><br>
>>> > --James<br>
>>> <br>
>>> </div></div>_______________________________________________<br>
>>> Qt-creator mailing list<br>
>>> <a href=3D"mailto:Qt-creator at trolltech.com">Qt-creator at trolltech.com
>> </a><br=
>>>>
>>> <a href=3D"http://lists.trolltech.com/mailman/listinfo/qt-creator"
>> target=
>>> =3D"_blank">http://lists.trolltech.com/mailman/listinfo/qt-creator
>> </a><br>
>>> </blockquote></div><br>
>>
>>
>> _______________________________________________
>> Qt-creator mailing list
>> Qt-creator at trolltech.com
>> http://lists.trolltech.com/mailman/listinfo/qt-creator
>>
>
>
> I've tried this more or less -- in fact I have my own parser for the cu=
> rrent XML file generated from cmake code blocks option.=A0 Haven't mess=
> ed around with creating my own XML file with cmake though.<br><br>So, I gue=
> ss what I don't understand, is that it seems like the CMakelists.txt fi=
> les are themselves incomplete and while one could write another parser for =
> them in Cmake, then how would you find the headers?=A0 Wouldn't they st=
> ill be missing?=A0 Or does cmake find them in some way?=A0 After all, cmake=
> is a build manager, not a code manager, and at some basic level, it only c=
> ares about include paths, not include files.=A0 I wrote my own native cmake=
> list.txt parser for creator a while back (and still have it somewhere), so =
> I'm somewhat familiar with the problem/question.<br>
> <br>If you'd like, I can post my current solution for parsing which see=
> ms to do a reasonably good job, based off of the current XML file from code=
> blocks.=A0 I'm using it to work on a fairly large project (a few hundre=
> d source files, some UI files, multiple directories) and the results are mu=
> ch better than the current release, IMHO, but it's not perfect, since i=
> n the end, I use a heuristic to try and find headers that aren't in cma=
> kelists.<br>
> <br>--James<br><br><br><div class=3D"gmail_quote">On Tue, Jul 14, 2009 at 1=
> 2:15 PM, Mike Jackson <span dir=3D"ltr"><<a href=3D"mailto:imikejackson@=
> gmail.com">imikejackson at gmail.com</a>></span> wrote:<br><blockquote clas=
> s=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margi=
> n: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> At some point Creator would actually generate a KDevelop project file<br>
> from your cmake based project by actually invoking CMake from creator.<br>
> This created an XML based file that Creator would then parse to gain<br>
> information about what/where to build things. This was slow and error<br>
> prone and tended to be missing information. There was a discussion on<br>
> the IRC channel that basically said there needs to be a "QtCreator&quo=
> t;<br>
> option for CMake. CMake would then generate an XML File that has all<br>
> the information that QtCreator would need to create a project. It was<br>
> stated in the same IRC conversation that the only thing closest to what<br>
> was needed was the Visual studio project/solution files (since they are<br>
> XML). Using the Visual Studio Generator as a starting point for<br>
> creating a "QtCreator Generator" was then born. Of course once yo=
> u have<br>
> cmake generating some XML files then you need QtCreator to be able to<br>
> parse the information contained in them.<br>
> <br>
> =A0So to get started you would need to do the following:<br>
> Pull the Latest CVS version of CMake.<br>
> Study the code to figure out what needs to be done to create a new generato=
> r.<br>
> Write the new generator for QtCreator (or append to the KDevelop one).<br>
> Test said generator on a project.<br>
> <br>
> Clone the latest version of QtCreator.<br>
> Find where the parsing of the XML files is happening<br>
> Add code to parse more detailed information from the new xml files that<br>
> were generated earlier.<br>
> Compile QtCreator<br>
> Test it out with the new project xml files that were generated with<br>
> CMake from above.<br>
> <br>
> <br>
> There is also the idea to have CMake generate .pro files but this was<br>
> quickly passed off as being too labor intensive/difficult to create.<br>
> <br>
> Of course the third option would be for Qt to drop qmake and go with<br>
> CMake instead ;-)<br>
> <br>
> Mike Jackson<br>
> <div><div></div><div class=3D"h5"><br>
> On 2009-07-13 22:40:50 -0400, James <<a href=3D"mailto:agnosticpope at gmai=
> l.com">agnosticpope at gmail.com</a>> said:<br>
> <br>
> ><br>
> > The idea of creating a new CMake parsers sounds interesting, but how w=
> ould<br>
> > that work exactly? =A0Part of the problem is that include files aren&#=
> 39;t<br>
> > contained in the CMake files, so you're still left, at some level,=
> with<br>
> > parsing the actual c++ files or just adding everything ending in .h.<b=
> r>
> ><br>
> > How does visual studio xml work with CMake? =A0I took a look, but coul=
> dn't<br>
> > find a single header file mentioned in anything...perhaps I'm look=
> ing in the<br>
> > wrong place (I'm not terribly familiar with VS though).<br>
> ><br>
> > --James<br>
> ><br>
> > On Fri, Jul 10, 2009 at 8:28 AM, Mike Jackson <<a href=3D"mailto:im=
> ikejackson at gmail.com">imikejackson at gmail.com</a>>wrote:<br>
> ><br>
> >> I tried Creator with CMake but there was _too_ much that I still h=
> ad to<br>
> >> do on my own for each project to get things to work.<br>
> >> I know that several ideas had been discussed (mainly in the irc<br=
>>
> >> channel) like creating a new generator for CMake that would produc=
> e xml<br>
> >> files that had all the needed information. I don't think this =
> is going<br>
> >> anywhere as it really needs someone with the time to jump into the=
> <br>
> >> catch-22 loop and start coding it up, both in CMake and in Creator=
> .<br>
> >><br>
> >> You need CMake to generate a QtCreator readable XML file. And you<=
> br>
> >> need Creator to be able to parse it. I think after that a lot of t=
> he<br>
> >> issues with code completion would be mitigated as all the proper<b=
> r>
> >> include directories would be listed in the xml file that cmake pro=
> duced.<br>
> >><br>
> >> The Visual Studio XML files are pretty close to what is needed as<=
> br>
> >> they have the most information. So starting with a clone of the Vi=
> sual<br>
> >> Studio CMake Generator code might be a good start.<br>
> >><br>
> >> Just my thoughts..<br>
> >><br>
> >> Mike Jackson<br>
> >><br>
> >> On 2009-07-07 22:28:33 -0400, James <<a href=3D"mailto:agnostic=
> pope at gmail.com">agnosticpope at gmail.com</a>> said:<br>
> >><br>
> >>><br>
> >>> Since I've been using Creator (1.0), cmake support has got=
> ten much<br>
> >> better.<br>
> >>><br>
> >>> Unfortunately, unless there's some step I'm missing, i=
> t still doesn't<br>
> >> parse<br>
> >>> files for autocompletion information. =A0Additionally, since C=
> Make files<br>
> >> don't<br>
> >>> necessarily include all the headers, the project tree itself m=
> ay not even<br>
> >> be<br>
> >>> complete.<br>
> >>><br>
> >>> While I've been using it, I was maintaining a small modifi=
> cation that<br>
> >> looked<br>
> >>> for a foo.h whenever parsing a foo.c++ (and if found added it)=
> and also<br>
> >> used<br>
> >>> the file extension to sort the headers from the source files.<=
> br>
> >>> Unfortunately, things started behaving strangely this Monday a=
> s I think<br>
> >> the<br>
> >>> most recent mod broke my change;)<br>
> >>><br>
> >>> I'm not wholly happy with my solution, and I'd be more=
> than happy to help<br>
> >> or<br>
> >>> write a proper solution to better accommodate CMake. =A0IMHO, =
> there's two<br>
> >>> issues: adding all headers properly and properly catagorizing =
> the files<br>
> >> so<br>
> >>> that they can be parsed. =A0There's various ways of doing =
> this, none of<br>
> >> which<br>
> >>> are very good. =A0There's my current solution, which misse=
> s files. =A0It'd<br>
> >> also<br>
> >>> be possible to parse every source file and look for includes, =
> maybe with<br>
> >>> some assumption about having them at the beginning, but probab=
> ly would be<br>
> >>> very slow. =A0A third would be to just look in every directory=
> parsed for<br>
> >>> header files, which, again, may get stuff that's unused.<b=
> r>
> >>><br>
> >>> What are the community/trolltech's thoughts on this? =A0Or=
> am I the only<br>
> >> one<br>
> >>> who uses Creator with CMake;)<br>
> >>><br>
> >>> --James<br>
> >><br>
> >> _______________________________________________<br>
> >> Qt-creator mailing list<br>
> >> <a href=3D"mailto:Qt-creator at trolltech.com">Qt-creator at trolltech.c=
> om</a><br>
> >> <a href=3D"http://lists.trolltech.com/mailman/listinfo/qt-creator"=
> target=3D"_blank">http://lists.trolltech.com/mailman/listinfo/qt-creator</=
> a><br>
> >><br>
> ><br>
> ><br>
> > The idea of creating a new CMake parsers sounds interesting, but how w=
> ould =3D<br>
> </div></div>> that work exactly?=3DA0 Part of the problem is that includ=
> e files aren&#39;t =3D<br>
> > contained in the CMake files, so you&#39;re still left, at some le=
> vel, with=3D<br>
> > =A0parsing the actual c++ files or just adding everything ending in .h=
> .<br><br>
> > <br>How does visual studio xml work with CMake?=3DA0 I took a lo=
> ok, but could=3D<br>
> > n&#39;t find a single header file mentioned in anything...perhaps =
> I&#39;m l=3D<br>
> > ooking in the wrong place (I&#39;m not terribly familiar with VS t=
> hough).<b=3D<br>
> > r><br>
> > <br>--James<br><br><div class=3D3D"gmail_quo=
> te">On Fri, Jul 10, 2009 at 8:28 =3D<br>
> > AM, Mike Jackson <span dir=3D3D"ltr">&lt;<a hre=
> f=3D3D"mailto:<a href=3D"mailto:imikejackson at gmail">imikejackson at gmail=
> </a>=3D<br>
> > .com"><a href=3D"mailto:imikejackson at gmail.com">imikejackson at g=
> mail.com</a></a>&gt;</span> wrote:<br><blockquote =
> class=3D3D"=3D<br>
> > gmail_quote" style=3D3D"border-left: 1px solid rgb(204, 204,=
> 204); margin: 0p=3D<br>
> > t 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
> > I tried Creator with CMake but there was _too_ much that I still had t=
> o<br><br>
> > do on my own for each project to get things to work.<br><br>
> > =A0=3DA0I know that several ideas had been discussed (mainly in the ir=
> c<br><br>
> > channel) like creating a new generator for CMake that would produce xm=
> l<br><br>
> > files that had all the needed information. I don&#39;t think this =
> is going<=3D<br>
> > br><br>
> > anywhere as it really needs someone with the time to jump into the<=
> br><br>
> > catch-22 loop and start coding it up, both in CMake and in Creator.<=
> ;br><br>
> > <br><br>
> > =A0=3DA0You need CMake to generate a QtCreator readable XML file. And =
> you<br><br>
> > need Creator to be able to parse it. I think after that a lot of the&l=
> t;br><br>
> > issues with code completion would be mitigated as all the proper<br=
> ><br>
> > include directories would be listed in the xml file that cmake produce=
> d.<br=3D<br>
> >><br>
> > <br><br>
> > =A0=3DA0The Visual Studio XML files are pretty close to what is needed=
> as<br><br>
> > they have the most information. So starting with a clone of the Visual=
> <br><br>
> > Studio CMake Generator code might be a good start.<br><br>
> > <br><br>
> > =3DA0Just my thoughts..<br><br>
> > <br><br>
> > Mike Jackson<br><br>
> > <div><div></div><div class=3D3D"h5">=
> <br><br>
> > On 2009-07-07 22:28:33 -0400, James &lt;<a href=3D3D"mailt=
> o:<a href=3D"mailto:agnosticpope at gmai">agnosticpope at gmai</a>=3D<br>
> > <a href=3D"http://l.com" target=3D"_blank">l.com</a>"><a href=
> =3D"mailto:agnosticpope at gmail.com">agnosticpope at gmail.com</a></a>&=
> ;gt; said:<br><br>
> > <br><br>
> > &gt;<br><br>
> > &gt; Since I&#39;ve been using Creator (1.0), cmake support ha=
> s gotten much=3D<br>
> > =A0better.<br><br>
> > &gt;<br><br>
> > &gt; Unfortunately, unless there&#39;s some step I&#39;m m=
> issing, it still =3D<br>
> > doesn&#39;t parse<br><br>
> > &gt; files for autocompletion information. =3DA0Additionally, sinc=
> e CMake fil=3D<br>
> > es don&#39;t<br><br>
> > &gt; necessarily include all the headers, the project tree itself =
> may not e=3D<br>
> > ven be<br><br>
> > &gt; complete.<br><br>
> > &gt;<br><br>
> > &gt; While I&#39;ve been using it, I was maintaining a small m=
> odification t=3D<br>
> > hat looked<br><br>
> > &gt; for a foo.h whenever parsing a foo.c++ (and if found added it=
> ) and als=3D<br>
> > o used<br><br>
> > &gt; the file extension to sort the headers from the source files.=
> <br><br>
> > &gt; Unfortunately, things started behaving strangely this Monday =
> as I thin=3D<br>
> > k the<br><br>
> > &gt; most recent mod broke my change;)<br><br>
> > &gt;<br><br>
> > &gt; I&#39;m not wholly happy with my solution, and I&#39;=
> d be more than ha=3D<br>
> > ppy to help or<br><br>
> > &gt; write a proper solution to better accommodate CMake. =3DA0IMH=
> O, there&#3=3D<br>
> > 9;s two<br><br>
> > &gt; issues: adding all headers properly and properly catagorizing=
> the file=3D<br>
> > s so<br><br>
> > &gt; that they can be parsed. =3DA0There&#39;s various ways of=
> doing this, no=3D<br>
> > ne of which<br><br>
> > &gt; are very good. =3DA0There&#39;s my current solution, whic=
> h misses files.=3D<br>
> > =A0=3DA0It&#39;d also<br><br>
> > &gt; be possible to parse every source file and look for includes,=
> maybe wi=3D<br>
> > th<br><br>
> > &gt; some assumption about having them at the beginning, but proba=
> bly would=3D<br>
> > =A0be<br><br>
> > &gt; very slow. =3DA0A third would be to just look in every direct=
> ory parsed =3D<br>
> > for<br><br>
> > &gt; header files, which, again, may get stuff that&#39;s unus=
> ed.<br><br>
> > &gt;<br><br>
> > &gt; What are the community/trolltech&#39;s thoughts on this? =
> =3DA0Or am I th=3D<br>
> > e only one<br><br>
> > &gt; who uses Creator with CMake;)<br><br>
> > &gt;<br><br>
> > &gt; --James<br><br>
> > <br><br>
> > </div></div>______________________________________________=
> _<br><br>
> > Qt-creator mailing list<br><br>
> > <a href=3D3D"mailto:<a href=3D"mailto:Qt-creator at trolltech.com=
> ">Qt-creator at trolltech.com</a>"><a href=3D"mailto:Qt-creator at trollt=
> ech.com">Qt-creator at trolltech.com</a></a><br=3D<br>
> >><br>
> > <a href=3D3D"<a href=3D"http://lists.trolltech.com/mailman/lis=
> tinfo/qt-creator" target=3D"_blank">http://lists.trolltech.com/mailman/list=
> info/qt-creator</a>" target=3D<br>
> > =3D3D"_blank"><a href=3D"http://lists.trolltech.com/mailm=
> an/listinfo/qt-creator" target=3D"_blank">http://lists.trolltech.com/mailma=
> n/listinfo/qt-creator</a></a><br><br>
> > </blockquote></div><br><br>
> <div><div></div><div class=3D"h5"><br>
> <br>
> _______________________________________________<br>
> Qt-creator mailing list<br>
> <a href=3D"mailto:Qt-creator at trolltech.com">Qt-creator at trolltech.com</a><br=
>>
> <a href=3D"http://lists.trolltech.com/mailman/listinfo/qt-creator" target=
> =3D"_blank">http://lists.trolltech.com/mailman/listinfo/qt-creator</a><br>
> </div></div></blockquote></div><br>
More information about the Qt-creator-old
mailing list