From: Peter V. <Pet...@es...> - 2002-09-04 11:41:19
|
Where should I specify that when using certain libraries (e.g. libMesaGL.so), the executable must also always link with -lpthread ? Peter. |
From: Ferenz K. <fe...@cs...> - 2002-11-27 14:23:19
|
Hi, I'm trying to create a library within vxl (at the same level in the directory tree as eg. `gel' or `mul'). As I'm new to CMake and as sourcefiles yet getting frequently in and out I quite often change the relevant CMakeLists.txt-s. Then I change to the build dir run `ccmake sourcedir' (where sourcedir is the whole vxl-src dir, not just my library dir) and then configure the build. My problem is that both steps (the initial `ccmake sourcedir' and the configuration after) take quite some time (tenseconds), which is very unfortunate in the modify-build-try cycle. So my question is, how could I do it faster? TIA, Fecu |
From: Geoffrey C. <ge...@cr...> - 2002-11-27 14:36:12
|
If you are editing some file in $VXLROOT/mystuff/, you should be able to just go into $VXLBUILDROOT/mystuff and type 'make', where $VXLBUILDROOT is the root of your vxl build. The Makefile generated by cmake in $VXLBUILDROOT should contain a dependency which will trigger the necessary rerun of cmake if you change the CMakeLists.txt. It might take a few seconds, but in practice you shouldn't be changing your CMakeLists very often once you start really coding and testing. Does that make any sense? Geoff. > -----Original Message----- > From: vxl...@li... [mailto:vxl-users- > ad...@li...] On Behalf Of Ferenz Kahlesz > Sent: Wednesday, November 27, 2002 3:12 PM > To: VxL User List > Subject: [Vxl-users] CMake question > > Hi, > > I'm trying to create a library within vxl (at the same level in the > directory tree as eg. `gel' or `mul'). As I'm new to CMake and as > sourcefiles yet getting frequently in and out I quite often change the > relevant CMakeLists.txt-s. Then I change to the build dir run `ccmake > sourcedir' (where sourcedir is the whole vxl-src dir, not just my library > dir) and then configure the build. > > My problem is that both steps (the initial `ccmake sourcedir' and the > configuration after) take quite some time (tenseconds), which is very > unfortunate in the modify-build-try cycle. > > So my question is, how could I do it faster? > > TIA, > Fecu > > > ------------------------------------------------------- > This SF.net email is sponsored by: Get the new Palm Tungsten T > handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en > _______________________________________________ > Vxl-users mailing list > Vxl...@li... > https://lists.sourceforge.net/lists/listinfo/vxl-users |
From: Amitha P. <pe...@cs...> - 2002-11-27 16:11:45
|
To add to Geoff's response: under Unix, you generally need to re-run ccmake only if you add a directory. Otherwise, running "make" will automatically re-generate the makefile in that directory if necessary. Amitha. "Geoffrey Cross" <ge...@cr...> writes: > If you are editing some file in $VXLROOT/mystuff/, you should be able to > just go into $VXLBUILDROOT/mystuff and type 'make', where $VXLBUILDROOT > is the root of your vxl build. The Makefile generated by cmake in > $VXLBUILDROOT should contain a dependency which will trigger the > necessary rerun of cmake if you change the CMakeLists.txt. > > It might take a few seconds, but in practice you shouldn't be changing > your CMakeLists very often once you start really coding and testing. > > Does that make any sense? > > Geoff. > > > > -----Original Message----- > > From: vxl...@li... [mailto:vxl-users- > > ad...@li...] On Behalf Of Ferenz Kahlesz > > Sent: Wednesday, November 27, 2002 3:12 PM > > To: VxL User List > > Subject: [Vxl-users] CMake question > > > > Hi, > > > > I'm trying to create a library within vxl (at the same level in the > > directory tree as eg. `gel' or `mul'). As I'm new to CMake and as > > sourcefiles yet getting frequently in and out I quite often change the > > relevant CMakeLists.txt-s. Then I change to the build dir run `ccmake > > sourcedir' (where sourcedir is the whole vxl-src dir, not just my > library > > dir) and then configure the build. > > > > My problem is that both steps (the initial `ccmake sourcedir' and the > > configuration after) take quite some time (tenseconds), which is very > > unfortunate in the modify-build-try cycle. > > > > So my question is, how could I do it faster? > > > > TIA, > > Fecu |
From: Ian S. <ian...@st...> - 2002-09-04 12:11:10
|
This should go in to the FindOpenGL.cmake file For example, the patch below. You might need to tighten the conditions under which the pthreads is added. C:\workspace\Lvxl\config.cmake\Modules\NewCMake>cvs diff cvs server: Diffing . Index: FindOpenGL.cmake =================================================================== RCS file: /cvsroot/vxl/vxl/config.cmake/Modules/NewCMake/FindOpenGL.cmake,v retrieving revision 1.2 diff -r1.2 FindOpenGL.cmake 94a95,98 > IF (OPENGL_gl_LIBRARY) > SET (OPENGL_LIBRARIES pthreads) > ENDIF (OPENGL_gl_LIBRARY) > > -----Original Message----- > From: Peter Vanroose [mailto:Pet...@es...] > Sent: Wednesday, September 04, 2002 12:41 PM > To: vxl...@li... > Subject: [Vxl-users] CMake question > > > Where should I specify that when using certain libraries (e.g. > libMesaGL.so), the executable must also always link with -lpthread ? > > > Peter. > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > Vxl-users mailing list > Vxl...@li... > https://lists.sourceforge.net/lists/listinfo/vxl-users > |
From: Amitha P. <pe...@cs...> - 2002-09-04 16:40:45
|
On Wed, Sep 04, 2002 at 01:41:09PM +0200, Peter Vanroose wrote: > Where should I specify that when using certain libraries (e.g. > libMesaGL.so), the executable must also always link with -lpthread ? One -- and perhaps the only -- solution with gcc is to provide a compiler flag: g++ -pthread .... You could do this by editing your CMakeCache.txt Amitha. |