Posted by Vetch on 2017-03-15 10:59

Hello Kirill,
May you describe a way to reproduce?
Do you create projects from CubeMX or directly in Eclipse?
How do transfer the project from Mac to Windows and vice verse?
Waht is the SW4STM32 version?
Cheers
Vetch

Posted by kir on 2017-03-15 11:09

Hello Vetch,

Its easy to reproduce - just create a project with CubeMX on OSX, import to SystemWorkbench, save it.
Then, try to open the project on Windows and build it - you’d get “no makefile” because it does not have a valid build configuration anymore.

I’ve attached an example of .cproject from Mac.

All versions of SysWorkbench and Cube MX are very recent - I reinstalled them yesterday

Cheers
Kirill

Posted by Vetch on 2017-03-16 14:55

Hello Kirill,

Do you mean you copied/pasted the project from OSX to Windows?
On my side, I did the following steps without any issue :
- Generate a project from CubeMX on OSX;
- Import this project in SW4STM32 on OSX;
- Compile it (without error) in SWSTM32 on OSX;
- Right-click on the project >> Export > General >> Archive File ;
- Copy the archve (zip) in Windows and uncompress it;
- Import the project in SW4STM32 on Windows;
- Compile it (without error) in SWSTM32 on Windows;

So the Import/Export feature to transfer project through OSs is fully functional.
Cheers
Vetch

Posted by kir on 2017-03-16 22:23

Hi Vetch,

I’m using GIT to syncronise code. Perhaps, if you do “Export” you won’t see this problem.

In my case, I checkout the code in Windows that has been pushed from Mac. Of course, the paths are screwed, but they are easy to re-generate with the CubeMX.

The only problem with the above is in “.cproject” file. While it theory (let me know if I’m wrong) it must have the same structure in both OSX and Windows, it is not the case.

Here is what I did:
- Generate a project from CubeMX on OSX;
- Import this project in SW4STM32 on OSX;
- Compile it (without error) in SWSTM32 on OSX;
- Push to a GIT server;
- Pull the project from the GIT in Windows, then open .iot file with CubeMX and re-generate the project to refresh paths in Windows style;
- Import the project in SW4STM32 on Windows;
- Compile it (without error) in SWSTM32 on Windows;

Cheers
Kirill

Posted by jandyman on 2017-07-29 21:07

Vetch,

Are you saying the project files are NOT compatible between Windows and Mac? Because having an export/import capability doesn’t make them compatible.

I’m doing the same thing that Kirill is doing with GIT, even though the problem I’m dealing with is slightly different than his. I’m a developer using OpenSTM32 on the Mac (where it seems to run much faster and more smoothly), some of our other developers are using Windows, on the same project. Export/Import does not work for this model of development.

Is the way we are using it not supported? At a distance, it seems much easier to make the project formats compatible than to use an export/import facility. So I’m a little confused.