You must Click Button "remove" Almost times! Remove the source path for Delphi and the project does not compile. Then do the same for "Library path". For anyone thats intrested. I managed to get Indy10 installed. 
| Uploader: | Dajar |
| Date Added: | 25 June 2004 |
| File Size: | 13.25 Mb |
| Operating Systems: | Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X |
| Downloads: | 32836 |
| Price: | Free* [*Free Regsitration Required] |
Why not improve Uninstall components and delphi library path? My first task is to convert some custom control packages.
EOSERV :: Forum :: Seose :: UPDATE: Seose v (release 9) - Back to sanity.
It is a shame we discussing this in the wrong place because I think there are thousands of people with the same confusion about how these packages are supposed to work. Shipping packages at the Post Office is about to get more expensive Between the untimely deaths of two incredible performers and the realization that we have to sit through another whole year of campaigning from Maybe this is not so? I added the path to the. That is exactly what it already does when the Runtime Packages option is disabled.
Subscribe to RSS
Only if your app is linking to the DCUs directly instead of using Indy's packages instead. If it matters, I'm using D on XP. It uses the version So being able to use a single source tree but multiple package files, one for each delphi would solve the problem if only Delphi could be told NOT to look at the pas or dcu files but instead use the package file. Idbwsecomponent.dcu a test I did this: But you still have to make sure the Packages list is accurate so it knows which Packages it can pull code from.
download IdBaseComponent.dcu Source and source code
I need to do this on a regular basis. Looks like a chopped up RAD Studio http: That is not the same as the list of Packages that the project actually uses for compiling purposes. You may as well just add the component idbasecpmponent.dcu code directly to your project instead. I have always not changed this because I believed that doing so would require me to distribute not only the exe file of my application but also a number of bpl package files.
Then do the same for "Library path". Asked 6 years, 9 months ago.
On Fri, 14 Sep On Fri, 31 Aug And when compiling idbasecomponfnt.dcu Packages, the compiler generates both static-link and dynamic-link versions. If I build with "Build with runtime packages" enabled, everything works fine. I have the path to the MyRtPkg. In order to use runtime packages that are built into this directory, this directory needs to be on your path. Yes, it is, in any version. The design part works, but for run time, the compiler must be able to find the dcu.
Usually to add a component package, all I do is add ixbasecomponent.dcu source dir to the Library path, compile the dpk and install. But I cannot think this is right, I must have done idbasecompondnt.dcu wrong to start with? More infrastructure needed for Duncan Gay's cycling safety package to balance That is exactly what Packages do for you.
The package project Directories and files: I had added all the Indy groups to the component palette but they Indy component groups just didn't want to appear. Packages are self-contained, though they may have references dibasecomponent.dcu other Packages. Since it's an installed component, you would want it to be available for any project, so setting the library path makes the most sense. See related articles to this posting.
Comments
Post a Comment