path -> patch, I lost characters sometimes :) вс, 5 апр. 2020 г., 23:17 Alexander Oryshchenko <a.oryshche...@gmail.com>:
> Hi, > > For second your question I can little bit help you. I wrote path which > replases "ln" command in link.sh with Windows links. Then both WLS and > Windows understand it fine and you will not need to create directory and > copy. But I have no idea about your first question. > > -Alexander > > вс, 5 апр. 2020 г., 23:12 Eduard Niesner <niesneredu...@gmail.com>: > >> Hi Alexander, >> >> I debug my application using Visual Studio and when I try to step-in a >> function from Nuttx it looks for the source files in >> C:\SysGCC\arm-eabi\mnt\d\work\NuttxH7\Nuttx\arch\arm\src\ >> *chip\<filename>.c. *Since the "chip" folder is a simbolic link and is not >> accessible from Windows, Visual Studio cannot access it either. >> >> Since Visual Studio looks for the files in the "chip" folder, I need to >> create it and copy the files from stm32H7 to it. This way, I am able to >> debug my application and step in Nuttx functions as well. >> I did not have the two issues from my initial email when I build Nuttx >> with >> Cygwin. I remember that the Nuttx/Apps repositories could not anywhere on >> my PC and also, the chip folder was always created after a successful >> build >> and its content was identical to the stm32H7 folder. So I did not have to >> do anything ... I was just doing a build and using the .a library in my >> application and I was able to debug just fine. >> >> Also, I dont want to go back to Cygwin because in my experience, Cygwin is >> very slow compared to Ubuntu Bash. I am looking for a solution so that I >> dont have do the two steps (copy Nuttx and Apps in the " >> C:\SysGCC\arm-eabi\mnt\d...." and copy stm32H7 content in chip folder.) >> >> Thank you, >> Edi >> >> On Sun, Apr 5, 2020 at 9:46 AM Alexander Oryshchenko < >> a.oryshche...@gmail.com> wrote: >> >> > Hello Eduard, >> > >> > Regarding you second question. >> > arch/arm/source/chip and board are symbolic links. They are accessible >> > under WSL (but at least for me inaccessible in Windows). But why do you >> > need to copy something here? >> > >> > -Alexander >> > >> > On Sat, Apr 4, 2020 at 11:39 PM Eduard Niesner <niesneredu...@gmail.com >> > >> > wrote: >> > >> > > Hi all, >> > > >> > > I am using the Nuttx build as a static library (*.a file) in my >> > application >> > > and in order to debug Nuttx I have to do some steps that I did not >> have >> > to >> > > do in the past: >> > > >> > > 1. Copy Nuttx and Apps folders to the following directory >> > > C:\SysGCC\arm-eabi\mnt\d\work\NuttxH7 >> > > - I know that in the past the static library had the right debug >> > > symbols and was always pointing to the right file location in my >> > > Nuttx/Apps >> > > folders. >> > > - I checked the debug symbols from the nuttx static library >> using >> > > eabi-objdump and it seems like the paths do not point to my >> > > Nuttx/Apps >> > > folders anymore - now, they all point to >> > C:\SysGCC\arm-eabi\mnt\d.... >> > > - I recently changed from using Cygwin to Ubuntu Bash under >> Windows >> > > 10 because it is a lot faster than Cygwin. Can this be the >> reason >> > > why the >> > > paths in the static library have changed to >> > > C:\SysGCC\arm-eabi\mnt\d...? >> > > - If yes, is there a option in Nuttx or in Ubuntu Bash to >> generate >> > > the correct paths? >> > > 2. Copy the content from >> > > C:\SysGCC\arm-eabi\mnt\d\work\NuttxH7\Nuttx\arch\arm\src\*stm32h7* >> to >> > > C:\SysGCC\arm-eabi\mnt\d\work\NuttxH7\Nuttx\arch\arm\src\*chip* >> > > - I noticed that after a successful build the "chip" folder is >> not >> > > created anymore and instead there is a "chip" file. >> > > - Now I have to delete the "chip" file, create a "chip" folder >> and >> > > copy the source files from "stm32H7" folder. >> > > - Can this be related to the Cygwin vs Ubuntu Bash as well? >> > > >> > > Also, in my configuration the "Suppress Optimization" and "Generate >> Debug >> > > Symbols" are checked. >> > > >> > > Any suggestions are welcome. >> > > >> > > Thanks, >> > > Edi >> > > >> > >> >
