Every now and then you want to know what units your project is made of. Not just the units require to build your project, but actually the ones ending up in the executable (i.e. not removed by the compiler or linker).
I had long forgotten that Chris Hesik [WayBack] wrote in debugging – How can I find all the units in my Delphi app? – Stack Overflow [WayBack]:
you can have the Delphi compiler show you a list of used .dcus by passing –depends when you compile a project. It will output a .d file with a list of the .dcus (and .dcps) that were required.
This reminded me of that: The –depends option is supposed to work with the Delphi compiler, and it outputs a .d file. Does it still work in Berlin, and where is the file supposed to be output to? – David Nottage – Google+ [WayBack]
In the mean time, I wrote a batch file that parses the .MAP file to see which units actually made it into your .EXE [WayBack] which works only for Widows executables (as I hardly do cross-platform Delphi development).
Uwe Schuster [WayBack] reported the IDE won’t pass on the –depends switch in Delphi XE and up (version 15.0.3953.35171) [WayBack] which means you need to pass this from the command-line.
Ondrej Kelle (G+/SO) pointed out that:
msbuild hello.dproj /property:DCC_OutputDependencies=true
- It does work from the IDE if you check “use MSBuild externally”
The msbuild property setting is available in at least Delphi/C++Builder versions 2007 and 2010..Berlin as it is in CodeGear.Cpp.Targets and CodeGear.Delphi.Targets/RTL.Build.targets for BDS versions 5, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17 and 18. It might be available in versions 2005/2006/2009 as well but I don’t have these lying around any more.
–jeroen
Read the rest of this entry »
Like this:
Like Loading...
