Watch, Follow, &
Connect with Us
Public Report
Report From: C++BuilderX/IDE/Toolset    [ Add a report in this area ]  
Report #:  6259   Status: Open
Building your own toolsets - design limitation
Project:  C++BuilderX/BC++ 2005 Build #:  1.0.0.1786
Version:    1.0 Submitted By:   Andrey Isaev
Report Type:  Issue Date Reported:  10/22/2003 6:09:50 AM
Severity:    Critical / Show Stopper Last Updated: 3/20/2012 2:24:39 AM
Platform:    All platforms Internal Tracking #:   184746
Resolution: None (Resolution Comments) Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: (4 Total Ratings)
4.50 out of 5
Total Votes: 4
Description
When you create your own toolset you will encounter one serious problem - you are unable to create tool that takes one input but produces several outputs. Only one output is allowed. However, when you work with tools for creating Palm OS applications, you have to use tools that have mutiply out put - they produce several files from one.

Main problem is that you should manually fill in options for your tools explicitly stating directories and filenames for your additional output.

However there is another problem - you have no access from within toolset default configuration to macros like $(BuildDirectory) or others like this. They are available only from tools you created from IDE. Thus, tou should do ugly things like writing "windows\Default Build\code0000.bin" as a parameter hoping that directory won't be changed in future.

This limitation makes almost absolete possibility to use BuilderX as IDE for external tools.
Steps to Reproduce:
None
Workarounds
None
Attachment
None
Comments

Jennifer-Ashley Kuiper at 10/22/2003 10:09:40 AM -
Add your comments here.

George Mealer at 10/31/2003 11:55:22 AM -
Talked to the R&D engineer in charge of the area.

You're basically right, on all counts.  Note that you can have multiple project-wide tools in a project.  See how we implemented MinGW's import library as an example; we have a toolset for generating the def file and another toolset for generating the lib file.  The import library project wizard creates a project that has both toolsets enabled, and thus, creates two outputs.  This won't cover you in all cases, but it covers you in some.

As for the cases that aren't covered and the macro issue, we're looking to improve this area in the next version--we know the current system can't handle all of the possibilities.

George Mealer at 10/31/2003 11:56:06 AM -
To correct, where I say "toolset" above, I meant ".tool file".  Sorry about that!

George Mealer at 10/29/2003 5:51:19 PM -
Andre:

I'm passing this on to R&D for comment.  I'll post here once I have a resolution.

In the meantime, this has been promoted to our internal bug-tracking system.

Server Response from: ETNACODE01