On Mon, 13 Aug 2007, [EMAIL PROTECTED] wrote:
> >> I was doing some tests with fpmake and came across what appears to be an > >> inconsistency. > >> > >> When fpmaking a program a units/cpu-os is created but the commandline > >> parameters for FPC are "-FE." which causes the tool and possible other > >> units to be placed in the directory where the program is located. > >> When calling "fpmake clean", the clean algorithm cannot find either the > >> .ppu/.o or the .exe files as it searches the units directory and not the > >> root dir. > >> > >> I would like to patch this inconsistency, but I am not sure what the > >> consensus is on fpmaking tools. > >> > >> 1) should -FU.units/cpu-os be used, so all compiled stuff is separated > >> from the executable which will result in the root dir > >> 2) should -FE. be used as it is now, but the units directory not be > >> created anymore and the clean algorithm adjusted so it searches the > >> right directory? > > > > Solution 1) needs to be fixed. This is a prerequisite for good > > cross-compiling support. Maybe even > > the executables need to be placed in a bin/cpu-os directory and symlinked > > (or copied) to the > > current dir. > > Sounds like a good idea. Shall I prepare a patch for it? > > I'm just wondering about the symlink/copy of the executable. Shouldn't > that be a task for "fmake install"? I also think so; I don't think the copy/symlink is necessary; The binary should simply be outputted in the bin/os-cpu directory. fpmake can write a message like 'Writing binary to bin/os-cpu directory' so the user knows where to look. Michael. _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
