I think you need a dependency declaration too don't you?
I've seen VStudio 2k3 build out of order without.
# App/CMakeLists.txt
ADD_EXECUTABLE(myexe ...)
TARGET_LINK_LIBRARIES(myexe mylib)
It seems actually a little more complicated in practice
because you probably want mylib's headers
James Mansion wrote:
I think you need a dependency declaration too don't you?
I've seen VStudio 2k3 build out of order without.
# App/CMakeLists.txt
ADD_EXECUTABLE(myexe ...)
TARGET_LINK_LIBRARIES(myexe mylib)
It seems actually a little more complicated in practice
because you
What is the standard way of having cmake access libaries built on the
same subdir level?
I have a project with two subdirs: Util and App. Util builds a
library called 'utillib'. Ap builds a
library and an exe (aplib, and ap.exe).
Main\
CMakeLists.tst
Util\CMakeLists.txt
Peter Kahn wrote:
What is the standard way of having cmake access libaries built on the
same subdir level?
I have a project with two subdirs: Util and App. Util builds a
library called 'utillib'. Ap builds a
library and an exe (aplib, and ap.exe).
Main\
CMakeLists.tst
