When installing IBX 2.2.0, today's release, using On-line Package manager:
[Error]
[Window Title]
Ambiguous unit found
[Content]
The unit IBXCustomIBLocalDBSupport exists twice in the unit path of the IDE:
1. "C:\ProgramFilesCP\LFixed\config_lazarus\onlinepackagemanager\packages\ibx\runtime\lib\x86_64-win64\IBXCustomIBLocalDBSupport.ppu"
2. "C:\ProgramFilesCP\LFixed\config_lazarus\onlinepackagemanager\packages\ibx\iblocaldb\lib\x86_64-win64\IBXCustomIBLocalDBSupport.ppu"
Hint: Check if two packages contain a unit with the same name.
[Ignore] [Ignore all] [Abort]
I have two Lazarus installs for working (2.0 RC2 Linux 64 bits and 1.8.4 Windows 64 bits). In both, I use the IBX package and it's version 2.2.0 that OPM has currently.
I see in that same forum 2.3.2 is available.
Yes, I can update to 2.3.2, but it has separate files for windows and linux, which is strange: http://www.mwasoftware.co.uk/ibx
How does OPM work? Does it depend on you to make the new version available manually?
Usually yes, but the package maintener can provide a json file, which will notify the user if a new version of the package is available.
Yes, I can update to 2.3.2, but it has separate files for windows and linux, which is strange: http://www.mwasoftware.co.uk/ibx
Strange indeed. A quick comparison of the source code shows no differences.
I am testing Lazarus 2.0.0. RC 3 FPC 3.2.0 Beta:
----------------------------------------
[Window Title]
Ambiguous unit found
[Content]
The unit IBXCustomIBLocalDBSupport exists twice in the unit path of the IDE:
1. "C:\fpcupdeluxe\config_lazarus\onlinepackagemanager\packages\ibx\runtime\lib\i386-win32\IBXCustomIBLocalDBSupport.ppu"
2. "C:\fpcupdeluxe\config_lazarus\onlinepackagemanager\packages\ibx\iblocaldb\lib\i386-win32\IBXCustomIBLocalDBSupport.ppu"
Hint: Check if two packages contain a unit with the same name.
[Ignore] [Ignore all] [Abort]
--------------------------------------
Is there a solution or what is the best workaround while the deadlock between IBX and OPM remains?