Activity
From 05/30/2013 to 06/28/2013
06/10/2013
- 03:59 PM Bug #1533 (Resolved): Errorneous library name on MacOS
- Updating rci solved the issue. It had an outdated imported library reference to just @rsc@.
06/07/2013
- 01:23 PM Bug #1533 (Feedback): Errorneous library name on MacOS
- Sebastian Wrede wrote:
> Which looks fine to me. However, the library name looks broken in several regards:
> First...
06/06/2013
- 09:24 PM Bug #1533 (Resolved): Errorneous library name on MacOS
- This error popped up after updating (today) to the newest HEAD version of RSC. The sympton is as follows:...
- 03:43 AM Tasks #1529 (Resolved): Implement optional wrapping of plugin loading and unloading exception
- Applied in commit:3c1c876c.
06/05/2013
06/03/2013
- 04:40 AM Enhancement #1524 (Resolved): Remove singleton implementation of plugin mechanism
- Applied in changeset rsc|commit:c48603c5fb597505424d39df7ff30f48847433a9.
- 04:40 AM Enhancement #1525 (Resolved): Document thread-safety for plugin mechanism
- Applied in changeset rsc|commit:b357ccb27f9ffd485bcc68aea82b4305678c892e.
05/31/2013
- 01:50 AM Tasks #1420 (Resolved): Simplify plugin initialization with windows export symbols
- Applied in changeset rsc|commit:8000389eb73d78d1a800034e039ef9a4cadea7c4.
- 01:52 PM Tasks #1420 (In Progress): Simplify plugin initialization with windows export symbols
- 02:09 PM Tasks #1529 (Resolved): Implement optional wrapping of plugin loading and unloading exception
- Specified by a flag in @load@ and @unload@, either wrap or do not wrap exception occurring in the plugin implementati...
- 01:57 PM Bug #1522 (Resolved): FindBoostUUID reset Boost_LIBRARIES varialbe when used with last CMake version
- Applied in changeset rsc|commit:ebfafed3cc969b90b43bc35688af1b2d08e1cb5c.
- 01:53 PM Bug #1522 (In Progress): FindBoostUUID reset Boost_LIBRARIES varialbe when used with last CMake v...
- 01:52 PM Bug #1528 (Rejected): Boost.uuid from boost distribution is not found with MSVC11 and boost 1.53
- No idea what I did wrong, but the user option for this was enabled.
- 11:02 AM Bug #1528 (Rejected): Boost.uuid from boost distribution is not found with MSVC11 and boost 1.53
- Instead, RSC uses the internal version of boost.uuid, which should not happen.
- 01:48 PM Enhancement #1526 (Resolved): Prevent duplicate loading of plugins
- Applied in changeset rsc|commit:3f067fe5a7793e84f6a5f7d7b8f26a62810ad477.
- 01:39 PM Enhancement #1523 (Resolved): Let Plugin mechanism throw an exception on duplicate plugin names
- Applied in changeset rsc|commit:00f2975e1c42ce2019e5a48ed4bdc3b4d5d09d96.
- 01:39 PM Tasks #1178 (Resolved): Add unit tests for plugin system
- Applied in changeset rsc|commit:412a06ece93675df27c32b0b5061fef73acee3f3.
05/30/2013
- 07:31 PM Bug #1527 (Resolved): Google mock cannot be built with MSVC11
- Applied in changeset rsc|commit:d14464e0250f444c90950dd91d50914a0c6ba641.
- 07:26 PM Bug #1527 (Resolved): Google mock cannot be built with MSVC11
- Some error about std::tuple. Fix this with compiler flags in the cmake macro: https://groups.google.com/forum/?fromgr...
- 07:10 PM Enhancement #1526 (Resolved): Prevent duplicate loading of plugins
- 07:09 PM Enhancement #1525 (Resolved): Document thread-safety for plugin mechanism
- 07:09 PM Enhancement #1524 (Resolved): Remove singleton implementation of plugin mechanism
- Avoid problems of global state.
- 07:08 PM Enhancement #1523 (Resolved): Let Plugin mechanism throw an exception on duplicate plugin names
- 10:53 AM Bug #1522: FindBoostUUID reset Boost_LIBRARIES varialbe when used with last CMake version
- They change the behaviour with this commit: http://cmake.org/gitweb?p=cmake.git;a=commit;h=0100f88e298c6766d601085370...
- 10:43 AM Bug #1522: FindBoostUUID reset Boost_LIBRARIES varialbe when used with last CMake version
- We coud even consider reporting this upstream. I don't know if this is really the intended behavior for the FindBoost...
- 10:41 AM Bug #1522: FindBoostUUID reset Boost_LIBRARIES varialbe when used with last CMake version
- I have no idea how to solve this correctly. FindBoostUUID can never know what a previous caller might have indicated ...
Also available in: Atom