Brian wrote
> Yes. Version 2.6.4 which I have been using has this problem.
Huh, version 3.0.0 and 3.1.1 too. ;-(
It is sad because I love to use {$I define.inc} in the units. (define.inc
--> with all the custom defines --> one unique file for all the units).
But if I forget to re-build all, the
Yes. Version 2.6.4 which I have been using has this problem.
Two work arounds :
1) Attempt to compile the include file which will fail , but the compiler
appears to then recognize the file has changed when the main program / unit
is later compiled.
2) save the file after the change , the recompi
On 09/09/2016 01:03 AM, Graeme Geldenhuys wrote:
On 2016-09-08 22:57, David Emerson wrote:
I'm wondering if anyone else has run into it, and if there might be a
workaround.
Yes, it has been happening here for years. No workaround that I know of,
except to do a Build All after you make changes
On 2016-09-08 22:57, David Emerson wrote:
> I'm wondering if anyone else has run into it, and if there might be a
> workaround.
Yes, it has been happening here for years. No workaround that I know of,
except to do a Build All after you make changes to include files. But
that's up to the developer
Hi all,
a couple days ago I filed this:
http://mantis.freepascal.org/view.php?id=30569
In a particular situation (common in my project), making changes to an
include file does not trigger recompilation of the unit(s) where it is
included.
I'm wondering if anyone else has run into it, and if
