[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cdt-dev] Possible Bug in org.eclipse.cdt.managedbuilder.internal.buildmodel.BuildDescription
|
I have uploaded to skydrive a zipped workspace project that demonstrates the bug 408525 but also a proposed solution to bug 408525, bug 411726 and bug 411728.
Here is the link to the shared skydrive:
I have modified the visual studio plugin.xml to add a new category option in the Compiler tool called Developer testing. This category contains 2 options. The first option : “Test Output Bypass” is an enumerated option that enable/disable the capability to specify a different output location than the default CDT Builder usage.
When enabled a second enumerated option called “Bypass output file (path/name)” specifies the location of the output file from the compilation output. 6 different file locations can be used to test the behavior of the CDT builder. With the standard unpatched CDT code I believe only 1 out of 6 paths will work. With the current patched code the 6 paths yield the expected output file creation at the expected location.
To use the zipped workspace with the current enumerated file locations you need to extract the project to the root of your C drive (Under Windows of course) and keep the same paths specified in the zipped file.
Note that I haven’t a deep knowledge of the CDT architecture yet. Thus the proposed patch is only a template. Also note that I haven’t tried under Linux.
If you have any questions let me know.
Thanks!
Guy
-----cdt-dev-bounces@xxxxxxxxxxx wrote: -----
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
From: Andrew Gvozdev
Sent by: cdt-dev-bounces@xxxxxxxxxxx
Date: 06/24/2013 01:36PM
Subject: Re: [cdt-dev] Possible Bug in org.eclipse.cdt.managedbuilder.internal.buildmodel.BuildDescription
Hi Guy,
In cases like that you would attach a sample plugin exhibiting this behavior.
Thanks,
Andrew
DISCLAIMER:
Privileged and/or Confidential information may be contained in this
message. If you are not the addressee of this message, you may not
copy, use or deliver this message to anyone. In such event, you
should destroy the message and kindly notify the sender by reply
e-mail. It is understood that opinions or conclusions that do not
relate to the official business of the company are neither given
nor endorsed by the company.
Thank You.