Well, I used MAP files in Delphi 7 and it was pretty descriptive, all function names, what library (UNIT/DLL) they are linking from ... classes e.t.c.
Just try and see either it is what you looking for Eugene Nosko On 3/14/07, CubicDesign <[EMAIL PROTECTED]> wrote: > > Good idea. I know where is this option in my Delphi 7. > How can I see the included functions after that? I should decompile the > EXE? > Thank you very much. > > I already compared a EXE file containing the DCU and one EXE not > containing that DCU but the differences were huge and it was very > difficult to keep track of all changes. Also a resource editor show that > some glyphs (BMPs) were included in the bigger EXE. Their names was > something like Network, Floppy, System... so I think they were pushed > there by those API 'units' included in my DCU (like ShlObj, ActiveX, > SHFolder). > > > > Eugene Nosko wrote: > > Hi Gabriel > > > > There is a way to see what is actually compiled into your executable. > Try > > compiling with detailed MAP file which will outline each function, class > and > > unit. There is an option in Delphi to compile and MAP info to the file > but > > different versions of Delphi have this setting in different places so do > > google for your version ;) > > > > I hope it helps > > > > Eugene Nosko > > > > On 3/9/07, CubicDesign <[EMAIL PROTECTED]> wrote: > > > >>> Rob Kennedy wrote: > >>> Looks like this is a unit that defines a form class. It includes a > >>> > >> resource file, right? That resource must be included in the EXE since > >> the compiler cannot know whether that resource really gets used. > >> Resources always get included. > >> > >> > >> Thanks for the answer. > >> No. It defines ONLY 2 classes: > >> > >> TYPE > >> TMyIniFile = class(TIniFile) > >> TMRUList = class(TPersistent) > >> > >> The rest of the code is over 200 functions and procedures. > >> Since I didn't worked very much with ShlObj, ActiveX, SHFolder, ComObj, > >> and I don't know very well theirs inside, I tend to blame these ones. > >> But only because I have nobody else to blame :) > >> > >> There is a way to see what was compiled in my EXE? Maybe with a > resource > >> decompiler? > >> > >> Gabriel > >> > >> > >> > >> > >> Rob Kennedy wrote: > >> > >>> CubicDesign wrote: > >>> > >>> > >>>> I added today that unit I was talking about a week before, to an > >>>> existing project. > >>>> I just added the unit to the uses clause and nothing more! I did not > >>>> used any of its procedures or functions. > >>>> The size of the exe file jumped from 409600 to 542800 bytes. The size > >>>> > >> of > >> > >>>> the compiled unit is 100KB. > >>>> > >>>> What it is wrong? The size of my EXE should not increase since I used > >>>> > >> no > >> > >>>> functions/procedures from that unit. > >>>> > >>>> The header of that unit is something like: > >>>> > >>>> UNIT MyTpu; > >>>> interface > >>>> uses Windows, Messages, SysUtils, Variants, Classes, Graphics, > >>>> > >> Controls, > >> > >>>> Forms, > >>>> Dialogs, StdCtrls, Registry, ShellApi, mmSystem, ComObj, JPEG, > >>>> DateUtils, > >>>> IniFiles, FileCtrl, ShlObj, ActiveX, SHFolder, ClipBrd, > ImageHlp, > >>>> WinSock, > >>>> FastStrings, UnitEmailVerifier, CubTPU_ext; > >>>> > >>>> > >>> > >>> > >> __________________________________________________ > >> Delphi-Talk mailing list -> Delphi-Talk@elists.org > >> http://www.elists.org/mailman/listinfo/delphi-talk > >> > >> > > > > > > > > > __________________________________________________ > Delphi-Talk mailing list -> Delphi-Talk@elists.org > http://www.elists.org/mailman/listinfo/delphi-talk > -- "Human brain is a search engine for joy" - Eugene Nosko __________________________________________________ Delphi-Talk mailing list -> Delphi-Talk@elists.org http://www.elists.org/mailman/listinfo/delphi-talk
