> After the first build of the superbuild, close the superbuild solution as
> it's job is done.
> ...
> Open the solution file for the clsparse library, which was generated as part
> of the superbuild
> and is the 'meat' of the project.
Heh, that's exactly what I meant - superbuilds don't work w
Ok so I’ve got this going now (kind of) but FIND_LIBRARY doesn’t seem to update
when the specified PATH changes. Since we are developing and releasing our own
static libraries on a separate development cycle from the final applications, a
final application may use a different library release th
>And are you able to browse the source code of all your dependencies
>(that were downloaded)?
When you open the generated solution file to the superbuild, targets are made
for all dependencies (in my case: boost, gmock, clsparse). From the superbuild
view, you can not browse the source of the de
On 20 August 2015 at 17:33, Howard Rubin
wrote:
> I have a C++/CLI LIB (and DLL) that I generate with
> include_external_msproject. I need to link to it from my C++ project, which
> I’m trying to do with target_link_libraries. This gives the below error
> message. Since I’m not creating it with a
On 21 August 2015 at 00:43, Klaim - Joël Lamotte wrote:
> On 21 August 2015 at 00:35, Andrey Pokrovskiy
> wrote:
>
>> And are you able to browse the source code of all your dependencies
>> (that were downloaded)?
>>
>
> I forgot to say that indeed if you use ExternalDependencies OR any
> non-sou
On 21 August 2015 at 00:35, Andrey Pokrovskiy wrote:
> And are you able to browse the source code of all your dependencies
> (that were downloaded)?
>
I forgot to say that indeed if you use ExternalDependencies OR any
non-source based way of linking your dependencies to your project,
you don't g
On 20 August 2015 at 22:11, Knox, Kent wrote:
> I can vouch that the superbuild project works fine both for visual studio
> and for xcode. Using visual studio as an example, you generate a visual
> studio solution which downloads and compiles all dependencies, inclulding
> the library. After th
Hm, I don't understand how that possibly could work (maybe there some
explicit support for that in the project generator for MSVS).
And are you able to browse the source code of all your dependencies
(that were downloaded)?
On Thu, Aug 20, 2015 at 1:11 PM, Knox, Kent wrote:
> I can vouch that the
I can vouch that the superbuild project works fine both for visual studio and
for xcode. Using visual studio as an example, you generate a visual studio
solution which downloads and compiles all dependencies, inclulding the library.
After the initial build, you just use the solution file gener
Such approach doesn't work with IDE. For example, when I open main
CMakeLists.txt in Qt Creator I only see two *.cmake files. Superbuilds
use ExternalProject_Add() which kills a lot CMake benefits when used
for CMake project from CMake project.
On Thu, Aug 20, 2015 at 9:28 AM, Knox, Kent wrote:
>
> I'm looking for a template or example project that shows the how to
> setup a cmake-based project in the cleanest and simplest way (i.e.
> using all the latest features of 3.3 release) and with support for the
> following build features:
I waited a few days to see if anybody else would volunteer
I have a C++/CLI LIB (and DLL) that I generate with
include_external_msproject. I need to link to it from my C++ project, which
I'm trying to do with target_link_libraries. This gives the below error
message. Since I'm not creating it with add_library I don't see how to
indicate it's a shared lib.
I have some flags for the PGI compiler that use the ":" character. Needless to
say, things break whenever that character is in the CMAKE_Fortran_FLAGS
variable. Any ideas how to work around this? Thanks,
-Matt
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FA
Hello,
On 17/08/15 01:01, digitalriptide wrote:
When I add SYSTEM to target_include_directories, for example using
target_include_directories( my_target SYSTEM PUBLIC ${MY_LIBRARIES} )
in Clang, CMake prepends -isystem to the relavent -I/my/library/path
type flags. With GCC, however, I see no -i
Please refer to this structure in the description below.
project_root
CMakeLists.txt
build
Debug
Release
src
CMakeLists.txt
COTS <- Third party packages used by various components
COTS_Pa
Hi David,
On 04/05/15 20:12, David Hirvonen wrote:
Thanks for the response. I've moved to a more standard *nix layout for
all platforms, and will rely on a post-build step to create my framework
(for now). If I find a fix, I'll be sure to share it here.
On Wed, Apr 29, 2015 at 5:22 AM, Eric
Hello,
did someone work on this? (http://public.kitware.com/Bug/view.php?id=12592)
Is there an alternative to use extra install commands per component?
Thanks in advance
Best Regards
Roman
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cma
17 matches
Mail list logo
