Log On
Embarcadero Home
Watch, Follow, &
Connect with Us
Share This
QualityCentral
Communities
Articles
Blogs
Resources
Downloads
Help
QualityCentral
Delphi-BCB
IDE
Project Management
Build Events
Project Manager
Project Options
Project Source
Virtual Folders
You are not logged in.
Help
Print
Public Report
Report From:
Delphi-BCB/IDE/Project Management/Project Options
[ Add a report in this area ]
Report #:
90049
Status:
Need Feedback
Manage include and library paths
Project:
C++Builder
Build #:
12.0.3210.17555
Version:
12.0
Submitted By:
Fraser Ross
Report Type:
Issue
Date Reported:
12/1/2010 4:32:28 AM
Severity:
Commonly encountered problem
Last Updated:
12/7/2010 6:46:13 AM
Platform:
All platforms
Internal Tracking #:
Resolution:
Need More Info
(Resolution Comments)
Resolved in Build:
:
None
Duplicate of:
None
Voting and Rating
Overall Rating:
No Ratings Yet
0.00 out of 5
Total Votes:
None
Description
When the option 'Manage include and library paths' is on entries always appear in the global 'Directories and Conditionals'.
It says in the help that they will be added to the appropriate include path options. When I add a 'C++ Builder unit' I would expect an entry under the 'C++ Compiler' options. 'Resource Compiler' and 'Turbo Assembler' also have include path options that are not used.
Fraser.
Steps to Reproduce:
None
Workarounds
None
Attachment
None
Comments
Fraser Ross at 12/31/2010 7:11:34 AM
-
It is quite easy to see what directory options have been used when something is added to a project. I do not know what more information I can give.
I have noticed that the global directory option must be used for forms or else the linker will not find a dfm file.
I still feel that this request should be accepted because it will make project options considerably more organised.
Tomohiro Takahashi at 1/1/2011 12:28:04 AM
-
Did you read 'Resolution comment' from Leo?
<<<<<<<<<<<<<<<
This is "As Designed". Is it causing some kind of problem for you?
The PM adds these to the global Directories and Conditionals so that they will be available to the C++ compiler, the Resource Compiler and the Assembler. This seems appropriate for an automatic facility that is never actually going to make intelligent choices for each project but should be expected to err on the side of being too general rather than too specific.
Personally, I find it much more annoying that it keeps adding paths like ..\ and D:\LIB\ (when I already hve d:\Lib\).
>>>>>>>>>>>>>>>
View Your Reports
Search
Server Response from: ETNACODE01
Developer Tools
Blackfish SQL
C++Builder
Delphi
FireMonkey
Prism
InterBase
JBuilder
J Optimizer
HTML5 Builder
3rdRail & TurboRuby
Database Tools
Change Manager
DBArtisan
DB Optimizer
ER/Studio
Performance Center
Rapid SQL
Technical Articles
Tutorials
White Papers
Press Releases
Newsletters
Add Content (GetPublished)
Audio
Audio & Video
Video
Bugs & Suggestions (QualityCentral)
Discussion Forums
Examples (CodeCentral)
Tags
Technology Partners
Downloads
Free Trials
Registered User Downloads
Beta Programs
Add Content (GetPublished)
Articles
Blogs
Bugs & Suggestions (QualityCentral)
Discussion Forums
Examples (CodeCentral)
Member Services
About
Connect with Us