search for: workspacewhiz

...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

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.

Ó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.