Okay. So I have Delphi 2010 installed.
It compiles/builds
JCL/packages/d14/jcl.dpk just fine
I then have another pakcage (not Jedi) that requires JCL. (I get error that it requires that package.)
I have tried adding the path to jcl140.bpl to its project options, but that does not help.
(I would preferably like to avoid running the JCL/JVCL installer again since I have the same versions of source code running on multiple computers.)
I decided to solve this another way. I decided to run the Jedi JCL installer. (And then switch the source back to the old afterwards.) That created the otherwise missing jcl140.dcp file (I only had jcl140.dpk, jcl140.bpl etc. but could not create/find the .dcp one) This seems to work.
Related
I just did a complete system rebuild (format C drive and go from there)... Win 10 Pro 64 bit. I reinstalled Delphi Rio, the INITIAL release (6.7GB).... Delphi started up fine. I had previously downloaded Delphi Rio Patch 2, (7.3GB), so I unzipped it, and ran setup. It automatically chose the middle option (Modify), so I left it at that... and installed. It appeared to run fine. After completion, I noticed that it had removed the Delphi icon I created on my desktop, and that the links in my start menu for Delphi no longer work... I did not investigate a whole lot, as I had a patch 3 (7.9GB) to install as well. I unzipped, ran setup, and again Modify was the default option, so I ran with that... no errors. When completed, I tried to run Delphi. I have what I think is the appropriate directory structure (C:\Program Files (x86)\Embarcadero\Studio\20.0\bin) with 298 files in the bin directory, however bds.exe is NOT one of the files. Any idea what is going on?
The only possibility I can think of is that I have let my subscription expire.... and I am not entitled to the patches, yet the Embarcadero support system let me download them. Could this be the explanation?
Updating a certain Delphi version is usually done like this:
Download new ISO file or web installer
Uninstall the Delphi version you want to update and keep the registry settings (you are asked about this during the process)
Run setup from downloaded ISO or web installer
Your approach of installing the newer version on top of the older one is clearly the wrong way.
This is also explained in the install instructions (readme file) that comes with every ISO or web installer.
I just did the update of RAD XE2 to the latest service pack. I can not compile my application using Fast reports stuff inside. The error at compile says "frxclass.dcu not found".
This seems to be a problem like
FAST REPORT ISSUE
Is this a bug of updateing XE2 or did I do something wrong while executing the update process ?
This problem happens with XE2 and XE3. I have FR professional with source and have done several installations each of which have suffered problems. I believe that it is an incompatibility between the included version of FR and the licenced version. My solution was thorough:
1. Go into control panel and delete any and all installations of FR.
2. Go to the program files folder and manually delete any FR folders.
3. Inside the Delphi IDE go into options, library and locate and delete any reference to fast report paths.
4. Go into the IDE Install Packages option and make sure that there are no references to FR packages.
5. Quit the IDE and now install FR using the supplied installer. When this completes you should be able to fire up the IDE fine without frClass errors.
Just a quick question for those of you that know. Is it possible to have both Delphi (ver 7) and Lazarus installed at the same time. I want to make sure the Lazarus install will not interfere with my current Delphi install in ANY WAY. I would have asked this on the Lazarus fourms but thought I would get quicker reply here.
Anyway if you have both Delphi & Lazarus installed please tell me any problems you have encountered (if any) thanks.
Chris
Lazarus does not interfere with any version of Delphi, they can live along very happily.
The only interference is for commandline building, both projects have a make.exe file which are not the same.
This is easily solvable by not adding FPC to the path (removing it via control-panel system), and do a
set PATH=c:\fpc\2.5.1\bin\i386-win32;%PATH%
or wherever you installed as first line in your batch files.
I generally don't bother, but a previous employer we did a lot of cmdline building with dcc, and then it matters.
File associations are another, but already named. (but not such a big problem since the project extensions vary (.dpr vs .lpr, .dproj vs .lpi) )
Btw: Other development products (cygwin,mingw, and maybe even VS) have their own respective make.exe files and the same kind of problems.
I currently have Delphi 5 and Lazarus both installed on my Windows 7 laptop. As near as I can tell they don't interfere with each other.
I don't really use Lazarus though, as I prefer Delphi 5 which is what I've used forever.
I have Delphi 2006, Delphi 2010 and Lazarus installed. No problems at all. I am sure Delphi 7 will be the same. The only problem I can see could be the use of .pas extension in Lazarus. I mean because of association problems. But you can use a different extension for Lazarus (free pascal) source files. I think the installer asks you that.
I have Lazarus "installed" on a USB drive. It interferes with nothing whatsoever. It is actually a checkout of the Git repository that mirrors the SVN repository. I installed the latest stable FPC to C:\FPC, and then copied that folder to inside my lazarus source folder, e.g. \lazarus\FPC\ (and then uninstalled the C:\FPC installation), and then whenever I like I build the latest lazarus like this:
X:\lazarus\> git fetch
[...fetch messages...]
X:\lazarus\> FPC\2.4.0\bin\i386-win32\make.exe clean all
[...compiler output messages...]
X:\lazarus\> startlazarus
[...IDE starts up...]
The main advantage of this is that if you find an IDE bug, the source is immediately available and you can make and submit a patch instantly.
On my D2007 installation, I installed the DDevExtension, and also the IDEFixPack from the same site.
Unfortunately, now I have a component, TmxSideBarPro, that won't load into the IDE anymore. Any time I try, I get the following error in the IDE:
EPackageRegistrationException
Registration procedure, Mxtaskpanereg.Register in package c:!_cg2007\Packages\mxTaskPane_D11D.bpl raised exception class EAccessViolation: Access violation at address 20006A04 in module 'rtl100.bpl'. Read of address 9B8825DB.
I have tried uninstalling the extension above, and they report a successful uninstall, but I still get the error above when trying to install the component. The component vendor hasn't helped much, and I'm not sure they're in business anymore at this point. They did ask if I'd installed any special IDE tools, I explained my situation to them, but I never heard back from them anymore.
What can I do here to get this component working again? I'm willing to reinstall D2007, but I've also got D2009 installed, and I've read that you shouldn't install an older version after a new version.
Also, if there's a different forum category this should be in, please let me know.
Is there something loading that mxTaskPane_D11D? TO find out rename mxTaskPane_D11D to mxTaskPane_D11D!.!bpl (extra characters). Now something ELSE will fail to load. Now unregister that.
Are you sure you have uninstalled both DDevExtensions and IDEFixPack, for the right version?
If so your Delphi should be as it was before.
They don't do any permanent modification IIRC.
Are you sure nothing else changed? Did you recompile the mx package by any chance?
I've found Andreas' tools of very good quality and I would probably look elsewhere 1st...
I am not familiar with that component, but if you have the source code for it, try recompiling the package. I had to recompile several component packages when migrating from Delphi 7 to Delphi 2007. Many of the packages were Delphi 5 packages.
Since Indy is now built-into the install process of Delphi 2009... is there a proper way to 'remove' it so it can be upgraded to the latest from the SVN repo? There isn't an automated option to remove it as far as I'm aware.
The dcu files for Indy are stored separately from the other Delphi units. To stop using them, simply remove that directory from the search path, library path, etc., and remove the source files from the browse path.
You can remove the design-time packages the same as any other design-time packages. Remove them from the IDE configuration, and then delete the bpl and dcp files. (If you just delete the files, you may get errors when you next start the IDE since it won't find the expected files.)
Once the Indy components no longer appear on the Tool Palette, the packages no longer appear on the package list, and compiling a project that references Indy units fails with a "can't find used unit" error, you're ready to start installing the latest version.
As Rob already said: Just remove the direcories from Delphi's configuration. An additional step is required though: After each update, make sure they have not been added again! Some of the Delphi 2007 updates apparently did that and I missed it for quite a while until I stumbled upon a bug that I already thought fixed.
I didn't use Delphi 2009, but in older versions of Delphi the installation of Indy components was optional. So you could try launching the setup for Delphi 2009 and see if there is an option to "Add/Remove features" or something similar and use it to remove Indy.
Also, you can customize which packages should be loaded in a project, so you can simply deselect the Indy 10 one and add the one from SVN on a per-project basis (you can also configure the default configuration for projects).
PS. Indy rocks! :-)