🚀 go-pugleaf

You are right, the /M switch will not compile a .pas file if it finds the 
corresponding .dcu file in the same directory and the .dcu file has a 
later datetimestamp.  I never use the /M switch since DCC32 is so 
blazingly fast, not sure what benefits would be gained by using it.

My normal practice is the create a dir called <delphi>/dcu and designate 
that as the place for my dcu both in the IDE and when using DCC32.  When 
it is time to do a build, I erase everything in that dir so I can be sure 
the build reflects the current source code and not some stray .dcu that 
might be there to throw me off.  I spent nearly two days tracking down a 
bug once that turned out to be an old dcu that nonetheless had a more 
recent date than the .pas file because the .pas file was recovered from a 
stash of old code that I wanted/needed to go back to.

As for using packages, I use them a lot, though I often do builds on a 
machine that has none of them installed.  DCC32 doesn't care about 
packages, only source code or dcu, though you can use it to build from 
.dpk.

Again, I strongly recommend never using the /M switch with DCC32 unless 
you are absolutely sure you know what is in every .dcu it might find.

In the IDE, on the other hand, I almost always use the equivalent of the 
/M swithc, CTL-F9.  As for packages in the IDE, I generally set up a 
seperate project (.dpr) that is the "host" for the develoment of the 
package.  Then I set up a seperate project manager that contains all my 
packages in the order they need to be installed.  Whenever I make a major 
change (or a change to one early in the chain), I have to use the right 
click, build, then right click and install.  AT least this is what I 
needed for D5 and D6.  The other methods seemed to fail more often than 
not.

Also, when using packages, make sure your default .dof file does not 
contain them.

Sorry for being long winded,

Brandon