llvm dev - Oct 2008 - [LLVMdev] Header files on VC project (was: Growing up CMake)

Óscar Fuentes wrote:
> All the headers in include/llvm? Or just those local to each library?
>   
All the headers. It's a pain to manually update the project files but it 
will be a bigger pain trying to use them without the include files.. 
included.
>   
>> -Could you please also add Clang to the CMake system ?
>>     
>
> So far we are having sunny days here. Maybe if the weather changes...
>   
Ok, I hope a storm is coming your way.. :-)


-Argiris

Argiris Kirtzidis <akyrtzi at gmail.com> writes:
> Óscar Fuentes wrote:
>> All the headers in include/llvm? Or just those local to each library?
>>   
>
> All the headers. It's a pain to manually update the project files but
it
> will be a bigger pain trying to use them without the include files.. 
> included.
There are almost 300 headers under include/llvm. I can put them all on
*each* project, plus local headers. This seems a lot of baggage.

I've checked that Intellisense can jump to an unlisted header file when
you ask for a declaration on a cpp file. So, what's the benefit of
having the header files explicitly listed in the solution? If it is for
text searching, maybe putting them on just one project (Hello.lib, for
instance) would be enough?

(I use the MSVC++ IDE on rare occassions for debugging, and never for
building nor text edition, so I'm not aware of the needs and
expectations you have)

-- 
Oscar

On Sat, Oct 25, 2008 at 9:09 PM, Óscar Fuentes <ofv at wanadoo.es> wrote:
> I've checked that Intellisense can jump to an unlisted header file when
> you ask for a declaration on a cpp file. So, what's the benefit of
> having the header files explicitly listed in the solution? If it is for
> text searching, maybe putting them on just one project (Hello.lib, for
> instance) would be enough?
Yes, for me personally, it'd be mostly for grepping to find things.
Also, project plugins that let you open files (WorkspaceWhiz, etc.)
generally work from the list of files included in the solution, so it
becomes "hard" to open any of the include files by name otherwise.

Perhaps something like putting them in an 'includes' or
'headers'
project might make sense?

scott