[CMake] Question regarding project structure

David Cole david.cole at kitware.com
Thu Sep 16 11:35:40 EDT 2010


On Thu, Sep 16, 2010 at 11:33 AM, Michael Wild <themiwi at gmail.com> wrote:

>
> On 16. Sep, 2010, at 17:13 , David Aldrich wrote:
>
> > Hi David
> >
> >> Something like this should work:
> >
> >> cmake_minimum_required(VERSION 2.8)
> >> project(MyExe)
> >
> >> add_subdirectory(../Kernel Kernel)
> >> add_subdirectory(../DynLibs DynLibs)
> >
> >> add_executable(MyExe exe.cxx)
> >> target_link_libraries(MyExe Kernel)
> >
> > I have a problem with add_executable(). Our Kernel library includes
> main.cpp, so all our existing linker command does is to take libKernel.a and
> make it an executable:
> >
> > g++ -o _gnuRelease/MyExe -ldl -Wl,-whole-archive,-export-dynamic
> ../Kernel/_gnuRelease/libKernel.a
> >
> > So I have no source files to specify. Does 'exe.cxx' (above) have special
> properties or is it just a placeholder? If the latter, how can I build an
> executable with no source files specified?
> >
> > BR
> >
> > David
>
> There is none. The only way to do that is create an empty dummy file (using
> e.g. a combination of file(WRITE) and configure_file() to prevent
> recompiling after every CMake run).
>
> --
> There is always a well-known solution to every human problem -- neat,
> plausible, and wrong.
> H. L. Mencken
>
>
Or you could just add an empty source file to your source tree...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20100916/2702c8bf/attachment.htm>


More information about the CMake mailing list