Activity
From 11/23/2013 to 12/22/2013
12/19/2013
- 11:54 AM Bug #1693 (Resolved): ProvideGoogleMock macro doesn't allow changing gmock source from inside cmake
- No idea how this happend
- 11:53 AM Bug #1693: ProvideGoogleMock macro doesn't allow changing gmock source from inside cmake
- No?
- 11:52 AM Bug #1693: ProvideGoogleMock macro doesn't allow changing gmock source from inside cmake
- You just re-opened it.
- 11:38 AM Bug #1693: ProvideGoogleMock macro doesn't allow changing gmock source from inside cmake
- May I close this?
- 10:20 AM Bug #1693: ProvideGoogleMock macro doesn't allow changing gmock source from inside cmake
- Without caching the user would not have a persistent possibility to override the default location from the command line.
- 10:19 AM Bug #1693 (New): ProvideGoogleMock macro doesn't allow changing gmock source from inside cmake
- I can't change cmake :/ The problem is that the cache is mainly intended to change variable from a user perspective, ...
- 10:17 AM Bug #1693 (Resolved): ProvideGoogleMock macro doesn't allow changing gmock source from inside cmake
- @set(GMOCK_SOURCE "http://googlemock.googlecode.com/files/gmock-1.6.0.zip" CACHE STRING "cmake cache sucks" FORCE)@ w...
- 10:12 AM Bug #1693: ProvideGoogleMock macro doesn't allow changing gmock source from inside cmake
- I need to provide a description for the @GMOCK_SOURCE@ variable in my downstream project just to overwrite the variab...
- 10:11 AM Bug #1693: ProvideGoogleMock macro doesn't allow changing gmock source from inside cmake
- Oh and if you previously defined it with the command line in the same configuration you might even need the force ;)
- 10:10 AM Bug #1693: ProvideGoogleMock macro doesn't allow changing gmock source from inside cmake
- It does, but as this is a cache variable, you probably need to define it as such to override the default value.
<pre... - 10:08 AM Bug #1693 (Resolved): ProvideGoogleMock macro doesn't allow changing gmock source from inside cmake
- The cmake macro @ProvideGoogleMock@ doesn't allow setting an alternative gmock source path from within the calling cm...
- 10:17 AM Revision b21ad2e4 (rsc): Fix whitespace and doc issues
12/16/2013
- 03:31 PM Revision 4a93eeef (rsc): Whitespace fixes
- 03:30 PM Revision 2ea4161a (rsc): Version bump to 0.11
- 03:22 PM Bug #1640: Loading same plugin twice from different pathes
- As we did not get any feedback before the new release date we move this issue over to the new version.
12/12/2013
- 05:01 PM Bug #1640 (Feedback): Loading same plugin twice from different pathes
- Daniel, I remember, that this issue came up in a setup of yours, where you had the toolkit plugin path configured and...
12/10/2013
- 02:45 PM Bug #1675 (Resolved): Type name tests fail on OSX mavericks
- Applied in changeset rsc|commit:95f1eaf64063de0be55aa22ab4c13751ab20fba8.
- 02:44 PM Revision 95f1eaf6 (rsc): fixes #1675: compiler-independent type name tests
- Merge branch 'bug-1675'
12/09/2013
- 04:33 PM Tasks #1451: Clarify configuration, when different rsx version installed
- We have nothing but API documentation and Wiki so far. ;) So it would probably be in the wiki then?
- 10:23 AM Tasks #1451: Clarify configuration, when different rsx version installed
- For example in the documentation, yes. AFAIR there is no 'dev' section somewhere. But a section like this could clari...
- 09:03 AM Tasks #1451: Clarify configuration, when different rsx version installed
- ping
- 04:32 PM Bug #1640: Loading same plugin twice from different pathes
- But then the description is actually wrong. ;) That commit addressed the issue that the configuration requested to lo...
- 10:19 AM Bug #1640: Loading same plugin twice from different pathes
- It seems, that you already adressed this issue in commit:a3932651bd, but did not close it. ;)
- 09:24 AM Bug #1640: Loading same plugin twice from different pathes
- I just looked at the code and there is a unit tests that actually tests that one path overrides another one: PluginTe...
12/04/2013
- 09:37 PM Bug #1674 (Resolved): Google mock 1.6 does not compile on OSX mavericks
- Applied in changeset rsc|commit:fd9e9958798c9850399fc239070486c60a28a6bd.
- 10:19 AM Bug #1674 (Resolved): Google mock 1.6 does not compile on OSX mavericks
- An update to 1.7. as the default version should fix this:
https://trac.macports.org/ticket/40910 - 06:46 PM Revision 94f70933 (rsc): Make TypeStringToolsTest independent of compiler
- Use generic patterns to find fragments of the string type name that
should be consistent across all compilers. - 06:39 PM Revision 82956ce2 (rsc): Make DemangleTest independent of compiler
- Avoid hard-coded compiler detail (the typename) and only expect certain
fragments to appear. - 01:27 PM Revision df8957e0 (rsc): Only use gmock 1.7 on mavericks clang version
- This prevents compilation errors with gcc 4.6 in cxx11 mode.
- 10:37 AM Bug #1675 (Resolved): Type name tests fail on OSX mavericks
- ...
- 10:32 AM Revision a1f1adb2 (rsc): refs #1674: upgrade gmock to 1.7.0
- 1.6.0 does not compile on OSX Mavericks, so we have to do the version
bump. - 10:27 AM Revision fd9e9958 (rsc): fixes #1674: upgrade gmock to 1.7.0
- 1.6.0 does not compile on OSX Mavericks, so we have to do the version
bump.
11/26/2013
- 01:19 PM Enhancement #1498: Encode version in library name
- The ENCODE_VERSION option is not available in rsb-cpp, rst-cpp and rst-proto.
- 12:33 PM Enhancement #1498: Encode version in library name
- This should actually be the case for rsb and rst. Where do you see conflicts?
- 11:28 AM Enhancement #1498: Encode version in library name
- The changes to disable the version need to be applied to the other projects (rsb, rst) as well.
Also available in: Atom