[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cdt-dev] Problems with setting options in a MBSCustomPage
|
Hmmm... I would tend to think this is one of two things...
1) Maybe ManagedBuildManager doesn't think the build info is dirty, so it's not writing out any changes.
2) Maybe CProjectDescriptionManager.SetProjectDescription() is glitching.
Assuming #1 is not the problem what you describe you are doing should work I would think.
===========================
Chris Recoskie
Team Lead, IBM CDT and RDT
IBM Toronto
Subs <dmsubs@xxxxxxxxxxxxx>
Subs <dmsubs@xxxxxxxxxxxxx>
Sent by: cdt-dev-bounces@xxxxxxxxxxx
03/11/2009 01:10 PM
Please respond to
"CDT General developers list." <cdt-dev@xxxxxxxxxxx> |
|
|
Hi,
I have developed a custom page (MBSCustomPage) that gets added to the C
Project Wizard. I am collecting some additional information that I am
then using to set options in the toolchain (compiler, linker etc). This
is done in the CustomPage Runnable that is called. I apply my changes to
the toolchain and then call:
ManagedBuildManager.saveBuildInfo(project, true);
to save these options.
When the project is built, I can see my options appear in the command
line and the project builds correctly. However, if I close Eclipse and
then reopen, my new settings have disappeared. I can confirm this by
looking in the .cproject file - my changes are not there.
So, it appears that my options are not being stored in the .cproject
file even though they were there in the 'in memory' version.
As an experiment, I added a button to the UI, whose action is to call:
ManagedBuildManager.saveBuildInfo(project, true);
If I press this button after my project has build, I see that sometimes
(but not every time), my settings ARE written to the .cproject.
Any clues as to what I might be doing wrong?
Thanks,
--
Subs
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


