Community
Participate
Working Groups
While other project types in new C project wizard are nicely categorized Xl appear right on the root. And there are categories for the too but they have empty projects... And in C project wizard there are C++ types! There are filters for that (to not show c++ in c project wizard) See scrennshot
Created attachment 171198 [details] screenshot
There is also inconsistency between categorization. If you click on Empty project in Executable category it show XL C/C++ Tool Chain, but XL UPC Tool Chain appear in Executable (XL UPC) category. In should be in Executable category, I don't why it has own category.
Yeah it doesn't make sense to me as to why UPC has its own category either. The other top level entries that are not categorized, I'm not quite sure how to get rid of. That's been an outstanding issue for quite some time. The toolchain specifies the right artifact types, so that's why stuff shows up in the categories as it should, but I'm not sure what makes MBS decide that a given projectType should get a top level entry as well.
(In reply to comment #0) And there are categories for the too but they have > empty projects... And in C project wizard there are C++ types! Sorry this confuses me. The toolchain does both C and C++ so it should show up for both wizards. I'm not sure what you mean by empty projects.
XL* project types are also ignoring checkbox "Show project types and toolchains only if they are supported on the platform". I understand that some users could use them compiling on remote system but it is not good excuse IMHO as that logic could be applied for any project type.
(In reply to comment #5) > XL* project types are also ignoring checkbox "Show project types and toolchains > only if they are supported on the platform". I understand that some users could > use them compiling on remote system but it is not good excuse IMHO as that > logic could be applied for any project type. Unfortunately the build system's idea of target platform for a configuration is only checked against the local system. So depending on what you mark your toolchain as supporting, either you end up with toolchains being hidden when the user might want them shown, or you end up with them shown when the user might want them hidden. There is a Java callback you can provide to determine whether a toolchain is supported, but as I recall, it takes no parameters and hence doesn't really give you any context on which you could interrogate what type of project you're creating, or where you're creating it, in order to properly determine whether to enable the toolchain or not. The callback seems to have been originally created with the scenarion in mind of just checking to see if the compiler is installed via some registry check or checking a known location on the hard drive, as examples. This all being said, there is a Remote XL C/C++ toolchain in PTP that was created after the original XL C/C++ one was created, so we could restrict the target platform for the local one to AIX and Linux/PPC and avoid the particular situation you mention.
(In reply to comment #3) > The other top level entries that are not categorized, I'm not quite sure how to > get rid of. That's been an outstanding issue for quite some time. The > toolchain specifies the right artifact types, so that's why stuff shows up in > the categories as it should, but I'm not sure what makes MBS decide that a given > projectType should get a top level entry as well. Note that there is a preference on page "New CDT Project Wizard"->tab "Wizard Defaults"->Group old-style toolchains to <Others> folder. If this preference were enabled by default it would be less confusing I think.
This bug was assigned and targeted at a now released milestone. As that milestone has now passed, the milestone field has been cleared. If this bug has been fixed, please set the milestone to the version it was fixed in and marked the bug as resolved.
