2016 at 8:43 AM, Lars wrote:
> > Appreciate some help understanding include_external_msproject.
> > Using Windows 7 and cmake 3.3
> >
> > This is what has been done so far,
> >
> > 1. Opened Visual Studio 2012 and created a new project (Windows Forms
> > A
This is what has been done so far,
>
> 1. Opened Visual Studio 2012 and created a new project (Windows Forms
> Application) and saved it under c:\temp\test.
>
> 2. Used the following to an cmake;
> include_external_msproject(ext_test c:/test/test/test.sln)
>
> This gene
Appreciate some help understanding include_external_msproject.
Using Windows 7 and cmake 3.3
This is what has been done so far,
1. Opened Visual Studio 2012 and created a new project (Windows Forms
Application) and saved it under c:\temp\test.
2. Used the following to an cmake
Hi David,
thank you. I'll take a look at it. But it's not a problem finding/linking to
the external libs. The problem is the dependencies. If I add the dependencies
to every linked binary (in contrast to a lib) it works. What doesn't work is
having a lib being dependent on an external lib and h
CMAKE_BUILD_TYPE is not typically used/useful with the Visual Studio
generators. You may want to look into using the CMAKE_CFG_INTDIR
variable instead.
https://cmake.org/cmake/help/v3.3/variable/CMAKE_CFG_INTDIR.html
On Tue, Oct 27, 2015 at 8:06 AM, Holzinger, Axel (ALC NetworX GmbH)
wrote:
>
Hi list,
I'm on my wits end with include_external_msproject, add_dependencies and build
type.
This is the situation: I have a CMake project with an external static library A
which is included in the build via include_external_msproject, a static library
B and a binary C.
B is depemding on A
C
This is because CMake generates invalid GUIDs in solution (these GUIDs are
for C++ project).
There is a bug report with patch on CMake bug tracker:
http://www.cmake.org/Bug/view.php?id=9742 but it seems C# is not very
interesting for CMake developers (complete C# support requires much more
effort)
I have several C++ projects (library, tests, examples) for Linux and
Windows. This projects are generated by CMake (Makefile for Linux, *.vcproj
for Windows MS Visual Studio). And I have C++/CLI (C++ library wrapper) and
C# projects (tests, examples). This projects are written in MS Visual
Studio a
Tyler Roscoe [mailto:ty...@cryptio.net]:
> On Thu, Jun 04, 2009 at 05:14:20PM -0400, david.k...@l-3com.com wrote:
> > I wonder if the concept of a PROJECT command in a subdirectory
> > of your top-level CMake directory is semantically sound. That is,
> > it might work sometimes but cause trouble
I missed this reply since it wasn't threaded correctly (something wrong
with your mail reader David?). Luckily David said something slightly
different from what I said :).
On Thu, Jun 04, 2009 at 05:14:20PM -0400, david.k...@l-3com.com wrote:
> I wonder if the concept of a PROJECT command in a sub
On Thu, Jun 04, 2009 at 12:47:48PM -0500, Randy Hancock wrote:
> external msproject to the parent. This is desirable, but lets say both
> the test/time project and the test/string project include the common
> lib. This makes common show up *twice* in the parent solution and
> causes a bunch of unwa
Randy Hancock :
> I'm getting duplicate projects included in my top-level solution
> (*.sln file). I have a cmake project() defined at the top level and in
> the test projects for convenience during development. When I use
> include_external_msproject in the subprojects it also adds the
> external
Hello all, It's my first post!
I'm having an issue with include_external_msproject. I have a
directory layout like so:
CMakeLists.txt
/src
/common/CMakeLists.txt
/string/CMakeLists.txt
/time/CMakeLists.txt
/test
/string/CMakeLists.txt
/time/CMakeLists.txt
/build
/src
/
13 matches
Mail list logo
