In Delphi you can add units, packages, etc to a project and it does not affect other projects the Delphi projects are well isolated. The first thing you need to understand about Python is project isolation. Currently I am dabbling in a nice MkDocs documentation generator and planning to use it for documenting my project. Why Delphi programmer needs Python at all? The main reason is: Python ecosystem is much bigger and much more active than Delphi ecosystem there are many useful and actively developing projects in Python, much more than you can find in Delphi. The release versions of *.dcp files has overwritten the debug versions, but the *.dcp files served their purpose: the compiled debug version of PackageB depends on compiled debug version of PackageA, the compiled release version of PackageB depends on compiled release version of PackageA the *.dcp files are not needed anymore.
Build PackageA in RELEASE configuration.
In this case the solution is: rely on the default *.dcp file location and don’t change it. If you develop 2 packages, say PackageA and PackageB, and the PackageB depends on the PackageA ( requires PackageA), then you can’t even fully create PackageB without specifying the location of PackageA.dcp file. If you develop a single package, say PackageA, you can forget about the PackageA.dcp file and where it is located it is simply not needed. For example, the default location for Win32 platform is $(BDSCOMMONDIR)\DCP if you build a package in DEBUG configuration and then in RELEASE configuration, the release *.dcp overwrites the debug *.dcp.īut the point is: *.dcp files are needed to develop dependent packages. It always bothered me that the default *.dcp file location does not take into account the build configuration. A *.dcp file is created when Delphi builds a package.
0 kommentar(er)
