T O P I C R E V I E W |
DavidMartel |
Posted - Oct 20 2016 : 08:00:07 I have just upgraded to the latest release 6.3.2, installed in to Berlin 10.1.
First time I started Rad Studio after the install I got an error dialogue
BDS.exe - Entry Point Not found
The procedure entry point @lextratransitions@initialization$qqrv could not be located in the dynamic link library C:\Users\Public\Documents\Embarcader\Studio\18.0\Bpl\DPKIECTRL24.bpl
I closed my project, and restarted RAD studio without incident. I create a new blank form, and try and put a component on it (in this case TImageEn), and I get the same error dialogue.
Any ideas what the problem is please?
Dave |
12 L A T E S T R E P L I E S (Newest First) |
xequte |
Posted - Oct 21 2016 : 16:23:59 Linking is not possible without the DCU's and associated DFM resources.
Nigel Xequte Software www.xequte.com nigel@xequte.com
|
DavidMartel |
Posted - Oct 21 2016 : 05:34:54 So are you saying there really should be some dfm files in the compiled directories, but with no corresponding pas files?
I will see if I can package up the changes I have made soon and email them to you. |
xequte |
Posted - Oct 21 2016 : 05:31:14 No, don't delete the *.dfm files, they are needed.
We are always interested in looking at source code changes if they will have appeal to other users.
Nigel Xequte Software www.xequte.com nigel@xequte.com
|
DavidMartel |
Posted - Oct 20 2016 : 18:47:31 Nigel,
Not only some pas files, but also some orphaned *.dfm files (ieprnform1.dfm, ieprnform2.dfm, ieprnform3.dfm, iexacquireform.dfm. IOPreviews.dfm, Previews.dfm)
I will give it a go with these deleted.
I am someone who does need to make some modifications ( a few extensions we needed to add in source code). They are somewhat generic, and if they are of interest (e.g. adding support for Angstroms as well as the other units already in place) I am happy to provide the source code changes.... once I have got it to compile through. |
xequte |
Posted - Oct 20 2016 : 17:02:30 Hi
The \Source\ folder is purely intended as to provide access to the source for documentation, and for some users who need to customize it.
Most users will have no need to access the \Source\ folder at all. They will use only the packages and the compiled unit.
The bug here is that some source files (giflzw.pas, iewords.pas and tiflzw.pas) have made it into the compiled unit folder. You should delete those.
Nigel Xequte Software www.xequte.com nigel@xequte.com
|
DavidMartel |
Posted - Oct 20 2016 : 12:12:30 Bill thanks for the detailed info. Here goes...
1. Absolutely removed all traces from hard disk
2. Ran installer (installed to c:\Components2\ImageEn) - PKIECTRL24.BPL appears in "C:\Components2\ImageEn\Delphi10.1Berlin" - PKIECTRL24.DCP appears in "C:\Components2\ImageEn\Delphi10.1Berlin" - PKIEDB24.BPL appears in "C:\Components2\ImageEn\Delphi10.1Berlin" - PKIEDB24.DCP appears in "C:\Components2\ImageEn\Delphi10.1Berlin" - DPKIECTRL24.BPL appears in "C:\Components2\ImageEn\Delphi10.1Berlin" - DPKIECTRL24.DCP appears in "C:\Components2\ImageEn\Delphi10.1Berlin" - DPKIEDB24.BPL appears in "C:\Components2\ImageEn\Delphi10.1Berlin" - DPKIEDB24.DCP appears in "C:\Components2\ImageEn\Delphi10.1Berlin"
ALSO - PKIECTRL24.BPL appears in "C:\Users\Public\Documents\Embarcadero\Studio\18.0\Bpl" - PKIEDB24.BPL appears in "C:\Users\Public\Documents\Embarcadero\Studio\18.0\Bpl"
ALSO Installer has added "C:\Components2\ImageEn\Delphi10.1Berlin" to library path. Installer has not added "C:\Components2\ImageEn\Source"
ALSO Check in packages page and the installer has registered - "C:\Components2\ImageEn\Delphi10.1Berlin\DPKIECTRL24.BPL" - "C:\Components2\ImageEn\Delphi10.1Berlin\DPKIEDB24.BPL" [i.e. in ImageEn directory, not in Embarcadero library, but I will leave it like that for now]
NOW Try and open and compile any demo application (e.g. ..\DisplayMagnify). I have tried a number and all fail with "F2039 Could not create output file 'c:\Components2\ImageEn\Delphi10.1Berlin\tiflzw.dcu" [And this is with a Vanilla install, no manual anything....] I guess this is a file permission issue, in that it is trying to write a dcu file in to the ImageEn directory and we may not have permission. Perhaps the project files for the demos ought to be set to put the units in the demo directory with the project, rather than back to the main source directory??
Now back to the source directories.... What really is the source directory??
The installer adds the path to "..\ImageEn\Delphi10.1Berlin". However there is also a directory "..\ImageEn\Source" and this is not added to the library path. There is considerable source code in "..\ImageEn\Source", but there is also some source code in "..\ImageEn\Delphi10.1Berlin". Strangely there is some overlap between the 2 (e.g. ieWords.pas is in both, but with subtly different versions, though in this case it is just a comment line and an extra blank line. This duplication etc. concerns me a little. It seems rather untidy and makes me wonder whether this was an oversight? That then makes me doubt more....
...and this doubt then moves on to the fact that if I try to rebuild the packages following your instructions, the first 2 build OK, but the design packages both fail to build with "E1026 File Not Found: 'IERegCtrl.dcr'" and "E1026 File Not Found: 'IERegDB.dcr'" respectively. If I manually add "c:\Components2\ImageEn\Source", then the other 2 packages build, but this is untidy and now it makes me wonder whether the fact I have 2 copies of source code in the 2 directories on the path may cause problems later...
Now. Having rebuilt the 2 bpl files (and associated dcp files where did they build? Not in "c:\Components2\ImageEn\Delphi10.1Berlin" which is their registered locations, the bpl files are in "C:\Users\Public\Documents\Embarcadero\Studio\18.0\Bpl" and the dcp files are in "C:\Users\Public\Documents\Embarcadero\Studio\18.0\DCP"
So now I have to uninstall the bpl files that are in "C:\Components2\ImageEn\Delphi10.1Berlin" and install the ones in the Embarcadero directories.
The demos still won't compile though (same file permission issue I guess).
One further observation regarding "what is the source directory"? When I open the group project (C:\Components2\ImageEn\Source\Delphi10.1Berlin\ImageEnProjectGroup.groupproj) and look at the long 'contains' list for PKIECtrl24.bpl (for example) and then I try and double click on almost any of the files to load them for editing/viewing (e.g. BMPFilt.pas) I get a message "Cannot open c:\Components2\ImageEn\Source\Delphi10.1Berlin\BMPFilt.pas".
It appears to me that there is some confusion between "..\ImageEn\Source\Delphi10.1Berlin" and "..\ImageEn\Delphi10.1Berlin". If I had to take my guess I suspect there should not be "..\ImageEn\Delphi10.1Berlin" at all. I think it should probably only be a subdirectory of 'source'..... but I guess we might need some input from the Xecute team on that one.
Sorry for the long-winded post, but it seems there is considerable detail that might allow a conclusive answer as to whether there is something amiss in this latest install... |
w2m |
Posted - Oct 20 2016 : 10:41:00 Guidance
1. Remove all ImageEn files and make sure duplicates do not exist anywhere. 2. Reinstall. 3. Select Tools -> Options, Library and ensure the ImageEn source files folder is listed in your "Library path" 4. Compile PKIECTRL*.DPK and PKIEDB*.DPK first, then install DPKIECTRL*.BPL and DPKIEDB*.BPL... but read and follow the official instructions carefully. Generally if you still have problems compiling the dpk's then it usually it means you have duplicate dcu's, bpl's or dcp's somewhere on your hard drive.
Installation
Generally you should use the ImageEn installer to handle the compilation and installation of the ImageEn packages. However you can also do it manually as follows...
Note: Before installing ImageEn, remove ALL old versions of it (remove all pkie*.bpl and dcp files): 1. In Delphi select Tools -> Options, Library tab. 2. Go through the list of Library paths and check for any that contain ImageEn packages (pkie*.bpl files) 3. Delete any ImageEn packages that you find
COMPILING THE IMAGEEN PACKAGES: For each version of Delphi/C++ Builder you should have four BPL packages named DPKIECTRL*.BPL, DPKIEDB*.BPL, PKIECTRL*.BPL and PKIEDB*.BPL where * indicates the version, e.g. DPKIECTRL16.BPL for Delphi XE2.
If these were not installed then you can manually compile them as follows:
1. Select Tools -> Options, Library and ensure the ImageEn source files folder is listed in your "Library path"
2. Open and compile PKIECTRL*.DPK, PKIEDB*.DPK, DPKIECTRL*.DPK and DPKIEDB*.DPK (where * is the version number for your Delphi/C++ builder product)
MANUALLY INSTALLING THE IMAGEEN PACKAGES: If you did not install the ImageEn packages into Delphi/C++ Builder using the installer then you can do it manually as follows:
1. Copy PKIECTRL*.BPL and PKIEDB*.BPL to your Windows "System" folder or Delphi "Bin" folder (where * is the version number for your Delphi/C++ builder product)
Note: The "System" folder is generally "C:\Windows\System32" on a 32bit system or "C:\Windows\SysWOW64\" on a 64bit one. The Delphi “Bin” folder will be similar to: "C:\Program Files\Embarcadero\Rad Studio\7.0\Bin"
2. Select Component -> Install packages, and press Add button. Then select DPKIECTRL*.BPL and DPKIEDB*.BPL (the latter is for database components).
3. Select Tools -> Options, Library and ensure that the ImageEn source folder is in your "Library path".
Bill Miller Adirondack Software & Graphics Email: w2m@hughes.net EBook: http://www.imageen.com/ebook/ Custom Commercial ImageEn Development |
DavidMartel |
Posted - Oct 20 2016 : 10:14:43 Oh, and BTW after a fresh install the DCP and BPL files are not in the Embarcadero directories the way most component packages seem to work. They are in ....\ImageEn\Delphi10.1Berlin.
However if you go and rebuild the packages from the package project files, then you end up with the bpl files in ...\public documents\Embarcadero\Studio\18.0\lib\bpl.
Perhaps this is a bit of the issue as you now have 2 copies of the bpl, but they may not match with the dcp? |
DavidMartel |
Posted - Oct 20 2016 : 10:11:38 Bill. Thanks for your time in replying. I am sure we all appreciate the number of questions you answer on here...
This just gets worse.
I have removed ImageEn totally from the system, removed all path entries etc. from Berlin
I have run the installer from fresh. I get the components on the palette. So far so good.
So lets try a demo....
Open demos\Display\DislayAdjust\Display.dproj Try and compile and it gives "F2039 Could not create output file 'c:\Components2\ImageEn\Delphi10.1Berlin\tiflzw.dcu"
Agh!
[ Tried a simple app of my own with one TImageEnView, one button and a file open dialog. At least that compiles, but I tried to load a very small jpeg in it and I get "Out of memory".]...EDIT: My Bad. This was my mistake. I can load the jpeg file... code completion meant I did not get the peocedure I was expecting...
Frustrated.
|
w2m |
Posted - Oct 20 2016 : 08:43:50 Because the file exists, the problem is the IDE's path to the file, otherwise the file would be found.
Bill Miller Adirondack Software & Graphics Email: w2m@hughes.net EBook: http://www.imageen.com/ebook/ Custom Commercial ImageEn Development |
DavidMartel |
Posted - Oct 20 2016 : 08:41:00 Yes it is in the folder, and I see the components in the palette, which I think I would not otherwise. I installed over the top of an earlier version, though I had uninstalled the ImageEn packages from the palette.
I have all the ImageEn paths in the IDE from before, but I would hope the installer would deal with that.
Ho, hum. I guess it will be a start from scratch. I will remove from berlin, delete the folders and try again...
Thanks for the reply. I will come back later to update how it goes. |
w2m |
Posted - Oct 20 2016 : 08:30:28 Is DPKIECTRL24.bpl in the C:\Users\Public\Documents\Embarcader\Studio\18.0\Bpl\ folder? if not then the design package for ImageEn is not installed into the ide. Is the ImageEn path in the IDE Path?
I would delete all your ImageEn folders and reinstall. Also make sure the path is also in the ide.
Bill Miller Adirondack Software & Graphics Email: w2m@hughes.net EBook: http://www.imageen.com/ebook/ Custom Commercial ImageEn Development |
|
|