Michael Jackson said the following on 11/15/2010 11:56 AM:
Ahh. It is a bit clearer the tract you are taking. What I am
suggesting is that you only have to run the scanner once and keep
the results in CMake syntax files so that CMake can just simply re-use
the list. As you add headers during
On 11/14/2010 5:00 AM, Eric Noulard wrote:
There has been some discussion on the list about improvement
of the dependency scanner, this kind of idea may be examined there.
May be it's worth filing a feature request on this subject.
I have not followed this too closely. However, I thought
On Nov 15, 2010, at 12:29 PM, Oliver kfsone Smith wrote:
Michael Jackson said the following on 11/15/2010 9:33 AM:
I have been casually following this thread and I understand the OPs
hesitation when trying to add thousands of files into a CMake build
system but what I think one needs to
2010/11/13 Oliver kfsone Smith osm...@playnet.com:
I mostly work with emacs/vi and - prior to CMake - Makefiles. I'm still
mostly working with emacs/vi, but I also do a fair amount of work with
Visual Studio and CodeBlocks, primarily when I need to test client
interactions with server
Eric Noulard said the following on 11/11/2010 5:53 AM:
Having a lot of source code re-use from source modules that can be shared
between several projects is off course a necessary goal when your source
code base grows and the set of projects using those goes along the same curve.
My experience
Michael Hertling said the following on 11/11/2010 5:23 AM:
Clearly, the downside is the usage of an external dependency scanner.
Yep, but radically better than having to try and manually
duplicate/recreate/maintain the dependency list :)
Thank you for your posts :)
- Oliver
On 11/10/2010 12:30 AM, Oliver kfsone Smith wrote:
Michael Hertling said the following on 11/6/2010 7:39 AM:
stored in the ${CMAKE_BINARY_DIR}/filelist.dat script as an assignment
to the variable FILELIST. Subsequently, this filelist.dat is read via
INCLUDE(), so CMake keeps track of it, i.e.
2010/11/10 Oliver kfsone Smith osm...@playnet.com:
Eric Noulard said the following on 11/6/2010 6:20 AM:
Initially it may be a pain to list them but after a while its generally
better
to manually keep track of file (dis)appearing in your source tree.
(which is usually what you do when using
Eric Noulard said the following on 11/6/2010 6:20 AM:
Initially it may be a pain to list them but after a while its generally better
to manually keep track of file (dis)appearing in your source tree.
(which is usually what you do when using an IDE without CMake)
I.e. if those files are/were
Michael Hertling said the following on 11/6/2010 7:39 AM:
stored in the ${CMAKE_BINARY_DIR}/filelist.dat script as an assignment
to the variable FILELIST. Subsequently, this filelist.dat is read via
INCLUDE(), so CMake keeps track of it, i.e. changing the filelist.dat
results in a rebuild.
On Friday, November 5, 2010, Oliver kfsone Smith osm...@playnet.com
Thanks for the detailed response, Michael :)
So, the question is actually:
Is there a way to have CMake automatically add included headers to visual
studio project files or do you need to use a dependency system to
2010/11/6 Pedro d'Aquino bud...@gmail.com:
On Friday, November 5, 2010, Oliver kfsone Smith osm...@playnet.com
Thanks for the detailed response, Michael :)
So, the question is actually:
Is there a way to have CMake automatically add included headers to visual
studio project files or do
On 11/06/2010 12:20 PM, Eric Noulard wrote:
2010/11/6 Pedro d'Aquino bud...@gmail.com:
On Friday, November 5, 2010, Oliver kfsone Smith osm...@playnet.com
Thanks for the detailed response, Michael :)
So, the question is actually:
Is there a way to have CMake automatically add included
Michael Jackson said the following on 11/4/2010 12:34 PM:
Like, others have stated: You MUST include them in the add_executable
or add_library call. The macro I give above can help keep those files
organized in the Project/Solution file if you want the organization to
mimic the file system for
So, the question is actually:
Is there a way to have CMake automatically add included headers to visual
studio project files or do you need to use a dependency system to generate
the lists by hand?
Take a look at this:
Checked the faq and googled as much as I could but I couldn't find
anything describing how to make visual studio include header files in
the solution/project files?
- Oliver
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
On Thu, Nov 4, 2010 at 11:58 AM, Oliver kfsone Smith osm...@playnet.com wrote:
Checked the faq and googled as much as I could but I couldn't find anything
describing how to make visual studio include header files in the
solution/project files?
Add them to the target just like you do C++
That's funny...
Google for cmake header visual studio and hit #1 explains it pretty well:
http://stackoverflow.com/questions/1167154/listing-header-files-in-visual-studio-c-project-generated-by-cmake
So do hits #2 through 10.
On Thu, Nov 4, 2010 at 11:58 AM, Oliver kfsone Smith
I have a macro to help with this:
MACRO (cmp_IDE_SOURCE_PROPERTIES SOURCE_PATH HEADERS SOURCES
INSTALL_FILES)
if (${INSTALL_FILES} EQUAL 1)
INSTALL (FILES ${HEADERS}
DESTINATION include/${SOURCE_PATH}
COMPONENT Headers
)
endif()
I just add them in the normal calls, then set them as PUBLIC_HEADER
if I am making a library. (Visual Studio seems to automatically
separate source and header files - easy to override if you prefer
something else.)
set(SOURCES
whatever.c
morestuff.c)
set(API
whatever.h)
Hi!
We use CMake to generate Visual Studio projects and it works great.
Everything builds ok, etc.
However, the header files we use are not included in the projects file
list. This doesn't effect the compilation, but from a development
perspective it's quite annoying.
Is there some way of
21 matches
Mail list logo
