[fpc-pascal] fpmake: output directories

[Michael Van Canneyt]

On Tue, 2 Jun 2009, Vincent Snijders wrote:

> Michael Van Canneyt schreef:
>> 
>> 
>> On Mon, 1 Jun 2009, Mattias Gaertner wrote:
>> 
>>> Hi fpmake devels,
>>> 
>>> fpmake uses as ppu output directory for example:
>>> units/i386-linux/
>>> And there is no way to change this. Right?
>>> 
>>> Some LCL packages have different PPUs per widgetset, so they need an
>>> output directory per widgetset. At the moment they use for example:
>>> units/i386-linux-gtk2/
>>> Another example is to distinguish between release and debug version.
>>> 
>>> What is the best/recommended way to solve this with fpmake?
>> 
>> You can't in this way.
>
> So, no debug and release version on one computer?

Not in this way, at least.

Don't forget that the system is geared towards *installing* the units in 
a directory. As far as I can see, this is never done with lazarus. The 
compiled units always reside in the lazarus source tree.

I have asked the question once: How to have 2 lazarus unit trees, 
(e.g. produced by 2 compilers, or debug and not-debug) 
but I never got an answer.

for fpmake I envisaged a system
/somefpcdir/packagename/units/i386-linux
and then a debug version in 
/somefpcdir/debug/packagename/units/i386-linux

Or something similar. But nothing is fixed yet.

>> The problem is the dependencies. The build system must know where the units 
>> are for every package, so this is packagename/units/CPU-OS/
>> 
>> You must make different packages per widgetset. They can be generated
>> by the same fpmake.
>> That means that you must make a package lcl-gtk2, which then is installed 
>> in
>> lcl-gtk2/units/linux-gtk2/
>> 
> typo?
> lcl-gtk2/units/i386-linux/

Yes, sorry :(

Michael.