Share projects for collaborative work

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Share projects for collaborative work

Jump to solution
988 Views
GGil
Contributor I

Hello, between 2 colleagues we want to merge different projects #s32k144evb (done in S32) IDE that are working in isolation
The issue is that this is not as simple how to share source code with GitHub, because of: the link to the components; libraries; the pin settings done in processor expert; etc.
Is there a simple way to manage it?
Kind regards
Gustavo

 

0 Kudos
Reply
1 Solution
951 Views
mikedoidge
NXP Employee
NXP Employee

Hello Gustavo,

The ability to merge projects as you described, really comes down to the pre-planning. The fewer differences created at the beginning will make this easier for merging later. For example, ensuring both projects are using the same version of SDK, same pin settings, etc. Then it is more of a merge of application files. However, this must be done manually. No automated way could be trusted to make the correct merge choices, except perhaps for some well trained AI engine.

Good luck!

Mike

View solution in original post

2 Replies
906 Views
kamilla_peixoto
Contributor II

Hello, Gustavo!

The alternative you can try is to export the Processor Expert components of one project and import it on the other one. For that, you may follow those steps:

  1. Export the Processor Expert Component Settings:
    1. On the Project Explorer Panel, right click on the project to be cloned and select the option Export.
  2. On the Export Tab, select the Export Component Settings option.
  3. On the Export Processor Expert Component Setting Tab:
    1.      Select the project you want to export;
    2.      Select all the processors and components desired;
    3.      Chose the file’s location and name;
    4.      Click on Finish.
  4. Create a new project (or use one of the projects you want to merge): 
    1. Click on File->New->S32DS Application project.
    2. Define the name of the new project, chose the corresponding processor for your application, and proceed to the next tab.
    3. On the New S32DS Project tab, chose the ProcessorsName_SDK_gcc on the SDKs option.
  5. Import the Processor Expert Component Settings:
    1. On the Project Explorer Panel, right click on the created projected and select the option Import…
    2. On the Import Tab, select Component Settings to Project.
  6. On the Import Processor Expert Component Settings Tab:
    1. Select the file created previously;
    2. Select the new project;
    3. Verify the list of components to be imported and their respective modes. Note that this component list varies accordingly to the original project.
  7. On the Components Tab click on the Generate Processor Expert Code icon.

After those steps, the file ProcessorExpert.pe should appear on the file list of the new project on the Project Explorer Panel. And all the components should be available on the Processor Expert. However, in some cases, conflicts between different dialects of the programming language used and the optimization parameters set could appear. To fix these issues, go to Project->Properties and:

  1. C/C++ Build -> Settings -> Standard S32DS C Compiler -> Dialect, and chose the corresponding language standard.
  2. C/C++ Build -> Settings -> Standard S32DS C Compiler -> Optimization, and chose the desired optimization settings.

After applying those changes, a pop-up will ask if you want to rebuild it now. After confirming it, the project is ready, and you can import the second project.

I hope my answer helps you.

Regards,
Kamilla 

0 Kudos
Reply
952 Views
mikedoidge
NXP Employee
NXP Employee

Hello Gustavo,

The ability to merge projects as you described, really comes down to the pre-planning. The fewer differences created at the beginning will make this easier for merging later. For example, ensuring both projects are using the same version of SDK, same pin settings, etc. Then it is more of a merge of application files. However, this must be done manually. No automated way could be trusted to make the correct merge choices, except perhaps for some well trained AI engine.

Good luck!

Mike