Conflict with FMSoft UniGui

[Serhio]

Hi JomiTech!

First of all, I want to thank you for such a wonderful product. It has significantly increased compilation speed! This is great!

But recently I encountered a problem: I can't install the TwineCompiler and FMSoft UniGui components together. It seems that both plugins use units from third-na DDetours library. These are DDetours.pas, CPUID.pas, InstDecode.pas, etc. According to Delphi rules, unit names within a single program must be unique. This creates a conflict: Delphi only correctly loads the plugin that was registered first. In my case, it's TwineCompiler. When loading UniGui, an error window appears:
Can't load package C:\Users\Public\Documents\Embarcadero\Studio\23.0\Bpl\UniGUI29dcl.bpl. Cannot load package 'UniTools29'. It contain unit 'DDetours', which is also contained in package 'TwineCompilePlugin123'.

It would be great if you could create unique names for the DDetours library units. For example, you could add a branded prefix to the unit names. So far, I've only encountered a conflict with one plugin. But this could potentially conflict with other plugins that might inadvertently use units from this library without changes of names.

I use Rad Studio 12.3.

Thanks!

[jomitech]

Thanks for using TwineCompile. Glad to hear that it's helping you so much.

Please download the following file and extract into the TwineCompile Program Files directory to resolve the issues with the conflicted unit names from DDetours.

https://jomitech.com/downloads/TwineCom ... gin123.zip

[Serhio]

Thanks, JomiTech!

This version works perfectly—no conflicts!!!
Can we now expect this TwineCompile update in GetIt for Rad Studio 12 and the new 13 versions?
I think this update would be useful for all users and will also be available in the new version of Rad Studio.
(We are currently considering upgrading to version 13)

Thank you for your work.

[jomitech]

This fix was already put in place for 13.0 - so it's available in GetIt for the latest IDE version. I don't know if we'll update it for 12.x, there have only been a handful of installations impacted by this issue.