I mentioned to Jorrit recently, that space requirements (among other things) have torpedoed my CS work for a bit. I have an external drive now, and a problem: I cannot get CS or components to build on a volume with spaces anywhere in the path. Building on my external drive, pretty inevitably will lead to a space in the path. This is required by other needs and is not, at the moment, changeable. Putting a symlink off of a path without a space in its tree does not help. CS figures out its canonical path and bombs. I have basically turned my ~/Projects/CRYSTAL tree into a symlink to another volume. The symptoms can get exciting since CS starts splitting paths into multiple components and quickly eats itself. Occasionally, it tries creating semi-random directories and sometimes succeeds. The big problem is M4 processing. No matter how I pad the options to Configure, (e.g.: "/Volumes/Path With Space/Crystal", '\"\"Path With Space\"\"', etc., the paths are evaluated enough times that somewhere it will choke. I also cannot do much with paths M4 generates off of generated canonical pathnames. I have tried editing the macros to fix this problem. After 150+ edits, I am getting nowhere, and some edits have proved mutually exclusive. Anybody have an idea? The only other solution is to go through and edit a whole bunch of other things which depend on the naming of this volume (including a bajillion symlinks and some local subversion junk). I may just start on this. In practice, many systems nowadays have paths with spaces. Sincerely, Eric Vought "Faith does not absolve us from trying to understand our world and make moral distinctions with the eyes and brain given us. Religion is as much responsibility as direction: Duty not Distinction." |
smime.p7s
Description: S/MIME cryptographic signature
