On Tue, 14 Aug 2007, Darius Blaszijk wrote:
> In fpmkunit.pp I found the function FixPath for which I don't understand the > exact purpose of. What happens is that if I issue an install command the > BaseInstallDir takes the FPCDIR env variable (which is c:\fpc in my case) > (line 1472). This value is then passed on to FixPath which converts all > '/','\',':' to PathDelim, so I end up with 'c\\fpc' as base install directory. > > Two things > > 1) why is the colon converted to a slash which yields invalid paths (at least > on windows) > 2) although fpmake initially was developed to be a make tool for FPC, it can > (and will be) used for other projects. Therefore I would propose not to > initialize FBaseInstallDir with the FPC directory. But rather raise an > exception if the basedir is not set in fpmake.pp (when issued an install > command only ofcourse). This will make setting this variable mandatory. I suggest that we introduce a boolean property in TInstaller: FPCProject by default set to True. If this is True, BaseInstallDir is initialized with FPCDir. If False, it's set to a sensible value: /usr on linux, or c:\program files\packagename on Windows. Michael. _______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal