On 11.10.2012 12:16, Klaim - Joël Lamotte wrote: 2. find a way for CMake FindBoost to automatically
find the 64 bit binaries instead of the 32 bit
binaris.
I don't see a clear solution to achieve this, because it depends a lot on how boost have been
compiled.
Use a naming convention, e.g.
Have you tried specifying the version?
FIND_PACKAGE(OpenCV 2.2.0 EXACT REQUIRED)
FIND_PACKAGE(OpenCV 2.4.0 EXACT REQUIRED)
Not sure if the FindOpenCV script can handle the version argument.
Andreas
On 14.02.2013 11:42, Bart Vandewoestyne wrote:
Hello list,
To compile and link my code with
-arch, then use that directory in the find
script.
Andreas
On 14.02.2013 12:09, Bart Vandewoestyne wrote:
On 02/14/2013 11:47 AM, Andreas Haferburg wrote:
Have you tried specifying the version?
FIND_PACKAGE(OpenCV 2.2.0 EXACT REQUIRED)
FIND_PACKAGE(OpenCV 2.4.0 EXACT REQUIRED)
Not sure
probably missing something, but why
add_dependencies(parent child)
? That doesn't make sense. Parent is not using anything from child. You can just leave that line
away and everything will be fine right?
On 2013-08-02, at 16:24:21 , Andreas Haferburg wrote:
Yes, that's pretty much the setup
In our build, we have two executables, parent.exe launches child.exe as a child process. ATM the
build is set up with add_dependencies(parent child). So when using F5 in Visual Studio, child.exe is
built first, then parent.exe, then parent.exe is launched. Is it possible to set this up such that
, at 12:19:56 , Andreas Haferburg wrote:
In our build, we have two executables, parent.exe launches child.exe as a child
process. ATM the build is set up with add_dependencies(parent child). So when
using F5 in Visual Studio, child.exe is built first, then parent.exe, then
parent.exe is launched
as both are done, parent is executed.
I hope it's clearer now.
Regards,
Andreas
On 08.02.2013 12:51, Nick Overdijk wrote:
Well cmake will take care of that if you target_link_library(common), right?
On 2013-08-02, at 12:50:13 , Andreas Haferburg wrote:
Right, sorry. I should have mentioned
On 02/08/2013 03:16 PM, Andreas Haferburg wrote:
Sure. Example:
add_library(common MyFancyString.cpp)
add_executable(parent parent_main.cpp)
target_link_libraries(parent common.lib)
add_executable(child child_main.cpp)
target_link_libraries(child common.lib)
add_dependencies(parent child)
Now I
.
Regards,
Andreas
On 08.02.2013 15:41, Patrick Johnmeyer wrote:
On Fri, Feb 8, 2013 at 8:16 AM, Andreas Haferburg ahaferb...@scopis.com
mailto:ahaferb...@scopis.com wrote:
What happens is that common is built, then child, then parent, then parent
is executed.
What I'd like to happen
The workaround I use is to set the build directory to another drive. I added a batch file to my
Startup folder which contains only this line:
subst b: G:\dev\build
Regards,
Andreas
On 31.01.2013 21:00, Bryn Aspestrand wrote:
Ah, this seems to be an issue with the generated files clashing
DLL Hell becomes an issue when executing a program. The EXE needs to use the DLLs that correspond to
the LIB files it was linked against.
I think you're only concerned with building a library or an executable here. The way CMake is
designed is that you simply call find_package(), and the
CMake doesn't support this out of the box. For most library dependencies, it's not even possible to
retrieve their version, because either the FindXYZ scripts aren't written properly, or because the
library doesn't provide it in the first place. Every library and every Find script does things
On 05.12.2012 14:21, Benoît Thiébault wrote:
$ENV{ProgramFiles} (x86)/Microsoft Visual Studio 10.0/Common7/IDE
$ENV{ProgramFiles} (x86)/Microsoft Visual Studio10.0/Common7/IDE
$ENV{ProgramFiles} (x86)/Microsoft Visual Studio 10/Common7/IDE
$ENV{ProgramFiles} (x86)/Microsoft Visual
I'm trying to use pkg_check_modules in my FindCMinPack script. How can I make
it find the .pc file?
find_package(PkgConfig)
pkg_check_modules(PC_CMINPACK cminpack=${CMinPack_FIND_VERSION})
--
Found PkgConfig: C:/dev/bin/pkg-config.exe (found version 0.26)
checking for module 'cminpack=1.1.3'
/2009/03/27/speeding-up-visual-c-qt-builds/
http://qt-project.org/wiki/jom
/MP only works from the VS IDE.
On 9/20/2012 11:34 AM, Andreas Haferburg wrote:
Hi Yuchen,
we're using the same way to enable /MP, and it works for us. You didn't
say exactly what doesn't work, so I'm left to guessing
Hi Yuchen,
we're using the same way to enable /MP, and it works for us. You didn't say exactly what doesn't
work, so I'm left to guessing.
Have you checked in Visual Studio if the flag is set (Project properties-C/C++-Command Line)?
Maybe there's a conflicting option enabled? Or maybe you're
Here's what we're using (found somewhere on the internet, slightly modified):
# MACRO_ADD_INTERFACES(idl_files...)
#
# Syntax: MACRO_ADD_INTERFACES(output list idl1 [idl2 [...]])
# Notes: idl1 should be absolute
Hello,
I'm currently evaluating Lazy C++ [1], which generates both header and
source files. I'm using add_custom_command() to invoke the generator on
*.lzz file, and for each .lzz file it generates one .hpp file and one
.cpp file. What I'm missing is the ability to compile the file I'm
On 12-Mar-12 9:36 PM, Bill Hoffman wrote:
On 3/12/2012 3:28 PM, Andreas Haferburg wrote:
Hello,
I'm currently evaluating Lazy C++ [1], which generates both header and
source files. I'm using add_custom_command() to invoke the generator on
*.lzz file, and for each .lzz file it generates one
Bill, thank you for your replies.
I'll be writing a macro for Visual Studio then which finds the
corresponding cpp file and compiles it.
Cheers
Andreas
On 12-Mar-12 10:26 PM, Bill Hoffman wrote:
On 3/12/2012 5:00 PM, Andreas Haferburg wrote:
Yea, that's pretty much what I've got so far
Hi,
I'd like to suppress the console, but only in release builds. What's the
official way to do that?
add_executable(... win32 ...) doesn't work, because it switches off the console
in debug builds.
When I set LINKER_FLAGS_RELEASE to /subsystem:windows, I can suppress the console in the
21 matches
Mail list logo