[Lazarus] Failure to recompile with a different define

Giuliano Colla giuliano.colla at fastwebnet.it
Thu Sep 1 18:29:42 CEST 2016


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 
perform a given task and can be used by many project is rather 
intuitive, putting all the units of a project into a package isn't very 
intuitive for an inexperienced user. Moreover in that way *all* units 
would be recompiled every time one switches from one project to the other.

>   
>> >this could make it much easier to have more than one project in the same
>> >directory, without any risk of mix-ups.
> Why do you must put all projects and units into a single directory?

You don't have to, but you may happen to keep more than one project in a 
single directory. E.g. I have a "Sandbox" directory which I use for 
simple tests, and where you can find a number of small projects,

>> >A simple option could be to change the default unit path proposed by
>> >Lazarus: in place of lib/$(TargetCPU)-$(TargetOS), make it
>> >lib/$(ProjectName)/$(TargetCPU)-$(TargetOS)
> See here:
> http://wiki.lazarus.freepascal.org/IDE_Window:_Compiler_Options#Change_the_output_directory_of_project_and_all_packages

Thank you, I'm aware of that, and personally I'm perfectly happy with 
what is provided by Lazarus.
I was just suggesting something which might help inexperienced users to 
avoid pitfalls.

Giuliano

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20160901/1f4d28f1/attachment.html>


More information about the Lazarus mailing list