A follow-up to my own question:
The introduction of the build-console logging to file is the reason why
the UI no longer activates the build consoles for non-C/C++ projects.
The BuildConsolePage::setProject(...) method rejects projects that
don't have a C project description, because it needs the active
configuration name to look up the preference for toggling the save
action button.
If I change this to set the project but ignore the button (disabling it
for safety) for my non-C project, then everything pretty much works as
before.
Of course, I'd like my projects to be able to take advantage of the new
logging capability. I'm curious as to why the logging preference is
implemented on a per-config basis: it doesn't really feel like part of
the build configuration, but an orthogonal concept. If it were
implemented per-project, then it could also work for non-C projects.
Or even, if I can work up a patch that implements a single preference
setting for non-C projects, I should like to contribute that.
Of course, given this, it would also be necessary for future
enhancements to the build console to always account for the non-C
project use cases :-)
Cheers,
Christian
On 24/03/10 09:55 AM, Christian Damus wrote:
Hi,
Since adopting CDT 7.0 M6, I find that something that worked well in
past releases and up to 7.0 M5 no longer does: build consoles for
non-C/C++ projects. See, this per-project console UI is so handy, that
builders that I have for projects of non-C/C++ nature have enjoyed
using it.
Oddly, the APIs that provide consoles and let me write text to them
still seem to work. It's just the console UI that doesn't show the
consoles for non-C/C++ projects. So, it seems that there's either a
bug in the UI not showing all consoles, or there's a bug in the API
making them available.
Ideally, of course, it would just work as it always did.
Is this a restriction that was introduced deliberately? Is it
something that was never intended to work? Should I raise a bug?
Thanks,
Christian
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
|