Gurusamy Sarathy wrote: >On Fri, 18 Feb 2005 18:24:25 GMT, Steve Hay wrote: > > >>Gurusamy Sarathy wrote: >> >> >>>Have you tried translating the backslashes into normal slashes? >>> >>> >>This works fine, but results in a Config.pm containing rather mixed-up >>looking paths like c:/perl\lib, which I'd rather not have even if it >>does work ;) >> >> > >Isn't this a "bug" in whatever diddles Config.pm, config.h, et al? >It seems like the paths should get normalized by the tools regardless >of what the user/makefiles happened to pass in. > I couldn't disagree with that, but its no good having, say, configpm apply File::Spec->canonpath() to all the Config.pm option values because they aren't all paths and many of them quite legitimately contain forward slashes (e.g. switches for things like "more /e" and "cmd /x /c", or things like "Data/Dumper" in dynamic_ext).
Even having win32/config_sh.PL (the script that win32's CFG_VARS are first passed to) try to fix up the values in CFG_VARS that might have / rather than \ is perilous because one of the options concerned is LINK_FLAGS, which contains a mixture of link.exe switches and paths. So I think that having win32/makefile.mk use the right paths to start with is going to be easier. - Steve ------------------------------------------------ Radan Computational Ltd. The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.
