embeddedsw icon indicating copy to clipboard operation
embeddedsw copied to clipboard

Several files will not compile for C++

Open PCrabbeIMMT opened this issue 11 months ago • 10 comments

When attempting to compile our project in C++ against the embeddedsw repo, there are several headers that cause build failures. The ones we have run into are as follows:

  • xdp.h: Missing extern "C" {}
  • xdp_hw.h: Missing extern "C" {}
  • xv_tpg.h: _Bool is not defined, had to include stdbool.h to solve this. Shouldnt this just match what other functions have done (use u8?).
  • i2stx_chsts.h: Missing the closing brace for the extern "C"
  • i2srx_chsts.h: Missing the closing brace for the extern "C"

We have patched it on our end, but it would be greatly appreciated for these to be fixed upstream.

PCrabbeIMMT avatar Mar 21 '24 05:03 PCrabbeIMMT

Too bad. Could you send a PR?

keryell avatar Mar 21 '24 18:03 keryell

Too bad. Could you send a PR?

The PR template says "Please do not submit a Pull Request via github. Our project makes use of mailing lists for patch submission and review.", I can submit a patch unless the maintainer specifically wants a PR?

Note: Replying from my personal account

MajorArkwolf avatar Mar 22 '24 00:03 MajorArkwolf

Interesting. I will investigate internally about this non-PR story. @tejus26

keryell avatar Mar 22 '24 01:03 keryell

@msreeram-xilinx , @saddepal or @vsrik should be able to help.

tejus26 avatar Mar 22 '24 01:03 tejus26

I do have the changes for the two issues I have raised and I can point them to this repo if you guys would like me to.

See: https://github.com/MajorArkwolf/embeddedsw/pull/1 https://github.com/MajorArkwolf/embeddedsw/pull/2 https://github.com/MajorArkwolf/embeddedsw/pull/3

MajorArkwolf avatar Mar 22 '24 02:03 MajorArkwolf

hi @saddepal can you please forward to respective to check the issue.

msreeram-xilinx avatar Mar 22 '24 04:03 msreeram-xilinx

Note that I also raised another issue for build failures in C++ as well: https://github.com/Xilinx/embeddedsw/issues/294

PCrabbeIMMT avatar Mar 22 '24 04:03 PCrabbeIMMT

Yes @PCrabbeIMMT - we will take a look at #293 and #294

vsrik avatar Mar 22 '24 04:03 vsrik

Yes @PCrabbeIMMT - we will take a look at #293 and #294

Perhaps this is a good opportunity to experiment a move to a more inclusive open-source workflow based only on GitHub instead of using Jurassic mail-based patches for simple changes without IP issues?

keryell avatar Mar 22 '24 17:03 keryell

I have emailed 3 patches to resolve #293 and #294

PCrabbeIMMT avatar Mar 25 '24 02:03 PCrabbeIMMT