Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
AW: [cdt-dev] How to setup a toolchain for a Standard Make Prj

Ok, I got a step further now. I used org.eclipse.cdt.build.makefile.projectType for the projectType in the “template” extension element of the extension point org.eclipse.cdt.core.templates. I got this info from the source of org.eclipse.cdt.managedbuilder.gnu.ui. I also removed all references to org.eclipse.cdt.build.core.buildArtefactType.exe, because I want to add a Makefile project template. Now I can see my new project template under the folder “Makefile project”. After selecting it I’m also able to select my own tool-chain.

On the next project wizard page I want to be able to select a folder from my local drive and add it to the source locations as a linked folder. In my template I added the following property:

 

<property

id="comproot"

label="Components root"

description="Select components root"

type="browse"

mandatory="true"

persist="true"

> 

</property>

 

The problem now is that I can’t select a folder in the browse dialog that appears, I can only select a file. How can I change this behaviour? Or do I have to implement a folder browse dialog on my own? The next question is how can I add the previously selected folder as a linked folder to the project? Is this possible with the org.eclipse.cdt.core.CreateSourceFolder process type or with the org.eclipse.cdt.core.AddLink process type, or do I have to create my own process type for this task?

If I got it right, then I will have to create a new project using the org.eclipse.cdt.managedbuilder.core.NewManagedProject process type, correct? Can I use this process type also for Standard Make projects?

 

Thanks,

Thomas

 


Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@eclipse.org] Im Auftrag von Merx, Thomas
Gesendet: Donnerstag, 23. Oktober 2008 14:19
An: CDT General developers list.
Betreff: [cdt-dev] How to setup a toolchain for a Standard Make Prj

 

Eclipse SDK Version: 3.3.2

CDT Version: 4.0.3

 

Hello,

 

I am currently trying to setup a tool chain for a Scons based build process. Now I have several questions that I can’t figure out from the documentation or FAQ. First of all I suppose that for such an external build process the “Standard Make” model is more suitable than the “Managed Make”, isn’t it?

What I’ve tried so far is that I added a projectType to the extension point org.eclipse.cdt.managedbuilder.core.buildDefinitions like the one below:

 

<extension

         point="org.eclipse.cdt.managedbuilder.core.buildDefinitions">

      <projectType

            buildArtefactType="org.eclipse.cdt.build.core.buildArtefactType.exe"

            id="mytoolchain.executable"

            isAbstract="false"

            isTest="false">

         <configuration

               buildArtefactType="org.eclipse.cdt.build.core.buildArtefactType.exe"

               errorParsers="org.eclipse.cdt.myerrorparser"

               id="mytoolchain.configuration.debug"

               name=" Debug">

            <toolChain

                  id="org.eclipse.cdt.mytoolchain.toolChain3"

                  superClass="org.eclipse.cdt.mytoolchain.toolChain1">

            </toolChain>

         </configuration>

      </projectType>

      <toolChain

            id="org.eclipse.cdt.mytoolchain.toolChain1"

            isAbstract="true"

            name="My Tool Chain"

            osList="win32"

            supportsManagedBuild="false">

         <builder

               command="Build.bat"

               id="org.eclipse.cdt.mytoolchain.builder1"

               name="My Builder"

               supportsManagedBuild="false">

         </builder>

         <tool

               command="Build.bat"

               id="mytoolchain.compiler"

               name="My Compiler"

               natureFilter="both"

               supportsManagedBuild="false">

            <inputType

                  dependencyContentType="org.eclipse.cdt.core.cHeader"

                  id="mytoolchain.compiler.input"

                  name="My Compiler Input"

                  primaryInput="true"

                  sourceContentType="org.eclipse.cdt.core.cSource">

            </inputType>

            <outputType

                  buildVariable="OBJS"

                  id="mytoolchain.compiler.output"

                  name="My Compiler Output"

                  outputs="obj"

                  primaryOutput="true">

            </outputType>

            <optionCategory

                  id="mytoolchain.compiler.optionCategory.general"

                  name="General"

                  owner="mytoolchain.compiler">

            </optionCategory>

            <option

                  browseType="directory"

                  category="mytoolchain.compiler.optionCategory.general"

                  command="-i"

                  id="mytoolchain.compiler.general.incpath"

                  name="Include paths"

                  valueType="includePath">

            </option>

            <option

                  category="mytoolchain.compiler.optionCategory.general"

                  command="-D"

                  id="mytoolchain.general.defines"

                  name="Defines"

                  valueType="definedSymbols">

               <listOptionValue

                     builtIn="false"

                     value="SCONS">

               </listOptionValue>

            </option>

         </tool>

      </toolChain>

   </extension>

 

Additionally I added a new template here:

 

   <extension

         point="org.eclipse.cdt.core.templates">

      <template

            id="org.eclipse.cdt.mytoolchain.template1"

            location="templates/MyPrjTemplate.xml"

            projectType="org.eclipse.cdt.build.core.buildArtefactType.exe">

         <toolChain

               id="org.eclipse.cdt.mytoolchain.toolChain3">

         </toolChain>

      </template>

   </extension>

 

What I now would expect is that I see my new Template under the Executable folder in the new Project Wizard and that I can select my own defined tool chain after selecting my new template. What I really get is that my tool chain can only be selected if I select the “Makefile project” folder. My template however is not available at all. If I then insert a name for the projectType in the buildDefinitions extension above I can see my template in parallel to the existing folders and can also select my tool chain, however my template isn’t executed. Can somebody tell me how to fix this issue?

Another question I have is how can I add a template to the folder “Makefile project”? I’ve only seen IDs to add templates to the exe, shared and static lib folder but not to the Makefile project folder.

 

Any help is greatly appreciated.

 

Thanks,

Thomas Merx

 

 

*******************************************

Harman Becker Automotive Systems GmbH

Management Board: Dr. Klaus Blickle (Chairman), Dr. Udo Hüls, Michael Mauser, Regis Baudot

Chairman of the Supervisory Board: Ansgar Rempp | Domicile: Karlsbad |

Local Court Mannheim: Register No. 361395

 

*******************************************
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden.

*******************************************


Back to the top