QualityCentral

Public Report

Report From: C++BuilderX/IDE/Object gallery [ Add a report in this area ]

Report #: 6755

Status: Open

Project wizards should provide easy setting of multi/single threaded and static/dynamic RTL options

Project: C++BuilderX/BC++ 2005

Build #: 1.0.1.103

Version: 1.5

Submitted By: Russell Hind

Report Type: New Feature Request

Date Reported: 1/6/2004 3:48:31 AM

Severity: Commonly encountered problem

Last Updated: 3/20/2012 2:24:39 AM

Platform: All platforms

Internal Tracking #: 192857

Resolution: None (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

The project wizards should all provide common options for choosing multi-threaded/single-threaded projects and also for static/dynamic linking of the RTL so this can be set when the project is created, rather than having to search through linker options and compiler options to change the libraries and such manually. It is currently very awkward to do this.

Steps to Reproduce:

None

Workarounds

None

Attachment

None

Comments

Russell Hind at 1/6/2004 3:48:47 AM -

Not sure if this is correct area, but couldn't find one for project wizards. Perhaps one should be created?

Robert Ehteshamzadeh at 1/7/2004 10:43:19 AM -

changed area to Object Gallery.

Opened and added to internal tracking system.

Duane Hebert at 1/9/2004 1:46:01 PM -

There should be a way to keep the path settings between different
build types as well. It's annoying to have to redo them when changing
to a release build. In my case, most paths don't change between
builds

Russell Hind at 1/12/2004 3:52:01 AM -

I think a new report should be opened for this as it is a new request. I've been thinking about this for a while but haven't posted a report until I made sure I'd come up with a way to do this. My current thinking is to have a tree structure for build configurations e.g.

Base Configuration
|
|--Debug Build
|
|--Release Build

That way, you set common options (libraries, paths etc) in Base Configuration, and then over-ride compiler settings etc in the appropriate build (define NDEBUG, turn on optimisations in release build etc). I think it would need the dreaded 'merge' option for it to be effective, but I think the 'Base Configuration' would be the default project properties (i.e. if merge is checked) but you can then alter it to have changes made applicable to all sub builds

Cheers

Russell

Developer Tools

Database Tools