On Thu, Jan 26, 2017 at 11:37 PM, Vidhumouli Hunsigida <[email protected]> wrote: > Hi Brian, > > It would help us if you can get us any details of the issues. > As mentioned, user is free to use his own tool chain to build app and debug > from Xilinx SDK and get all Xilinx SDK benefits which is beyond simple build > and debug. > > Regards, > Vidhumouli >
Hi Vidhumouli, Thanks. No, I don't have specifics yet. I'm kind of standing at a crossroad and just trying to figure out which road to take and what the journey may be like along the way so I don't have to go down several only to have to turn around (aka, jerking around the app developers). It's like that gameshow where you have to pick what's behind door #1, #2 or #3. I don't want to get into a situation where I'm asked to name names but I was hitting a xilinx employee that I know with some of these questions and the warning of the incompatible aspects I previously mentioned mixing Xilinx and Yocto came from him. I am interested in doing what you said and setting up the Xilinx SDK to use my Yocto generated SDK (toolchain and sysroot) so that I may try out building a hello world type app with Xilinx SDK and using the Xilinx debugging tools (tcf agent if I recall correctly etc.) to make sure they work and the scripts to generate device trees from HDF (the guys using Vivado for hardware are in different country than the ARM guys doing the app). I'll be more than happy to check out and try whatever info you have on the subject! :) I appreciate the input and hope it allows me to figure out which direction we should go in soon. Regards, Brian -- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
