[CMake] Create library and executable with libraries but no source files

2008-11-14 Thread [EMAIL PROTECTED]
Hi, I would like to create a library (static or shared) and an executable with only libraries (static) but no sources files. It seems add_library and add_executable commands do not accept no source files. In my project, parent directory creates library or executable from libraries created in su

Re: [CMake] Create library and executable with libraries but no source files

2008-11-14 Thread Mathieu Malaterre
To build you executable you need at least a 'main' function. Did you place that file into one of your libs ? On Fri, Nov 14, 2008 at 3:05 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi, > > I would like to create a library (static or shared) and an executable with > only libraries (static)

Re: [CMake] Create library and executable with libraries but no source files

2008-11-14 Thread Andreas Pakulat
On 14.11.08 15:05:17, [EMAIL PROTECTED] wrote: > I would like to create a library (static or shared) and an executable > with only libraries (static) but no sources files. That doesn't make sense. An executable always needs the main() function, which a library doesn't have. A library without sour

Re: [CMake] Create library and executable with libraries but no source files

2008-11-14 Thread [EMAIL PROTECTED]
PROTECTED] > Copie à : cmake@cmake.org > Objet : Re: [CMake] Create library and executable with libraries but no > source files > > > To build you executable you need at least a 'main' function. Did you > place that file into one of your libs ? > > On Fri,

Re: [CMake] Create library and executable with libraries but no source files

2008-11-14 Thread Alexander Neundorf
On Friday 14 November 2008, [EMAIL PROTECTED] wrote: > Hi, > main.c is not necessary for diab compiler (microcontroller) (add_executable > generates an .elf file thanks to my toolchain file). I agree with you for > executable and gcc but what about library ? I don't really understand you here. Any