For some reason, I can not get the IDE to properly save the "Intermediate
output" and "Final output" directories after I type them in and press [OK].
When I go back into the dialog box, the entries have changed.  I'm using C++
Builder 4.0 (Build 14.4).  Is this a known problem?  Is there a patch?

Thanks,

Tom Dowdell
Intuitive Edge Corp.

: "Tom (Intuitive Edge)" <t...@intuitiveedge.com> wrote:

Final output path - yes. I do not recall a problem with the intermediate
output path.

You might want to have a look at the Borland C++Builder Developer Support
Pages (http://www.borland.com/devsupport/bcppbuilder/) where work-arounds
for at least the Final output path problem have been published.

--
General information:
  * Post to the right group - http://www.borland.com/newsgroups/
    * Do not cross- or multipost
      * Research at http://www.mers.com/searchsite.html

Stefan Hoffmeister - http://www.econos.de/
TeamB - http://www.teamb.com/

I've seen this BUGGY behavior in all C++ Builder IDEs since 1.0. They
continue to insist that they know better what I want. If I type a relative
path into the dialog, C++ Builder had better not change this. There is
usually a good reason for doing so.

Absolute paths DO NOT work in a mult-developer environment since this forces
everyone to have exactly the same configuration. Ideally it would be useful
to allow the use of environment variables in the paths.

Stefan Hoffmeister (TeamB) <Stefan.Hoffmeis...@Econos.de> wrote in message
news:fon48sckqcchvbnad3tkik0rh11j61hckj@4ax.com...

It seems like Borland is trying to force the use of the $(BCB) method. When
you use this in the paths things work a LITTLE better.

My problem is that we use a multi-level directory structure to store our
various packages (*.bpk) files. This allows for a clean hierarchy of code
and works well with CVS. We typically have a DEBUG and RELEASE project file
that build into separate subdirectories, debug  and release, under the
project directory. This method works fine under Visual C++ and somewhat
reasonably under C++ Builder 3.0. C++ Builder 4.0 doesn't seem to work quite
as well.

We also have an automated build system that runs through the directory
structure and build each project. After each project is built the files for
the project are copied to a common area (bin = *.bpl,*.dll,*.exe / lib =
*.bpi,*.lib / include = *.h,*.hpp / source = *.cpp,*.pas).

By hard coding paths in the makefiles or not allowing the use of user
defined environment variables it really makes this process not work well.

If I recall the older Borland C++ compilers and IDEs handled this situation
just fine.

Tom (Intuitive Edge) <t...@intuitiveedge.com> wrote in message
news:85tm6j$ced4@bornews.borland.com...

One thing I've seen done successfully is to mount virtual drives to certain
directories.  Instead of having everything relative, you can say that the
project is always relative to drive z.  Then you can create a virtual drive
z (using subst) that points to any directory you choose.  If your project
configuration is relative to z, then it doesn't matter where the directory
actually lives, just make z point to the appropriate root directory.

Ideally, I completely agree, we shouldn't have to jump through such hoops.

Chris (TeamB)

: "Jeff Stano" <jeffst...@stano.com> wrote:

Switching between absolute and relative paths is a design decision. If you
are unhappy with the design decision, please submit a bug report.

If the design has not been properly implemented, submit a bug report.

--
General information:
  * Post to the right group - http://www.borland.com/newsgroups/
    * Do not cross- or multipost
      * Research at http://www.mers.com/searchsite.html

Stefan Hoffmeister - http://www.econos.de/
TeamB - http://www.teamb.com/

Jeff,

Please take a few moments to go to the bug report page and submit a
complaint. The more people who complain about these issues, the more
likely something will be done about it. You have lots of sympathy and
support, believe me.

Lin
--
Linda K Sherman <lind...@concentric.net>
linsh...@gte.net  www.cti-pro.com   www.dalati.com

BCB has always messed up the directory paths in one way or another. Way back
in BCB3 (or maybe it was BCB1), the IDE converted everything to absolute
paths. In BCB4, its the opposite. Things tend to get converted to relative
paths.

This is a nightmare when dealing with controls. I have some controls in the
c:\raize directory. When I add c:\raize to the path of a project, BCB
converts it to ..\..\raize. Now if I save the project to a new location,
chances are that ..\..\raize won't be valid.

If I type a relative path, BCB should leave it alone. If I type an absolute
path, BCB should also leave it alone. Furthermore, BCB should allow me to
make my own aliases, just like the $(BCB) aliase. This would be awesome in a
multi-user environment.

In the meantime, I do exactly what chris does. I use the dos subst command
to create virtual drives, like z:, x: and so on. When you add a path to a
different drive, BCB usually leaves it alone.

Harold Howe [TeamB]
http://www.bcbdev.com