Perfect. Thanks Leif!
On Tue, Apr 16, 2013 at 11:23 AM, Leif Walsh wrote:
> cmake --build /path/to/build/dir [--target ]
>
> I usually go to the build directory and type `cmake --build .` You can
> pass extra options to the underlying build system by adding `--`
> afterwards, so if you are usi
cmake --build /path/to/build/dir [--target ]
I usually go to the build directory and type `cmake --build .` You can
pass extra options to the underlying build system by adding `--`
afterwards, so if you are using, for example, the Makefile generator, you
can build in parallel with `cmake --build
Hi,
Now that I have a project up and running with CMake generated native
project files, can I trigger a build with CMake as well? That is, a
cross-platform way to trigger a build on the project without the need for
me to call 'msbuild' on windows for example?
- Saad
--
Powered by www.kitware.com
On Tue, Apr 16, 2013 at 3:16 PM, Andreas Haferburg wrote:
> > I can't guarantee where the boost libraries are installed, that's why I
> use FindBoost.
> Just make the CMake error message clear, e.g. "Boost 1.50 expected to be
> found in ". Most people know how to rename a directory.
That's what
I guess you could file a bug/request to de-duplicate in the FindCUDA
cmake code.
Anybody who reads the property via get_property (or get_target_property
or get_directory_property) and then sets it back with some appended
info is directly manipulating the property itself. Moreover,
include_dir
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.
On Tue, Apr 16, 2013 at 12:32 PM, Slava
wrote:
>
> You build 64-bit stuff (including boost if you wish) in 64-bit
> environment, 32-bit stuff (including boost if you wish) in a separate
> 32-bit environment. The environment is native for build tools, so you need
> no crosscompiling (-m32), no spec
On Tue, Apr 16, 2013 at 9:15 AM, Slava wrote:
>
> In my experience finding/adapting packages for crosscompiling 64->32 is
> much more troublesome than setting up 32-bit chroot and using it for 32-bit
> builds.
Sorry but I don't understand, certainly because I'm still a noob at linux
stuffs.
I do
Hi David,
Appears you are right. However nvcc is clearly not playing by the new
rules. When using cuda_add_executable() I do get multiple -I entries on
the command line. Should I file a bug report for FindCUDA then?
Regards,
Marcel.
On 16/04/13 01:03, David Cole wrote:
It removes duplicates
On Mon, 15 Apr 2013 16:59:25 +0200, Klaim - Joël Lamotte
wrote:
For now I think the simplest solution would be to make b2 use a default
64bit lib directory
when the directory is unspecify. Then FindBoost cmake module can rely on
this knowledge to try to find the right binaries,
based on BOOS
10 matches
Mail list logo
