Eclipse Community Forums: C / C++ IDE (CDT) » Programatically create a project?

Search

Help

Login

Home » Language IDEs » C / C++ IDE (CDT) » Programatically create a project?

Show: Today's Messages :: Show Polls :: Message Navigator

Switch to threaded view of this topic

Create a new topic

Submit Reply

Programatically create a project? [message #227953]

Sat, 13 December 2008 14:04

Bryan Hunt is currently offline

Friend

Messages: 366
Registered: July 2009

Senior Member

Is there a section of code I could lift from a unit test that
programatically creates a C / C++ project?

I'm using the CDT launcher, and I need to write a unit test that uses
the launcher. In order for the launcher to be happy, I must have a
valid C / C++ project. I don't need to create an executable, just
enough for the launcher to consider it a valid project.

Bryan

Report message to a moderator

Re: Programatically create a project? [message #227977 is a reply to message #227953]

Sat, 13 December 2008 17:54

Andrew Gvozdev is currently offline

Friend

Messages: 257
Registered: July 2009

Senior Member

Bryan Hunt wrote:

> Is there a section of code I could lift from a unit test that
> programatically creates a C / C++ project?

> I'm using the CDT launcher, and I need to write a unit test that uses
> the launcher. In order for the launcher to be happy, I must have a
> valid C / C++ project. I don't need to create an executable, just
> enough for the launcher to consider it a valid project.

I suppose the most accurate code would be C/C++ New Project Wizard code. I
also referred to org.eclipse.cdt.projectmodel.tests in
org.eclipse.cdt.managedbuilder.core.tests. Here is an excerpt of the code
I am using for my tests, this would create Standard Makefile project:

// Create and persist Standard Makefile project
{
// Create model project and accompanied project description
IWorkspace workspace = ResourcesPlugin.getWorkspace();
IWorkspaceRoot root = workspace.getRoot();

IProject newProjectHandle = root.getProject(projectName);
Assert.assertNotNull(newProjectHandle);
Assert.assertFalse(newProjectHandle.exists());

IProjectDescription description =
workspace.newProjectDescription(newProjectHandle.getName());
IProject project =
CCorePlugin.getDefault().createCDTProject(description, newProjectHandle,
new NullProgressMonitor());
Assert.assertTrue(newProjectHandle.isOpen());

ICProjectDescriptionManager mngr =
CoreModel.getDefault().getProjectDescriptionManager();
ICProjectDescription des = mngr.createProjectDescription(project,
false);
ManagedProject mProj = new ManagedProject(des);

Configuration cfg = new Configuration(mProj, null,
"your.configuration.id", "YourConfigurationName");

IBuilder bld = cfg.getEditableBuilder();
Assert.assertNotNull(bld);
Assert.assertFalse(bld.isInternalBuilder());

bld.setManagedBuildOn(false);

CConfigurationData data = cfg.getConfigurationData();
Assert.assertNotNull(data);
des.createConfiguration(ManagedBuildManager.CFG_DATA_PROVIDE R_ID, data);

// Persist the project description
mngr.setProjectDescription(project, des);

project.close(null);
}

Thanks,
Andrew

> Bryan

Report message to a moderator

Re: Programatically create a project? [message #228143 is a reply to message #227977]

Thu, 18 December 2008 02:36

Bryan Hunt is currently offline

Friend

Messages: 366
Registered: July 2009

Senior Member

Andrew,

Thanks for the info. I was able to use this code to get my unit test
working. :)

Bryan

On 2008-12-13 11:54:11 -0600, angvoz.dev@gmail.com (Andrew Gvozdev) said:

> Bryan Hunt wrote:
>
>> Is there a section of code I could lift from a unit test that
>> programatically creates a C / C++ project?
>
>> I'm using the CDT launcher, and I need to write a unit test that uses
>> the launcher. In order for the launcher to be happy, I must have a
>> valid C / C++ project. I don't need to create an executable, just
>> enough for the launcher to consider it a valid project.
>
> I suppose the most accurate code would be C/C++ New Project Wizard
> code. I also referred to org.eclipse.cdt.projectmodel.tests in
> org.eclipse.cdt.managedbuilder.core.tests. Here is an excerpt of the
> code I am using for my tests, this would create Standard Makefile
> project:
>
> // Create and persist Standard Makefile project
> {
> // Create model project and accompanied project description
> IWorkspace workspace = ResourcesPlugin.getWorkspace();
> IWorkspaceRoot root = workspace.getRoot();
>
> IProject newProjectHandle = root.getProject(projectName);
> Assert.assertNotNull(newProjectHandle);
> Assert.assertFalse(newProjectHandle.exists());
>
> IProjectDescription description =
> workspace.newProjectDescription(newProjectHandle.getName());
> IProject project =
> CCorePlugin.getDefault().createCDTProject(description,
> newProjectHandle, new NullProgressMonitor());
> Assert.assertTrue(newProjectHandle.isOpen());
>
> ICProjectDescriptionManager mngr =
> CoreModel.getDefault().getProjectDescriptionManager();
> ICProjectDescription des = mngr.createProjectDescription(project, false);
> ManagedProject mProj = new ManagedProject(des);
>
> Configuration cfg = new Configuration(mProj, null,
> "your.configuration.id", "YourConfigurationName");
>
> IBuilder bld = cfg.getEditableBuilder();
> Assert.assertNotNull(bld);
> Assert.assertFalse(bld.isInternalBuilder());
>
> bld.setManagedBuildOn(false);
>
> CConfigurationData data = cfg.getConfigurationData();
> Assert.assertNotNull(data);
> des.createConfiguration(ManagedBuildManager.CFG_DATA_PROVIDE R_ID, data);
>
> // Persist the project description
> mngr.setProjectDescription(project, des);
>
> project.close(null);
> }
>
>
> Thanks,
> Andrew
>
>> Bryan

Report message to a moderator

Re: Programatically create a project? [message #229922 is a reply to message #227977]

Tue, 03 February 2009 14:02

Andrew Gvozdev is currently offline

Friend

Messages: 257
Registered: July 2009

Senior Member

For the cross-reference, I posted also how to create managed project
programatically in this thread:
http://www.nabble.com/Programatically-create-CDT-project-td2 1096039.html

Andrew Gvozdev wrote:
> Bryan Hunt wrote:
>> Is there a section of code I could lift from a unit test that
>> programatically creates a C / C++ project?
>> I'm using the CDT launcher, and I need to write a unit test that uses
>> the launcher. In order for the launcher to be happy, I must have a
>> valid C / C++ project. I don't need to create an executable, just
>> enough for the launcher to consider it a valid project.

> I suppose the most accurate code would be C/C++ New Project Wizard code. I
> also referred to org.eclipse.cdt.projectmodel.tests in
> org.eclipse.cdt.managedbuilder.core.tests. Here is an excerpt of the code
> I am using for my tests, this would create Standard Makefile project:

> // Create and persist Standard Makefile project
> {
> // Create model project and accompanied project description
> IWorkspace workspace = ResourcesPlugin.getWorkspace();
> IWorkspaceRoot root = workspace.getRoot();

> IProject newProjectHandle = root.getProject(projectName);
> Assert.assertNotNull(newProjectHandle);
> Assert.assertFalse(newProjectHandle.exists());

> IProjectDescription description =
> workspace.newProjectDescription(newProjectHandle.getName());
> IProject project =
> CCorePlugin.getDefault().createCDTProject(description, newProjectHandle,
> new NullProgressMonitor());
> Assert.assertTrue(newProjectHandle.isOpen());

> ICProjectDescriptionManager mngr =
> CoreModel.getDefault().getProjectDescriptionManager();
> ICProjectDescription des = mngr.createProjectDescription(project,
> false);
> ManagedProject mProj = new ManagedProject(des);

> Configuration cfg = new Configuration(mProj, null,
> "your.configuration.id", "YourConfigurationName");

> IBuilder bld = cfg.getEditableBuilder();
> Assert.assertNotNull(bld);
> Assert.assertFalse(bld.isInternalBuilder());

> bld.setManagedBuildOn(false);

> CConfigurationData data = cfg.getConfigurationData();
> Assert.assertNotNull(data);
> des.createConfiguration(ManagedBuildManager.CFG_DATA_PROVIDE R_ID, data);

> // Persist the project description
> mngr.setProjectDescription(project, des);

> project.close(null);
> }

> Thanks,
> Andrew

>> Bryan

Report message to a moderator

Re: Programatically create a project? [message #231197 is a reply to message #227977]

Thu, 05 March 2009 14:19

John Moule is currently offline

Friend

Messages: 13
Registered: July 2009

Junior Member

Hi,

I've used the code you posted successfully (thanks a lot), but I also want
to use a specific toolchain when the project is created. The toolchain (a
slightly adapted GNU one) exists in my toolset plugin and I can
successfully create a project with this toolchain using the new project
wizard. But now I'd like the ability to do this programmatically. I'd like
to specify myToolChain like this:

...
Configuration cfg = new Configuration(mProj, myToolChain,
"com.xyz.microtoolset.toolchain.gnu.base", "XYZ Micro Toolset");
...

But I can't figure how to create the myToolChain object easily. I've
looked at the constructors in
org.eclipse.cdt.managedbuilder.internal.core.ToolChain but I don't
understand how to specify the various params they require using what I've
got.

Any tips would be gratefully received.

cheers john

Andrew Gvozdev wrote:

> Bryan Hunt wrote:

>> Is there a section of code I could lift from a unit test that
>> programatically creates a C / C++ project?

>> I'm using the CDT launcher, and I need to write a unit test that uses
>> the launcher. In order for the launcher to be happy, I must have a
>> valid C / C++ project. I don't need to create an executable, just
>> enough for the launcher to consider it a valid project.

> I suppose the most accurate code would be C/C++ New Project Wizard code. I
> also referred to org.eclipse.cdt.projectmodel.tests in
> org.eclipse.cdt.managedbuilder.core.tests. Here is an excerpt of the code
> I am using for my tests, this would create Standard Makefile project:

> // Create and persist Standard Makefile project
> {
> // Create model project and accompanied project description
> IWorkspace workspace = ResourcesPlugin.getWorkspace();
> IWorkspaceRoot root = workspace.getRoot();

> IProject newProjectHandle = root.getProject(projectName);
> Assert.assertNotNull(newProjectHandle);
> Assert.assertFalse(newProjectHandle.exists());

> IProjectDescription description =
> workspace.newProjectDescription(newProjectHandle.getName());
> IProject project =
> CCorePlugin.getDefault().createCDTProject(description, newProjectHandle,
> new NullProgressMonitor());
> Assert.assertTrue(newProjectHandle.isOpen());

> ICProjectDescriptionManager mngr =
> CoreModel.getDefault().getProjectDescriptionManager();
> ICProjectDescription des = mngr.createProjectDescription(project,
> false);
> ManagedProject mProj = new ManagedProject(des);

> Configuration cfg = new Configuration(mProj, null,
> "your.configuration.id", "YourConfigurationName");

> IBuilder bld = cfg.getEditableBuilder();
> Assert.assertNotNull(bld);
> Assert.assertFalse(bld.isInternalBuilder());

> bld.setManagedBuildOn(false);

> CConfigurationData data = cfg.getConfigurationData();
> Assert.assertNotNull(data);
> des.createConfiguration(ManagedBuildManager.CFG_DATA_PROVIDE R_ID, data);

> // Persist the project description
> mngr.setProjectDescription(project, des);

> project.close(null);
> }

> Thanks,
> Andrew

>> Bryan

Report message to a moderator

Re: Programatically create a project? [message #231220 is a reply to message #231197]

Fri, 06 March 2009 11:55

John Moule is currently offline

Friend

Messages: 13
Registered: July 2009

Junior Member

Hi,

... I've sussed it. I struck gold in
org.eclipse.cdt.managedbuilder.core.ManagedBuildManager; its full of
useful statics. So to get my toolchain that I'm interested in I use the
following (note error checks not included!):

IToolChain[] tcs = ManagedBuildManager.getRealToolChains();
ToolChain tc=null;
for (int i=0; i<tcs.length; i++) {
if(tcs[i].getName().contains("XYZ Micro Toolset")) {
tc = (ToolChain) tcs[i];
break;
}
}
Configuration cfg = new Configuration(mProj, tc,
"com.xyz.microtoolset.toolchain.gnu.base", "XYZ Micro Toolset");

cheers john

John Moule wrote:

> Hi,

> I've used the code you posted successfully (thanks a lot), but I also want
> to use a specific toolchain when the project is created. The toolchain (a
> slightly adapted GNU one) exists in my toolset plugin and I can
> successfully create a project with this toolchain using the new project
> wizard. But now I'd like the ability to do this programmatically. I'd like
> to specify myToolChain like this:

> ...
> Configuration cfg = new Configuration(mProj, myToolChain,
> "com.xyz.microtoolset.toolchain.gnu.base", "XYZ Micro Toolset");
> ...

> But I can't figure how to create the myToolChain object easily. I've
> looked at the constructors in
> org.eclipse.cdt.managedbuilder.internal.core.ToolChain but I don't
> understand how to specify the various params they require using what I've
> got.

> Any tips would be gratefully received.

> cheers john

> Andrew Gvozdev wrote:

>> Bryan Hunt wrote:

>>> Is there a section of code I could lift from a unit test that
>>> programatically creates a C / C++ project?

>>> I'm using the CDT launcher, and I need to write a unit test that uses
>>> the launcher. In order for the launcher to be happy, I must have a
>>> valid C / C++ project. I don't need to create an executable, just
>>> enough for the launcher to consider it a valid project.

>> I suppose the most accurate code would be C/C++ New Project Wizard code. I
>> also referred to org.eclipse.cdt.projectmodel.tests in
>> org.eclipse.cdt.managedbuilder.core.tests. Here is an excerpt of the code
>> I am using for my tests, this would create Standard Makefile project:

>> // Create and persist Standard Makefile project
>> {
>> // Create model project and accompanied project description
>> IWorkspace workspace = ResourcesPlugin.getWorkspace();
>> IWorkspaceRoot root = workspace.getRoot();

>> IProject newProjectHandle = root.getProject(projectName);
>> Assert.assertNotNull(newProjectHandle);
>> Assert.assertFalse(newProjectHandle.exists());

>> IProjectDescription description =
>> workspace.newProjectDescription(newProjectHandle.getName());
>> IProject project =
>> CCorePlugin.getDefault().createCDTProject(description, newProjectHandle,
>> new NullProgressMonitor());
>> Assert.assertTrue(newProjectHandle.isOpen());

>> ICProjectDescriptionManager mngr =
>> CoreModel.getDefault().getProjectDescriptionManager();
>> ICProjectDescription des = mngr.createProjectDescription(project,
>> false);
>> ManagedProject mProj = new ManagedProject(des);

>> Configuration cfg = new Configuration(mProj, null,
>> "your.configuration.id", "YourConfigurationName");

>> IBuilder bld = cfg.getEditableBuilder();
>> Assert.assertNotNull(bld);
>> Assert.assertFalse(bld.isInternalBuilder());

>> bld.setManagedBuildOn(false);

>> CConfigurationData data = cfg.getConfigurationData();
>> Assert.assertNotNull(data);
>> des.createConfiguration(ManagedBuildManager.CFG_DATA_PROVIDE R_ID, data);

>> // Persist the project description
>> mngr.setProjectDescription(project, des);

>> project.close(null);
>> }

>> Thanks,
>> Andrew

>>> Bryan

Report message to a moderator

Re: Programatically create a project? [message #496036 is a reply to message #231220]

Sat, 07 November 2009 13:22

Yevgeny Shifrin is currently offline

Yevgeny Shifrin

Friend

Messages: 208
Registered: July 2009

Senior Member

Hi,

I am writing eclipse plug-in, in which I would like to create C++ project. I took the code from this post.
Unfortunately I am not able to find correct imports for "ManagedProject" and "Configuration". Eclipse suggests the following imports:
import org.eclipse.cdt.managedbuilder.internal.core.ManagedProject;
import org.eclipse.cdt.managedbuilder.internal.core.Configuration;

And then I have warnings for both imports:
Discouraged access: The type Configuration / ManagedProject is not accessible due to restriction on required library E:\Professional\eclipse_dev\eclipse3.5_rcp\eclipse\plugins
\org.eclipse.cdt.managedbuilder.core_6.0.0.200909110608.jar

Any idea how to solve it, which import to use? In plugin.xml I added org.eclipse.cdt.managedbuilder.core(6.0.0) dependency.

Thanks,
Yevgeny

Report message to a moderator

Re: Programatically create a project? [message #496048 is a reply to message #496036]

Sat, 07 November 2009 14:46

Derek is currently offline

Friend

Messages: 60
Registered: July 2009

Member

On 07/11/2009 13:22, Yevgeny Shifrin wrote:
> Hi,
>
> I am writing eclipse plug-in, in which I would like to create C++
> project. I took the code from this post. Unfortunately I am not able to
> find correct imports for "ManagedProject" and "Configuration". Eclipse
> suggests the following imports:
> import org.eclipse.cdt.managedbuilder.internal.core.ManagedProject;
> import org.eclipse.cdt.managedbuilder.internal.core.Configuration;
>
> And then I have warnings for both imports:
> Discouraged access: The type Configuration / ManagedProject is not
> accessible due to restriction on required library
> E:\Professional\eclipse_dev\eclipse3.5_rcp\eclipse\plugins
> \org.eclipse.cdt.managedbuilder.core_6.0.0.200909110608.jar
>
> Any idea how to solve it, which import to use? In plugin.xml I added
> org.eclipse.cdt.managedbuilder.core(6.0.0) dependency.
>
> Thanks,
> Yevgeny
Try using IManagedProject and IConfiguration

--
Derek

Report message to a moderator

Re: Programatically create a project? [message #496689 is a reply to message #496048]

Tue, 10 November 2009 23:07

Yevgeny Shifrin is currently offline

Yevgeny Shifrin

Friend

Messages: 208
Registered: July 2009

Senior Member

Hi Derek,

Thank you for trying to help. I am not sure I understand your suggestion.

I changed the code from:
ManagedProject mProj = new ManagedProject(des);
Configuration cfg = new Configuration( mProj,null,"your.configuration.id", "YourConfigurationName");
to:
IManagedProject mProj = new ManagedProject(des);
IConfiguration cfg = new Configuration( mProj,null,"your.configuration.id", "YourConfigurationName");

I still need to allocate ManagedProject and Configuration objects so they still must be added to the import. Am I missing something?

Thanks,
Yevgeny

Report message to a moderator

Re: Programatically create a project? [message #505072 is a reply to message #496689]

Sat, 26 December 2009 11:18

Yevgeny Shifrin is currently offline

Yevgeny Shifrin

Friend

Messages: 208
Registered: July 2009

Senior Member

Hi,

Does anyone knows how to solve this issue? I am trying to create Eclipse C++ project without having any warnings about using internal packages. I guess I am using CDT APIs in a wrong way. Any ideas?

Thanks,
Yevgeny

Report message to a moderator

Re: Programatically create a project? [message #505137 is a reply to message #505072]

Sun, 27 December 2009 15:23

Andrew Gvozdev is currently offline

Friend

Messages: 257
Registered: July 2009

Senior Member

I have just added another method in ResourceHelper of cdt.core.tests plugin to create project with configurations. Looks API clean. Take a look. Also added a reference to it in http:// wiki.eclipse.org/CDT/Developer/FAQ#How_can_I_programmaticall y_create_a_new_CDT_project.3F

One characteristic of project model design is that configuration is not allowed be created from scratch outside of MBS plugins but it can be copied from another - including those defined by plugins' project type (as extensions).

Andrew

Report message to a moderator

Re: Programatically create a project? [message #505766 is a reply to message #505137]

Mon, 04 January 2010 20:23

Richard is currently offline

Friend

Messages: 26
Registered: July 2009

Junior Member

Andrew or Yevgeny.
Sorry I am using this posting as a way to communicate with you. I am having problems with Eclipse 5.0 and Yevgeny has helped me in the past. I can not quite figure out how I can get any other help on this forum. I have posted a problem I am having and have had no replies or solutions. I posted the problem on 11/23/09. I need to get it solved to do my job. It is message #499716. I will not put the details in here. If you have any ideas for how I can get replies/solutions to my Eclipse problems in the future, please let me know.

Sincerely, Rick Pollgreen

Report message to a moderator

Re: Programatically create a project? [message #506314 is a reply to message #505766]

Wed, 06 January 2010 23:01

Yevgeny Shifrin is currently offline

Yevgeny Shifrin

Friend

Messages: 208
Registered: July 2009

Senior Member

Hi Rick,

I saw that you found a solution for your issue. From my experience, most of the time questions are answered in this forum, in case someone has a solution. Have a great day Smile

Smile

Yevgeny

[Updated on: Wed, 06 January 2010 23:02]

Report message to a moderator

Re: Programatically create a project? [message #513237 is a reply to message #505072]

Tue, 09 February 2010 13:38

Eugene K is currently offline

Friend

Messages: 11
Registered: February 2010

Junior Member

Hi Yevgeny,

Did you ever solve the import problem with Configuration object? I face the same problem and can't figure it out.

I'd appreciate any help.

Thanks,
Eugene

Report message to a moderator

Re: Programatically create a project? [message #513318 is a reply to message #227953]

Tue, 09 February 2010 18:19

Andrew Gvozdev is currently offline

Friend

Messages: 257
Registered: July 2009

Senior Member

nm

[Updated on: Tue, 09 February 2010 18:24]

Report message to a moderator

Re: Programatically create a project? [message #513953 is a reply to message #513237]

Thu, 11 February 2010 18:57

Yevgeny Shifrin is currently offline

Yevgeny Shifrin

Friend

Messages: 208
Registered: July 2009

Senior Member

Hi Eugene,

Unfortunately I did not have time working on this issue. I am working on this when I have time. Andrew added a link which suggested how to solve this issue. According to his post you should use the org.eclipse.cdt.core.externalSettingsProvider extension point.

The external Settings Provider extension point can be used to register a build settings provider and have it dynamically called back at your own control. You can use this to contribute paths to your build configuration, making decisions at runtime on what should be added.

1. Use the org.eclipse.cdt.core.externalSettingsProvider extension point, give it an "ID"
2. Create a 'provider' element pointing at a class that extends CExternalSettingProvider
3. Register the class on your CDT projects by adding your settingsProvider ID to the configuration descriptions list of settings providers:
1. externalSettingsProviders = new LinkedHashSet<String> (Arrays.asList(ICConfigurationDescription.getExternalSetting sProviderIds()));
2. extSettings.add(ID)
3. ICConfigurationDescription.setExternalSettingsProviderIds(ex ternalSettingsProviders.toArray(new String[0]));
4. You will get a call-back on:
1. public CExternalSetting[] getSettings(IProject project, ICConfigurationDescription cfgd) {
5. which allows you to return appropriate macros and includes for the given configuration desc.
6. CDT will cache this response, when there is a configuration change which may require a change to your settings, you should call:
1. cfgd.updateExternalSettingsProviders(new String[] {ID});

Bug 222738 has an attachment with a sample plugin employing this technique. You can download it to get started.

Report message to a moderator

Re: Programatically create a project? [message #515785 is a reply to message #513953]

Sat, 20 February 2010 19:01

Eugene K is currently offline

Friend

Messages: 11
Registered: February 2010

Junior Member

Thanks, Yevgeny!

I'll take a look at the org.eclipse.cdt.core.externalSettingsProvider extension point and bug 222738. Although, there are lots of bits and pieces all over the net on how to create CDT project none of the methods provides single 'clean' method or maybe I was just looking in wrong places.

BTW, is this forum the right place to ask these types of questions?

Eugene

Report message to a moderator

Re: Programatically create a project? [message #517408 is a reply to message #515785]

Sat, 27 February 2010 15:29

Yevgeny Shifrin is currently offline

Yevgeny Shifrin

Friend

Messages: 208
Registered: July 2009

Senior Member

Eugene K wrote on Sat, 20 February 2010 14:01

BTW, is this forum the right place to ask these types of questions?

Eugene

I think this is the right place for such questions. There is also cdt-dev mailing list. For details please refer to https://dev.eclipse.org/mailman/listinfo/cdt-dev

Thanks,
Yevgeny

[Updated on: Sat, 27 February 2010 15:30]

Report message to a moderator

Re: Programatically create a project? [message #518736 is a reply to message #517408]

Thu, 04 March 2010 20:40

Eugene K is currently offline

Friend

Messages: 11
Registered: February 2010

Junior Member

Yevgeny and all,

I think that I figure out clean way of programmatically creating CDT project. Pulled it from the bits and pieces.

- Start with buildDefinitions extension point and define projectType with all required children
- Use ManagedBuildManager static methods to create managed project and configuration. Interfaces are used here so everything comes out clean as was mentioned before in this post

createConfigurationClone()(why ?) did not work for me but createConfiguration() did. Created project can support STD Make and Managed Make approaches out of the box. It is just a check box.

However, I ran into another problem with Output Location Tab. I used this code to set up different output paths for configurations:

ICOutputEntry[] outEntry = new ICOutputEntry[1];
outEntry[0] = new COutputEntry(outputPath, null, ICSettingEntry.OUTPUT_PATH);
buildSetting.setOutputDirectories(outEntry);

It works fine if project is created as STD make but gives me "Duplicate path entries found" in problems view when project is created as Managed Make (setManagedBuildOn(true)). It looks like for managed make projects output location is not accepted at all. When I switch back to STD project then Output Location tap shows the same entries for all configurations. This tab is not present for managed make projects, why?

Can someone please, point me in the right direction on how to get rid of this warning for Managed Make project?

Thank you in advance,
Eugene

Report message to a moderator

Switch to threaded view of this topic

Create a new topic

Submit Reply

Previous Topic:	DSF-GDB non-stop-mode with Cygwin
Next Topic:	Problem with executing dsf-gdb JUnit tests

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 23 09:30:06 GMT 2024

Powered by FUDForum. Page generated in 0.09391 seconds

.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top