Hi,
add this :
link_directories(${Boost_LIBRARY_DIRS})
after the include_directories command.
Cheers,
Mourad
*
*
On Mon, Apr 30, 2012 at 10:26 PM, Hui Wang wrote:
> Yes, I tried with find_package( Boost COMPONENTS thread ) and
> target_link_libraries( ShowEngine ${Boost_LIBRARIES}), and tha
Yes, I tried with find_package( Boost COMPONENTS thread ) and
target_link_libraries( ShowEngine ${Boost_LIBRARIES}), and that works.
Thank you so much!
On Mon, Apr 30, 2012 at 3:27 PM, Alain Leblanc wrote:
> Don't have much experience with boost in combination with cmake, but don't
> you still n
Hello,
I'm using CMake generated Visual Studio solution, and I added boost with
find_package(Boost),
before that I used commands: set(Boost_USE_STATIC_LIBS
ON) set(Boost_USE_MULTITHREADED ON) set(Boost_USE_STATIC_RUNTIME OFF)
after that I used
commands: include_directories(${Boost_INCLUDE_DIR}) ad
2012/4/30 Giovanni Azua :
> Hello,
Hi,
Please be careful not to drop the CMake ML address.
> Now I am completely set on Mac OS X. I can Compile/Run/Debug successfully.
> Basically I had to fix the environment settings of the Run Configuration to
> include in-place the DYLD_LIBRARY_PATH (linking
Hi,
I used the following code to add protobuf project to my "solution":
$-- script --$
if( MSVC )
include_external_msproject( libprotobuf
${CMAKE_CURRENT_SOURCE_DIR}/protobuf/vsprojects/libprotobuf.vcproj )
else()
message( "No project file set for protobuf for thi
Hi Luke.
Quotes are generally a pain. I haven't tested it, but I would try
putting the option specification in quotes (for cmake), like this:
set (CMAKE_CXX_FLAGS_RELEASE ${CMAKE_CXX_FLAGS_RELEASE}
"/MyCustomTool:\"$(SolutionDir)\"")
Petr
On Mon, Apr 30, 2012 at 11:36 AM, Luke Snape wrote:
> H
Hello,
I am adding some custom compiler options to a VS2008 project containing paths
with spaces. As such, I require double quotes around the argument name to
ensure the spaces in the path are not interpreted as individual compiler flags.
e.g:
set (CMAKE_CXX_FLAGS_RELEASE ${CMAKE_CXX_FLAGS_REL
On Mon, Apr 30, 2012 at 13:56, Michael Wild wrote:
> You are looking for the MSVC [1] variable and the
> include_external_msproject [2] command
>
>
Thank you very much, I can't believe I missed this one!
Joël Lamotte
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
ht
Hi
We have been using a configuration system named CMT which exactly cope
with this issue
It used to be directly based on pure Make files for the build aspect.
Nowadays, we are converting the build part to using CMake, while
preserving te general configuration properties.
In fact, we do mana
Hi Alexander,
I had to create a very similar setup at work. My solution was to
define a global property for the list of projects to generate. There
is a top level CMakeLists.txt file which doesn't define any targets,
but just includes all subdirectories as necessary. In pseudo-code, my
solution is
10 matches
Mail list logo
