Hello Alexander,
Am Montag, 19. April 2010 um 18:03:28 schrieb Alexander Neundorf:
> On Monday 19 April 2010, Benjamin Eikel wrote:
> > Hello Alexander,
> >
> > Am Sonntag, 18. April 2010 10:52:17 schrieb Alexander Neundorf:
> > > Hi Benjamin,
> > >
> > > On Friday 16 April 2010, Benjamin Eikel wr
On Monday 19 April 2010, Benjamin Eikel wrote:
> Hello Alexander,
>
> Am Sonntag, 18. April 2010 10:52:17 schrieb Alexander Neundorf:
> > Hi Benjamin,
> >
> > On Friday 16 April 2010, Benjamin Eikel wrote:
> > > Hello,
> > >
> > > maybe my first post was not clear enough.
> > > I created a minimal
Hello Alexander,
Am Sonntag, 18. April 2010 10:52:17 schrieb Alexander Neundorf:
> Hi Benjamin,
>
> On Friday 16 April 2010, Benjamin Eikel wrote:
> > Hello,
> >
> > maybe my first post was not clear enough.
> > I created a minimal example to demonstrate what I mean (see attached
> > files). That
Hi Benjamin,
On Friday 16 April 2010, Benjamin Eikel wrote:
> Hello,
>
> maybe my first post was not clear enough.
> I created a minimal example to demonstrate what I mean (see attached
> files). That example contains a library called MyLib and a binary called
> MyBin. The enclosed shell script ca
Hello,
maybe my first post was not clear enough.
I created a minimal example to demonstrate what I mean (see attached files).
That example contains a library called MyLib and a binary called MyBin. The
enclosed shell script can be used to build the binary on Linux. At first the
library will be c
Hello,
we are using CMake to build different binaries which depend on some libraries,
that we develop ourselves. At the moment we export the settings from the build
directories of the libraries using export(... lib-build.cmake ...). The
CMakeLists.txt of a binary uses an own CMake module using
I have a project configured by CMake that uses a macro to create an
executable from a generated source file using code like the following:
macro(CreateProgram Name)
set(SourceFile ${Name}.cpp)
add_custom_command(OUTPUT ${SourceFile}
COMMAND
DEPENDS ${ARGN}
WORKING_DI
Hi all.
I have a larger project, consist of some libraries.
I've "ported" it to CMake and it've been build well at all my platforms(vs
2005,vs 2008,mingw), but VS 2003.
In VS .Net 2003 cmake creates additional projects for each library, called
XXX_UTILITY, and adds project dependencies through thos
