Hi,

Why are my directories always messd up when I open the project options
dialog box. What can I do against it. Never encountered something so
annoying.

Thanks,
Andr

C++ Builder 4.0

It's a 'feature' (most people call it a bug).

I barely remember some reports about using network paths:
instead of c:\myDir write \\localhost\c\myDir

This is clumsy, I know, but there are not other workaround.

Annoying, stupid, dangerous...

It is in C++ Builder 5.0, too.

Oscar.

news:9k9o2a$gpl$06$1@news.t-online.com...

The problem is that Builder assumes that all paths are relative, so that
moving your source to a different directory shouldn't require you to mess
with the path settings.  It's not smart enough to figure out which parts
actually are relative, so it just assumes everything on the same drive...
which is COMPLETELY wrong if your components live on the same drive, which
is often the case.

The 'solution' (read: workaround) I use is to map drives to directories
using the DOS subst command.  I have an S: drive where my source code lives
(mapped to C:\Source), and a P: drive for my packages (mapped to
S:\Source\Components\Packages), etc.  This also helps with moving source
code between work and home, or between computers at work, where source code
is often kept on different drives, etc.  As far as builder is concerned it's
always P: and S: drives.

And yes, this DOES work on WinNT/2K.  On my dev machine I have a batch file
that runs on startup to map the drives for me.  It looks something like
this:

--batch file below--
@echo off
subst P: e:\source\components\packages
subst S: s:\source
--end batch file--

--
Corey Murtagh
The Electric Monk
"Quidquid latine dictum sit, altum viditur."

Good idea. Implemented it and it works for me :-)

Boy was that an annoyance, can't tell you how often I swore at my computer.

Thanks, Andr

Andr,

If you use UNC paths directories are left alone eg:

  \\MyMachine\DriveC\Source

Note that the share for the drive (in this case 'DriveC') must have
read/write access.

Andrue Cope
[Bicester, UK]

Andr,

Use UNC paths - the IDE leaves them alone. The only caveat is that I
don't know if UNC paths are available w/out network support.

FWIW I use:

  \\VIKING\HD_D\VFS\Version5\Cmd.dll\output\
or
  \\PELL\HD_C\VFS\LIB1\output

and they stay that way.

Actually there is one other caveat - you must define a share for that
drive and it must give write permission.

Andrue Cope
[Bicester, UK]