Re: [Lazarus] Failure to recompile with a different define

2016-09-01 Thread Giuliano Colla
Il 01/09/2016 15:25, Mattias Gaertner ha scritto: [...] >Using a package isn't a very intuitive solution, when*all* the units >belong to the project. Because of circular dependencies or because of company rules? No, I just mean that while putting into a package a group of units which perfor

Re: [Lazarus] Failure to recompile with a different define

2016-09-01 Thread Mattias Gaertner
On Thu, 1 Sep 2016 13:58:10 +0200 Giuliano Colla wrote: >[...] > Using a package isn't a very intuitive solution, when *all* the units > belong to the project. Because of circular dependencies or because of company rules? > this could make it much easier to have more than one project in the

Re: [Lazarus] Failure to recompile with a different define

2016-09-01 Thread Giuliano Colla
Il 01/09/2016 13:12, Mattias Gaertner ha scritto: ppus do not include the defines, so a simple compile won't rebuild ppu files. That's by design. How do you share units? If you do it manually by adding unit paths to the Compiler Options then you have to clean up manually. If you use Lazarus pack

Re: [Lazarus] Failure to recompile with a different define

2016-09-01 Thread Mattias Gaertner
On Thu, 1 Sep 2016 12:53:57 +0200 Giuliano Colla wrote: > I have two Lazarus projects, let's call them project A and project B, > which share the same sources, only with a different define: let's say > -dProjA and -dProjB. > > If, starting from a clean situation, I compile first project A, and

[Lazarus] Failure to recompile with a different define

2016-09-01 Thread Giuliano Colla
I have two Lazarus projects, let's call them project A and project B, which share the same sources, only with a different define: let's say -dProjA and -dProjB. If, starting from a clean situation, I compile first project A, and then project B, most of the modules aren't recompiled, and I end