On Tue, Jun 2, 2009 at 8:09 PM, Bill Hoffman wrote:
> Robert Dailey wrote:
>
>> Oops! I spoke too fast :)
>>
>> I found this:
>> http://www.cmake.org/pipermail/cmake/2009-May/029660.html
>>
>>
> But, don't forget about this post:
>
> http://www.cmake.org/pipermail/cmake/2009-May/029782.html
>
> Yo
I'm getting a Cdash dashboard set up; I believe the Cdash stuff is set
up correctly on my web server. Now I'm trying to run a build. I'm
getting an immediate error:
C:\ace\exported\qpid> ctest -S trunk_nightly.cmake --ctest-config
trunk\qpid\cpp\CTestConfig.cmake
Unable to run ctest:
Cannot find f
On Jun 3, 2009, at 3:56 PM, Bill Hoffman wrote:
Michael Jackson wrote:
Sorry, that should be:
link_directories(${CMAKE_LIBRARY_OUTPUT_DIRECTORY})
No, this is not needed. This is all taken care of by CMake for
internal targets.
add_library(foobar ...)
add_executable(car ...)
target_link_
On Wed 03 Jun 22:46 2009 Bill Hoffman wrote:
> e...@cs.bgu.ac.il wrote:
>
> >
> > thanks for the tip though but my current problem is in regards to the
> > linking of external libs, I've used to add them to the
> > TARGET_LINK_LIBRARIES but it was suggested here not to use it in that
> > way.
>
Please don't top-post.
> 2009/6/3 Tyler Roscoe :
> > Sounds like you must have overriden the default destination directory.
> > Did you set EXECUTABLE_OUTPUT_PATH (or the related target property)?
On Wed, Jun 03, 2009 at 08:59:11PM +0200, Steven Van Ingelgem wrote:
> Yes, but only for the base-pr
Michael Jackson wrote:
Sorry, that should be:
link_directories(${CMAKE_LIBRARY_OUTPUT_DIRECTORY})
No, this is not needed. This is all taken care of by CMake for
internal targets.
add_library(foobar ...)
add_executable(car ...)
target_link_libraries(car foobar) # link_directories should n
Sorry, that should be:
link_directories(${CMAKE_LIBRARY_OUTPUT_DIRECTORY})
Also, are you having CMake build all these dependent libraries? If so
then you can use the the invocation of target_link_libraries with just
the names of the targets(AgathaHUD).
IF those dependent libraries are al
e...@cs.bgu.ac.il wrote:
thanks for the tip though but my current problem is in regards to the
linking of external libs, I've used to add them to the
TARGET_LINK_LIBRARIES but it was suggested here not to use it in that
way.
OK, I think I see the problem. For external libraries, you should us
On Wed 03 Jun 22:34 2009 Bill Hoffman wrote:
> e...@cs.bgu.ac.il wrote:
>
> >>
> >> Where are the symbols defined that you are not finding?
> >>
> >> Also, please try make VERBOSE=1 to see the link line being used. Also,
> >> you will want to use nm and grep to find out where the symbols should
On Wed 03 Jun 22:25 2009 Michael Jackson wrote:
>
>
> On Jun 3, 2009, at 2:53 PM, e...@cs.bgu.ac.il wrote:
>
> >
> > TARGET_LINK_LIBRARIES(AgathaHud libAgathaUtils libAgathaEngine
> > libAgathaThreads)
> > the error output is: /usr/lib/gcc/x86_64-pc-linux-gnu/
> > 4.3.3/../../../../x86_64-pc
e...@cs.bgu.ac.il wrote:
Where are the symbols defined that you are not finding?
Also, please try make VERBOSE=1 to see the link line being used. Also,
you will want to use nm and grep to find out where the symbols should be
found.
-Bill
Still lost
You don't need this:
add_depen
On Jun 3, 2009, at 2:53 PM, e...@cs.bgu.ac.il wrote:
TARGET_LINK_LIBRARIES(AgathaHud libAgathaUtils libAgathaEngine
libAgathaThreads)
the error output is: /usr/lib/gcc/x86_64-pc-linux-gnu/
4.3.3/../../../../x86_64-pc-linux-gnu/bin/ld:
cannot find -llibAgathaUtils
like I've said before, t
On Wed 03 Jun 22:14 2009 Bill Hoffman wrote:
> e...@cs.bgu.ac.il wrote:
>
> > I've just noticed the suggestion to remove the lib from the
> > TARGET_LINK_LIBRARIES entry which I did, that solved the previous
> > linking problem but now I get unknown reference to each function or
> > var that I us
e...@cs.bgu.ac.il wrote:
I've just noticed the suggestion to remove the lib from the
TARGET_LINK_LIBRARIES entry which I did, that solved the previous
linking problem but now I get unknown reference to each function or
var that I use from the external libs. how can I add them without
adding them
Yes, but only for the base-project, not for the project where I did an
"add_subdirectory" for...
2009/6/3 Tyler Roscoe :
> On Wed, Jun 03, 2009 at 01:09:09PM +0200, Steven Van Ingelgem wrote:
>> When I "make" it, it says:
>> Linking C executable ../../bin/file
>>
>> But the current binary director
On Wed 03 Jun 21:53 2009 e...@cs.bgu.ac.il wrote:
>
> On Wed 03 Jun 18:37 2009 Michael Wild wrote:
> >
> > On 3. Jun, 2009, at 15:15, e...@cs.bgu.ac.il wrote:
> >
> > >
> > > On Tue 02 Jun 7:33 2009 e...@cs.bgu.ac.il wrote:
> > >>
> > >> On Mon 01 Jun 20:56 2009 Bill Hoffman wrote:
> > >>> e...
On Wed 03 Jun 18:37 2009 Michael Wild wrote:
>
> On 3. Jun, 2009, at 15:15, e...@cs.bgu.ac.il wrote:
>
> >
> > On Tue 02 Jun 7:33 2009 e...@cs.bgu.ac.il wrote:
> >>
> >> On Mon 01 Jun 20:56 2009 Bill Hoffman wrote:
> >>> e...@cs.bgu.ac.il wrote:
> On Mon 01 Jun 15:28 2009 Bill Hoffman wrote
On 3. Jun, 2009, at 15:15, e...@cs.bgu.ac.il wrote:
On Tue 02 Jun 7:33 2009 e...@cs.bgu.ac.il wrote:
On Mon 01 Jun 20:56 2009 Bill Hoffman wrote:
e...@cs.bgu.ac.il wrote:
On Mon 01 Jun 15:28 2009 Bill Hoffman wrote:
e...@cs.bgu.ac.il wrote:
On Mon 01 Jun 8:18 2009 Tyler Roscoe wrote:
tha
On Wed, Jun 03, 2009 at 01:09:09PM +0200, Steven Van Ingelgem wrote:
> When I "make" it, it says:
> Linking C executable ../../bin/file
>
> But the current binary directory is "build/externals/file", why does
> it build in "../../bin"??
>
> How can I know in what directory the executable is being
Thanks Tyler, that works indeed. It seems very obvious now actually. For
people reading this thread in the archive, the following works:
SET( sources s1.cpp s2.cpp s3.cpp )
SET( arguments -c1 2 )
LIST( APPEND arguments ${sources} )
ADD_CUSTOM_COMMAND( TARGET test
On Tue 02 Jun 7:33 2009 e...@cs.bgu.ac.il wrote:
>
> On Mon 01 Jun 20:56 2009 Bill Hoffman wrote:
> > e...@cs.bgu.ac.il wrote:
> > > On Mon 01 Jun 15:28 2009 Bill Hoffman wrote:
> > >> e...@cs.bgu.ac.il wrote:
> > >>> On Mon 01 Jun 8:18 2009 Tyler Roscoe wrote:
> > >>> thanks for the tip, it solv
Hi,
I have the following setup:
CMakeLists.txt [have project()]
externals\CMakeLists.txt [add_subdirectory(file)]
externals\file\CMakeLists.txt [have project()]
The problem I am facing is because in the last txt-file I have:
add_executable(file )
when I ask to show the directories, what I get
22 matches
Mail list logo
