Watch, Follow, &
Connect with Us
Public Report
Report From: Delphi-BCB/IDE/Project Management    [ Add a report in this area ]  
Report #:  104430   Status: Need Feedback
Custom Manifest Relative Pathing
Project:  Delphi Build #:  16.0.4429.46931
Version:    16.4 Submitted By:   Lance Rasmussen
Report Type:  New Feature Request Date Reported:  3/26/2012 8:09:37 AM
Severity:    Infrequently encountered problem Last Updated: 3/30/2012 10:41:29 PM
Platform:    All versions Internal Tracking #:  
Resolution: Cannot Reproduce (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
Now that XE2 introduces the ability to point to a custom manifest file instead of adding a compiler inclusion as a resource (Thank you!!!), I've found that this feature needs a slight tweak to be most effective.

Currently the custom manifest is set as an absolute path, which can be a problem if the project is resaved as a new project in a different directory.

There should be an option to dictate if that path is relative to the project file or absolute as it stands now.  Under the hood, if the compiler needs absolute pathing, it can be translated at that point.
Steps to Reproduce:
Create a VCL project and point to a custom manifest file in the project directory.
Save project.
Save project as a new project in a different directory.  The custom manifest points to the original directory.
Workarounds
You must edit the project options for each build/target combination to point to the correct manifest and location.
Attachment
None
Comments

Teodor Nacu at 3/30/2012 6:39:56 AM -
Hi,
I am not able to reproduce this.
If the manifest is saved as to the same location of the new project location, the new path will appear in the Project Options.
Could you provide a sample project and clearer stepts to understand the issue, please?

Thanks,
Teodor Nacu
SDET - IDE, QA RAD Studio

David Zimmerman at 5/1/2012 7:05:14 AM -
this is problem if the Project is built somewhere other than the developer's machine.  We build on a separate build computer and it extracts the source in directories of its owen.  The absolute path of does not match.

Server Response from: ETNACODE01