2010/6/19 Alexander Boström a...@root.snowtree.se:
lör 2010-06-19 klockan 19:32 +0200 skrev Andrea Musuruane:
I do not know how should I threat those internal libraries. How should
I package them? Because upstream uses static libraries the dynamic
versions cmake creates are not versioned.
On Sat, Jun 19, 2010 at 7:44 PM, Chen Lei supercyp...@gmail.com wrote:
You can open a RFE report against this package in bugzilla for review.
Can you point me to an example?
For internal libs, if those libs are not libs from other project, you
can simply use %cmake
Andrea Musuruane píše v Ne 20. 06. 2010 v 11:25 +0200:
2010/6/19 Alexander Boström a...@root.snowtree.se:
lör 2010-06-19 klockan 19:32 +0200 skrev Andrea Musuruane:
I do not know how should I threat those internal libraries. How should
I package them? Because upstream uses static
Hi all,
a new version of Hatari has recently been released:
http://hatari.berlios.de/
The new version drops the old build system based on autotools and now
it only support cmake. An (optional) python GUI is now bundled with
the emulator. Moreover some static libraries have been introduced
2010/6/20 Andrea Musuruane musur...@gmail.com:
Hi all,
a new version of Hatari has recently been released:
http://hatari.berlios.de/
The new version drops the old build system based on autotools and now
it only support cmake. An (optional) python GUI is now bundled with
the emulator.
lör 2010-06-19 klockan 19:32 +0200 skrev Andrea Musuruane:
I do not know how should I threat those internal libraries. How should
I package them? Because upstream uses static libraries the dynamic
versions cmake creates are not versioned.
