[meta-xilinx] Can Xilinx SDK (XSDK - Eclipse IDE) be integrated with Yocto SDK?

[Vidhumouli Hunsigida]

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

-----Original Message-----
From: meta-xilinx-bounces at yoctoproject.org [mailto:meta-xilinx-bounces at yoctoproject.org] On Behalf Of Brian Hutchinson
Sent: Friday, January 27, 2017 2:50 AM
To: meta-xilinx at yoctoproject.org
Subject: Re: [meta-xilinx] Can Xilinx SDK (XSDK - Eclipse IDE) be integrated with Yocto SDK?

Thanks for the replies and ideas.

I forgot to mention it in the original email but my main concern is with some things I "heard" but haven't experienced yet.  I'm aware that the Xilinx SDK (and the Petalinux tools etc.) use a fixed Linaro toolchain while Yocto+meta-xilinx default to building a gcc toolchain.
I've "heard" that this can cause problems when trying to use XSCT and tcf-agent stuff ... debuggers etc. in the Xilinx SDK while using rootfs and user space apps built with Yocto.

This makes me wonder if I should just give up on using Xilinx SDK (would need to use gdb and other debug tools in that case I guess - which could upset some folks) and make folks that insist on using an IDE for application development to use plain Eclipse (or with Yocto
plugin) or make Yocto builds use external Linaro toolchain to make deliverables that will work with whatever version of toolchain the Xilinx SDK is using.

These are all new decisions/issues I've not had to contemplate before we started using Zync stuff.

Regards,

Brian
--
_______________________________________________
meta-xilinx mailing list
meta-xilinx at yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx


This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.