<br><br><div class="gmail_quote">On Wed, Mar 10, 2010 at 1:47 PM, Alexander Neundorf <span dir="ltr"><<a href="mailto:a.neundorf-work@gmx.net">a.neundorf-work@gmx.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Tuesday 09 March 2010, Markus Raab wrote:<br>
> Hi list!<br>
><br>
> I am currently trying to migrate a autotools project to cmake.<br>
><br>
> The project used modules intensively. It was possible to compile all these<br>
> modules also statically and link them together to a single static library.<br>
> Is this supported out of the box by cmake? How?<br>
<br>
</div>AFAIK no.<br>
In KDE we also had these libtool convenience libraries.<br>
We don't have that anymore, we just compile all the files directly into one<br>
library.<br>
We didn't have any issues with this since then.<br>
<br>
(it may be possible to hack something together with custom commands to extract<br>
the object files from the ar archives and put them together into a resulting<br>
ar file but I wouldn't recommend this)<br>
<br>
Alex<br clear="all"></blockquote></div><br>A bit less work: if you're building all the modules in CMake too, you could loop through them extracting their source lists then adding those to a new target: probably could be generalizable to a custom command in a cmake module.<br>
<br>Ryan<br>-- <br>Ryan Pavlik<br>HCI Graduate Student<br>Virtual Reality Applications Center<br>Iowa State University<br><br><a href="mailto:rpavlik@iastate.edu">rpavlik@iastate.edu</a><br><a href="http://academic.cleardefinition.com">http://academic.cleardefinition.com</a><br>
Internal VRAC/HCI Site: <a href="http://tinyurl.com/rpavlik">http://tinyurl.com/rpavlik</a><br>