gigapana.blogg.se

Virtualbox ubuntu file sharing
Virtualbox ubuntu file sharing









  • I do all other code/project editing (using vscode, etc.).
  • I do all the building (gcc, make, etc.).
  • So my idea is that I somehow create a shared folder on the VM which I can open in windows to edit the rhapsody files and generate the autogen code such that: We want to do away with the need to develop on windows. So there are plenty of #ifdef WIN32 bits of code around - we have a OS abstraction layer etc. The overhead of keeping windows side working is getting quit high and time consuming as the code wants to become more linux specific (it is designed to run on embedded linux systems). We have two jenkins servers (for windows and ubuntu).
  • On windows: re-test changes (debug if required).
  • virtualbox ubuntu file sharing virtualbox ubuntu file sharing

    On ubuntu: edit other areas of the code, test and debug.On windows: Test and debug the state changes.On windows: Edit Rhapsody state machines and generate code.On windows its with visual studio and rhapsody. So at the moment, we have full development environments in both windows and ubuntu. The issue here is that the folder that is shared is windows-side, and this folder format does not work for linux (git, make, gcc, etc.) since the permissions/types are all wrong (not to mention symlinks). So it sounds like I just need to setup a VM share. project/> makeīut this requires the VM folder and the windows folder to be shared. project/autogen/ all the rhapsody code is put into one folder called autogen. On windows draw the state machine with rhapsody and generate code->.

    virtualbox ubuntu file sharing virtualbox ubuntu file sharing

    What I need is a quick way to generate our state code and integrate it with the rest of the project. I am working on getting it working on newer versions and 64-bit - but that is a background task at the moment. Rhapsody runs well on windows, but is only supported by redhat version 6 32-bit. However we use IBMs Rhapsody to generate some state machine code - probably that was a mistake, but we are too far down the path to want to stop using it now, and its a good state machine tool - but a crappy IDE!. I use the ubuntu VM to develop our C++ code, all the tools and gcc etc working nicely. I have a windows 10 PC and on that I have an ubuntu 18.04 virtualbox (+ guest editions) and its all working well.











    Virtualbox ubuntu file sharing