Jump to content

RobinP

Members
 View Profile  See their activity

  • Content Count

    10

  • Joined

  • Last visited

Community Reputation

2 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. RobinP

    Rad Studio 12.2

    RobinP replied to Lubo13's topic in General Help

    This is apparently fixed in the latest patch: https://blogs.embarcadero.com/rad-studio-12-2-athens-patch-2-available/
  2. RobinP

    Upgrading to new RAD Studio vs. project Lib names

    RobinP replied to w0wbagger's topic in General Help

    Just been doing the 11.2 to 12.2 upgrade. Yes it's a pain but not too bad, here's what I did: 1. Build one project in the new IDE. Tick yes to remove the old components. 2. To fix any linker errors drop one of the now missing components on the main form. Repeat until it builds. 3. Revert all changes to the main form. You should now just have an updated project file, from which you can tell both the old and new names, so: 4. Use a Python script update all other project files.
  3. RobinP

    Code Coverage tool for C++ based Applications

    RobinP replied to Goutham's topic in General Help

    You could try AQTime from Smartbear (yes it costs money). I haven't really used the coverage profiler but the performance profiler is excellent.
  4. RobinP
    Make sure you right click on the pch file in the project and select "Use for precompiling". This is set by default for a new project but won't be if you have an old project that used to be compiled with the classic compiler. With that set I usually find moving from Classic to Clang that the build takes around 4 to 5 times longer, which can just about be squeezed down to only twice as long using Twine.
  5. RobinP
    @Stefan Glienke I really don't know, I'll have to start trying things out, but this won't be for a month or two yet.
  6. RobinP
    Ok seems to be my mistake, DUnitX is clearly still used for Delphi, but the 10.4 wiki clearly states that it does not work with C++ Builder, and they even suggest using GoogleTest: http://docwiki.embarcadero.com/RADStudio/Sydney/en/DUnitX_Overview So if I want to migrate to the Clang compilers this leaves 3 options: 1. Hope somebody updates DUnit or DUnitX to work with Clang (32 and 64 bit). I could maybe do some testing for this but can't put much time into it. 2. Move to another already existing C++ framework such as GoogleTest. 3. Write my own home brew test framework. At the moment I don't really have any idea which would be easier.
  7. RobinP
    I agree with all you say about DUnit. I had a quick look into fixing it myself but since we are currently a pure C++ shop (don't even have Delphi installed) I thought it was too much of a learning curve and would probably be easier just to move to a more actively maintained framework, hence my interest in GoogleTest. I have a feeling there were more issues with DUnit and Clang but can't remember exactly what.
  8. RobinP
    DUnit works fine using the classic C++ compiler, but with Clang some tests wouldn't build due to a missing overload of CheckEquals. I reported it but they said it was a DUnit issue so nobody is going to fix it. https://quality.embarcadero.com/browse/RSP-27695 Since DUnit seems to have been a dead project for many years it makes sense to move to something else now as part of our Clang migration. I know there are spinoffs but I think DUnitX is now deprecated or will not be supported by Embarcadero, and I'm not sure how far DUnit2 got or if it works with C++ and Clang.
  9. RobinP
    Thx @Roger Cigol, looks like you are in a similar place to us. I'm with you on looking forward to C++17, and not looking forward to migrating 100 DUnit test projects to something else. I really like the GUI runner in DUnit so would prefer something similar (there do seem to be a couple for GoogleTest that look interesting).
  10. RobinP
    Hi Roger, did you get any further with using Google Test in 10.4.2? We're currently looking for a replacement for DUnit so we can migrate to using the Clang compilers, so we'd be interested in any experience you have to share.
×