That’s what I was thinking as well, however, what wasn’t clear to me is how to
associate the DLL version with the DLL configuration and the static lib with
the static configuration type? Make it will just work, I’ll have to try it I
suppose.
From: Klaim - Joël Lamotte [mailto:mjkl...@gmail.com]
On Saturday 08 December 2012 20:56:49 Vivek Goel wrote:
> Do I need to change all install rull using this syntax or can I use an
> override rule which can do It for all components ?
I'm not that experienced with cmake...
What about the following:
set(SOURCES
file1
file2
file3
... and so on
)
fo
Do I need to change all install rull using this syntax or can I use an
override rule which can do It for all components ?
regards
Vivek Goel
On Sun, Dec 9, 2012 at 12:59 AM, Martin Koller wrote:
> On Friday 07 December 2012 07:37:38 Vivek Goel wrote:
> > Hi,
> > I am using cmake install targe
On Friday 07 December 2012 07:37:38 Vivek Goel wrote:
> Hi,
> I am using cmake install target to copy files to directory.
> Is there a way I can tell cmake to automatically add destination files in svn
> repo ?
>
> regards
> Vivek Goel
What about an additional install rule, e.g.
install(CODE "e
For example:
add_library( mylibStatic STATIC ${MYLIB_ALL_SOURCES} ) # generate the
static version of the lib
add_library( mylibDLL SHARED ${MYLIB_ALL_SOURCES} ) # generate the dll
loaded at startup version of the same lib, same sources
add_library( mylibExtension MODULE ${MYLIB_ALL_SOURCES} ) # g
