Watch, Follow, &
Connect with Us

QualityCentral

Public Report
Report From: Delphi-BCB/IDE/Project Management/Project Manager    [ Add a report in this area ]  
Report #:  88572   Status: Closed
Optionset not applied to a build configuration
Project:  Delphi Build #:  15.0.3890.34076
Version:    15.0 Submitted By:   Marek Bojarski
Report Type:  Basic functionality failure Date Reported:  10/1/2010 1:57:37 PM
Severity:    Serious / Highly visible problem Last Updated: 3/20/2012 2:24:39 AM
Platform:    All versions Internal Tracking #:   280670
Resolution: Fixed (Resolution Comments) Resolved in Build: : Update 1
Duplicate of:  None
Voting and Rating
Overall Rating: No Ratings Yet
0.00 out of 5
Total Votes: None
Description
When the build configuration does not contain any changes from the base one, the optionset applied to it by reference doesent apply its settings to the project. Also, saving the project doesn't save the reference to the optionset.
Steps to Reproduce:
1) create vcl forms application
2) add build configuration called "Test", based on the base one.
3) create a new opionset for this configuration.
4) edit an optionset and define conditional "TEST"
5) you may see in "project options" that "TEST" is defined.
6) add oncreate event handler for the form and insert into it:
{$IFDEF TEST}
bla bla bla
{$ENDIF}
7) compile the project, it will compile and run fine. (should not !)
8) save project, close and reopen
9) the "Test" build configuration doesn't have assigned optionset as a reference (should have!)

Workaround:

Define other conditional in "Test" configuration. From that point everything works as expected.
Workarounds
Workaround:

Define other conditional in "Test" configuration. From that point everything works as expected.
Attachment
None
Comments

Tomohiro Takahashi at 11/14/2010 5:00:20 PM -
This issue is fixed in Update 1.
If possible, please retest your issue with Update 1.

Marek Bojarski at 11/20/2010 5:18:05 AM -
Well, it seems to work now.

Compilation works as expected. There is a moment when Error Insight doesn't show an error in "bla bla bla" after defining "TEST" in optionset, but typing anything in the editor underlines "bla bla bla" as an error.
AFAIR it is so for any conditionals change, so at least it is "as it always was".

Thanks for correcting this issue.

Server Response from: ETNACODE01

Copyright© 1994 - 2013 Embarcadero Technologies, Inc. All rights reserved.