Log On
Embarcadero Home
Watch, Follow, &
Connect with Us
Share This
QualityCentral
Communities
Articles
Blogs
Resources
Downloads
Help
QualityCentral
Delphi-BCB
Compiler
Delphi
Anonymous Methods
BASM
Code Generation/Optimization
Error Recovery
Errors - Warnings
Exceptions
Execution
Finalization
Generics
Header Generation
Interaction with UI
Interfaces
Language
Linker
Make Logic
Memory Manager
OBJ Generation
OBJ Support
Other Compiler
Packages
RTTI
String Resources
TD Debug Info
Thread Local Storage
Version resilience
You are not logged in.
Help
Print
Public Report
Report From:
Delphi-BCB/Compiler/Delphi/Packages
[ Add a report in this area ]
Report #:
1496
Status:
Withdrawn
Contain DCUs in design time packages
Project:
Delphi
Build #:
0
Version:
6.0
Submitted By:
Ritsaert Hornstra
Report Type:
New Feature Request
Date Reported:
6/12/2002 11:45:54 PM
Severity:
Extreme corner case
Last Updated:
5/2/2003 12:58:35 PM
Platform:
All platforms
Internal Tracking #:
Resolution:
None
Resolved in Build:
:
None
Duplicate of:
None
Voting and Rating
Overall Rating:
(13 Total Ratings)
1.85 out of 5
Total Votes:
None
Description
When distributing precompiled packages you also need to distribute the DCU's along with it. Is it possible to 'stuff' the DCU's into the resource section of the package? It has the following Pros:
- This will clear up the $(DELPI)/lib directory considerably
- When a package is developen in another directory, the library path does not need extension (only for the sourcecode if needed).
A design time Package should not only contain the dcu's of itself but also the dcu's of the runtime packages it "opens".
Steps to Reproduce:
None
Workarounds
None
Attachment
None
Comments
Joe White at 6/13/2002 8:20:53 AM
-
> When distributing precompiled packages you also
> need to distribute the DCU's along with it.
I don't think that's true. You should be able to distribute just packagename.bpl and packagename.dcp. (The .dcp file includes the interface-section information from all of the units in the package - it should be able to replace all of the individual .dcus, as long as the end application is compiled using packages.)
Actually, if you're distributing a pure design-time package (i.e., your code is only used at design time, and won't be linked into any EXEs created by your end-users), you can just distribute the .bpl.
Apply the usual caveats about distributing .dcu code instead of source (i.e., not compatible across Delphi versions).
Ritsaert Hornstra at 6/20/2002 1:35:55 AM
-
What I was referring to was in fact a DCP file!
After testing/ reading the help file for a while I got it right.
So the feature already exists
Sebastian Modersohn at 6/22/2002 8:09:15 AM
-
If the requested feature does already exist, then please withdraw your report.
Registered User at 6/13/2002 8:42:07 AM
-
I think you're right.
View Your Reports
Search
Server Response from: ETNACODE01
Developer Tools
Blackfish SQL
C++Builder
Delphi
FireMonkey
Prism
InterBase
JBuilder
J Optimizer
HTML5 Builder
3rdRail & TurboRuby
Database Tools
Change Manager
DBArtisan
DB Optimizer
ER/Studio
Performance Center
Rapid SQL
Technical Articles
Tutorials
White Papers
Press Releases
Newsletters
Add Content (GetPublished)
Audio
Audio & Video
Video
Bugs & Suggestions (QualityCentral)
Discussion Forums
Examples (CodeCentral)
Tags
Technology Partners
Downloads
Free Trials
Registered User Downloads
Beta Programs
Add Content (GetPublished)
Articles
Blogs
Bugs & Suggestions (QualityCentral)
Discussion Forums
Examples (CodeCentral)
Member Services
About
Connect with Us