Directory Path Hell - (NS content)
ericmedley
Posts: 4,177
[rant]
So, we had to change out a disc on the File Server to get more storage. Thus begins my long trip through the seventh circle of NS hell...
It seems that duet doesn't do like most other SDKs and make the project folder the 'root' pathway but use the real pathway all the way out to the drive name (and thus shared computer involved) So, all the duet modules that I foolishly chose to use now no longer can compile.
After talking to TS I must go through and 'Pack-N-Go' all my projects with duet modules and rebuild the directories. Of course, Pack-N-Go occasionally fails to keep my folder hierarchy within the project folder in tack and just decides to put all the files (ALL THE FILES) flat in the new directory. Naturally, you don't find this failure out until you try to unpack the Pack-N-Go.
ARGGGGGG!!!!
[/rant]
So, we had to change out a disc on the File Server to get more storage. Thus begins my long trip through the seventh circle of NS hell...
It seems that duet doesn't do like most other SDKs and make the project folder the 'root' pathway but use the real pathway all the way out to the drive name (and thus shared computer involved) So, all the duet modules that I foolishly chose to use now no longer can compile.
After talking to TS I must go through and 'Pack-N-Go' all my projects with duet modules and rebuild the directories. Of course, Pack-N-Go occasionally fails to keep my folder hierarchy within the project folder in tack and just decides to put all the files (ALL THE FILES) flat in the new directory. Naturally, you don't find this failure out until you try to unpack the Pack-N-Go.
ARGGGGGG!!!!
[/rant]
0
Comments
Hey welcome to the wondrous joys of being an AMX Programmer. At least you didn't get the *Hmmmm... Sounds difficult* thought, resulting in the 'not possible' statement.
Regardless I've had this too, I now store everything locally and back it up to the server, or if you're really forced to have your computer's files shared on your network you could consider placing it in the actual path on your pc instead of putting it on a relative path. That will save you a lot of hassle and headaches.
It's not pretty.. but hey what else is new.
Edit: I forgot to mention that you have my sympathy.
Nooo, don't do it!
Just edit the workspace file in a text editor (it's just XML) and replace any definite paths with relative paths.
You can just do a search and replace for with an empty string. If something's in a folder above the project folder then use
Two folders up:
A file in a child folder:
This might come in handy someday and would probably makes e's day if it isn't too late already.
Thanks!
I ended up doing this. I just went in and did it on all my projects It still took some time. But, oh well. It's just time....
I'm still a little baffled in that I do on occasion have to copy my files to my laptop desktop and that doesn't seem to break anything. But, copying to a new server and drive did.
All the rest of the paths were not hard coded. Also, this only causes a problem when a DUET module is present in the project. Any non-duet projects work just fine. I chalked it up to some paths in DUET.
Either way, it seems to be fixed for now. (as 'for now' echos menacingly)
Just had a need to do this and changing the workspace's files directory paths using find/replace is a heck of alot easier than changing each file's path in properties. I used XML Pad to open the .apw but any editor would probably work such as NotePad++.
XMLPad also creates a back up of the original when saving after changes have been made which is kind of cool.