[CMake] Source file symlinks on out-of-source builds

Hi people, I was thinking if it would be nice if cmake created symlinks on supported platforms of source files into CMAKE_CURRENT_BINARY_DIR when it differs from CMAKE_CURRENT_SOURCE_DIR. My only complaint against out-of-source builds is that the sources aren't around when I do make. This feature

[CMake] Documentation for CMAKE_CXX_IMPLICIT_LINK_LIBRARIES and CMAKE_Fortran_IMPLICIT_LINK_LIBRARIES

Hi all, I am new to this list and hope its the right point of contact for feature/enhancement proposals, if not, please give me the right pointer. I experienced that CMake 2.8 automatically figures out how to link a C/Fortran executable when linking to a static C++ library, great. However I

Re: [CMake] Documentation for CMAKE_CXX_IMPLICIT_LINK_LIBRARIES and CMAKE_Fortran_IMPLICIT_LINK_LIBRARIES

Zitat von Tobias Hilbrich tobias.hilbr...@zih.tu-dresden.de: [...] After hours of googling I finally found the right variables to read this information CMAKE_CXX_IMPLICIT_LINK_LIBRARIES and CMAKE_CXX_IMPLICIT_LINK_LIBRARIES. None of these variables are documented anywere, the only pointer to

Re: [CMake] continuous integration with CMake

Tyler Roscoe wrote: I am using CMake to build several medium-sized C++ projects on several Linux and Windows platforms (with an eye to supporting Mac and several Unices eventually). The next step is to get a Continuous Integration envrionment up and running. From my readings around the web and

[CMake] CMake, iPhone XCode

Hello, I am trying to build a project for iPhone using XCode. The basic stuff works if I use the makefile generator I get my test.app. Switching wo XCode with -GXcode creates the problem:

[CMake] CMake, iPhone XCode

Hello, I am trying to build a project for iPhone using XCode. The basic stuff works if I use the makefile generator I get my test.app. Switching wo XCode with -GXcode creates the problem:

Re: [CMake] Why doesn't cmake generate the file?

Hi, [Tyler] Have you tried this with a custom command that actually creates gen.h? [Michael] ...use full paths to gen.h ... [Michael] ...don't need to set the source file property GENERATED ... Thank you for your hints, I've added them to the example code below and tested it. (also had to

Re: [CMake] Why doesn't cmake generate the file?

Jörg Förstner wrote: Hi, --- So the big question is: --- Why do I need to manually add gen.h to the ADD_LIBRARY() command? To let CMake know it is a generated file. When the depend scanner runs the file will not be there. It is just how it works.

Re: [CMake] Source file symlinks on out-of-source builds

Rodolfo Lima wrote: Hi people, I was thinking if it would be nice if cmake created symlinks on supported platforms of source files into CMAKE_CURRENT_BINARY_DIR when it differs from CMAKE_CURRENT_SOURCE_DIR. My only complaint against out-of-source builds is that the sources aren't around when I

Re: [CMake] Source file symlinks on out-of-source builds

I'll throw a no vote on that but what I would like to hear is some more detail from Rodolfo explaining why he thinks he needs this? Have you tried embedding the build directory inside the source directory? Some of us use this type of setup and it seems to work really nicely with IDEs, Text

Re: [CMake] Source file symlinks on out-of-source builds

Michael Jackson wrote: I'll throw a no vote on that but what I would like to hear is some more detail from Rodolfo explaining why he thinks he needs this? Have you tried embedding the build directory inside the source directory? Some of us use this type of setup and it seems to work really

Re: [CMake] Source file symlinks on out-of-source builds

On Thu, Dec 3, 2009 at 1:18 PM, Rodolfo Schulz de Lima rodo...@rodsoft.org wrote: Michael Jackson wrote: I'll throw a no vote on that but what I would like to hear is some more detail from Rodolfo explaining why he thinks he needs this? Have you tried embedding the build directory inside the

Re: [CMake] Why drop -D from wxWidgets_DEFINITIONS ?

* Orion Poplawski (or...@cora.nwra.com) wrote: Note that this is breaking previously working builds of plplot because of the missing -D. I don't see this being done in any other module. This also breaks Rigs of Rods with the same symptoms. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56

Re: [CMake] Source file symlinks on out-of-source builds

On Thu, Dec 03, 2009 at 12:41:59PM -0500, Bill Hoffman wrote: Tools like emacs and other build tools can be taught how to deal with the sources not being right there. The symlinks will likely be a pain to maintain. What happens when a file is removed in the source tree? Who updates the

Re: [CMake] Source file symlinks on out-of-source builds

Rodolfo Schulz de Lima wrote: About emacs/vi, they can locate the source file only if we're going though an error list, as gcc spits out the path to the source files involved. But if you want to load another file, you must do it yourself, which can be irritating sometimes. Sorry to reply to

Re: [CMake] Source file symlinks on out-of-source builds

_ Mike Jackson mike.jack...@bluequartz.net BlueQuartz Softwarewww.bluequartz.net Principal Software Engineer Dayton, Ohio On Dec 3, 2009, at 1:18 PM, Rodolfo Schulz de Lima wrote:

Re: [CMake] Source file symlinks on out-of-source builds

Rodolfo Schulz de Lima wrote: On Thu, Dec 03, 2009 at 12:41:59PM -0500, Bill Hoffman wrote: Tools like emacs and other build tools can be taught how to deal with the sources not being right there. The symlinks will likely be a pain to maintain. What happens when a file is removed in the

Re: [CMake] Source file symlinks on out-of-source builds

On Thu, 03 Dec 2009 16:26:19 -0200, Rodolfo Schulz de Lima rodo...@rodsoft.org wrote: About emacs/vi, they can locate the source file only if we're going though an error list, as gcc spits out the path to the source files involved. But if you want to load another file, you must do it yourself,

Re: [CMake] Source file symlinks on out-of-source builds

Michael Jackson wrote: I guess those of us that use IDEs like Visual Studio, Eclipse, NetBeans, Xcode, CobeBlocks, QtCreator may not see the issue you are trying to solve. That's precisely it, I'm use an old-school setup, Vi + make, and my idea would certainly be helpful in this case.

Re: [CMake] Source file symlinks on out-of-source builds

Bill Hoffman wrote: And, they can still have that, but I once they get used to it, I bet they will like it... Sorry Bill, I think I didn't understand, you mean that they will like to have source code in a different directory than Makefile's? Another option might be a tool on top of CMake.

Re: [CMake] Source file symlinks on out-of-source builds

Jed Brown wrote: See etags/ctags (this is ancient technology). Also semantic (part of cedet for emacs) does semantic analysis so it can jump more intelligently between files (i.e. determine the type of a variable and jump to the appropriate definition). Hi Jed, I know about ctags and the

Re: [CMake] Source file symlinks on out-of-source builds

On 03.12.09 16:31:06, Rodolfo Schulz de Lima wrote: Rodolfo Schulz de Lima wrote: About emacs/vi, they can locate the source file only if we're going though an error list, as gcc spits out the path to the source files involved. But if you want to load another file, you must do it yourself,

Re: [CMake] Source file symlinks on out-of-source builds

On 03.12.09 16:54:08, Rodolfo Schulz de Lima wrote: Bill Hoffman wrote: And, they can still have that, but I once they get used to it, I bet they will like it... Sorry Bill, I think I didn't understand, you mean that they will like to have source code in a different directory than

Re: [CMake] Source file symlinks on out-of-source builds

Andreas Pakulat wrote: See my other mail, there's no way for cmake to find out which symlinks are dead links, except by scanning all source files on a cmake run. Thats a huge waste of time, especially on bigger projects with a few thousand files scattered over a few hundered directories. I

Re: [CMake] Source file symlinks on out-of-source builds

On Thu, 03 Dec 2009 16:59:01 -0200, Rodolfo Schulz de Lima rodo...@rodsoft.org wrote: Hi Jed, I know about ctags and the like, but I'm don't use them (but I should). But these tools cover only a part of the problem. If you want to go to another file and there's no useful context around the

Re: [CMake] Source file symlinks on out-of-source builds

Andreas Pakulat wrote: We're using out-of-source builds (custom buildsystem) at work for about almost a year now. And in fact none of the developers uses an IDE, its emacs or vi. And none of them ever complained about that particular problem, I don't know exactly how they manage that (I'm

Re: [CMake] Source file symlinks on out-of-source builds

Jed Brown wrote: I use command-find-tag M-. and enter (a) part of the file name (not including the path) or (b) part of the function name, with tab completion, or (c) part of the struct name also with tab completion, and it takes me to the definition. No need to enter paths, and this works

Re: [CMake] Source file symlinks on out-of-source builds

On Dec 3, 2009, at 3:11 PM, Rodolfo Schulz de Lima wrote: I'm interested to know how they manage this. But even with if you run make with -C to change to the build directory, the executable would be generated there. This feels awkward when you are used to in-source builds. Inside vi I usually

Re: [CMake] Source file symlinks on out-of-source builds

2009/12/3 Jed Brown j...@59a2.org: On Thu, 03 Dec 2009 16:26:19 -0200, Rodolfo Schulz de Lima rodo...@rodsoft.org wrote: About emacs/vi, they can locate the source file only if we're going though an error list, as gcc spits out the path to the source files involved. But if you want to load

Re: [CMake] Source file symlinks on out-of-source builds

2009/12/3 Rodolfo Schulz de Lima rodo...@rodsoft.org: Michael Jackson wrote: I guess those of us that use IDEs like Visual Studio, Eclipse, NetBeans, Xcode, CobeBlocks, QtCreator may not see the issue you are trying to solve. That's precisely it, I'm use an old-school setup, Vi + make, and

Re: [CMake] Source file symlinks on out-of-source builds

Michael Jackson wrote: cmake -C ${workspace_loc}/${project_name}/Build -j 16 VERBOSE=1 And the executables (as setup in the Cmake files) are always built into Build/Bin. This way you can only have one build tree per project. One way to extend it is to use something like Build_${build_type}

Re: [CMake] Source file symlinks on out-of-source builds

Eric Noulard wrote: Cscope is another light and fast (compared to IDE) alternative Thanks Eric, I'm gonna check this one out. I've heard of it but never tried. []s, rod ___ Powered by www.kitware.com Visit other Kitware open-source projects at

Re: [CMake] Source file symlinks on out-of-source builds

True, but I can always change the build to something else if needed (like a release). 98% of the time using Build works just fine. I think there have been lots of great discussions and suggestions in this thread that you should be able to find something that works for you. I envy the

Re: [CMake] Source file symlinks on out-of-source builds

Eric Noulard wrote: I'm using both vi+make and Eclipse CDT (for C/C++ project using CMake). In fact I was a pure command line guy until the noise of mouse click surround me and I decided to give a try to IDE way to see the code :-) I went into the opposite direction, from mouse to keyboard,

[CMake] set directory for object file generation

Is there a way to set the directory that cmake (2.8) uses for object file generation? I haven't found an online resource for this. There is a difference when we build the same project on a Windows vs. Linux platform. On WIN32, cmake creates 'PROJ_NAME/PROJ_NAME.dir/ directory for object

Re: [CMake] Source file symlinks on out-of-source builds

That's one way do deal with it, but since I use xterm I don't have tabs, and my monitor is a 17 4:3, so screen space it rare. Dude... I need some serious tools and hardware upgrades :) install screen http://www.gnu.org/software/screen/ John ___

Re: [CMake] set directory for object file generation

On Thu, Dec 03, 2009 at 03:08:02PM -0600, Voisard, Shane S CIV NSWCDD, K54 wrote: Is there a way to set the directory that cmake (2.8) uses for object file generation? I haven't found an online resource for this. I don't know of a way. The problem is that the resulting directory on the

Re: [CMake] Source file symlinks on out-of-source builds

2009/12/3 Rodolfo Schulz de Lima rodo...@rodsoft.org: Eric Noulard wrote: I'm using both vi+make and Eclipse CDT (for C/C++ project using CMake). In fact I was a pure command line guy until the noise of mouse click surround me and I decided to give a try to IDE way to see the code :-) I went

Re: [CMake] Source file symlinks on out-of-source builds

Michael Jackson wrote: True, but I can always change the build to something else if needed (like a release). 98% of the time using Build works just fine. I think there have been lots of great discussions and suggestions in this thread that you should be able to find something that works for

[CMake] installing pdb files

I fought with trying to get pdb files copied to a specific location during the install step of my build. I finally have something working and this is what I've come up with: install(FILES ${CMAKE_CURRENT_BINARY_DIR}/\${CMAKE_INSTALL_CONFIG_NAME}/project_name.pdb DESTINATION ${SYMBOLS_DIR}) where

Re: [CMake] Source file symlinks on out-of-source builds

On 03.12.09 20:23:36, Rodolfo Lima wrote: John Drescher escreveu: install screen Thanks for the tip but that's not my point in this whole thread (i.e. I'm not looking for solutions, I'm giving one). CMake does so much complicate things to make working with software projects a seamless

[CMake] installing pdb files

(Very sorry for screwing up my first message. Take 2) I fought with trying to get pdb files copied to a specific location during the install step of my build. I finally have something working and this is what I've come up with: install(FILES

Re: [CMake] Source file symlinks on out-of-source builds

On 03.12.09 18:03:56, Rodolfo Schulz de Lima wrote: Andreas Pakulat wrote: See my other mail, there's no way for cmake to find out which symlinks are dead links, except by scanning all source files on a cmake run. Thats a huge waste of time, especially on bigger projects with a few

Re: [CMake] Source file symlinks on out-of-source builds

On Thu, Dec 3, 2009 at 5:55 PM, Bill Hoffman bill.hoff...@kitware.comwrote: Rodolfo Lima wrote: John Drescher escreveu: install screen Thanks for the tip but that's not my point in this whole thread (i.e. I'm not looking for solutions, I'm giving one). CMake does so much complicate

Re: [CMake] Source file symlinks on out-of-source builds

Andreas Pakulat escreveu: That doesn't work good enough. CMake doesn't prohibit referencing files from all over the project tree, so if I update foo/CMakeLists.txt, that might need symlink changes over at bar/... So a complete tree-update is needed unless CMake wants to keep track of the last