On Wed, Jun 12, 2019 at 09:41:03PM +0530, nitish nagesh wrote: > | arm-cnos-linux-gnueabi-gcc -march=armv7-a > --sysroot=/build/tmp/sysroots/switch -DNDEBUG -g -O3 -Wall > -Wstrict-prototypes -O2 -pipe -ggdb3 -feliminate-unused-debug-types > -fdebug-prefix-map=/build/tmp/work/armv7a-cnos-linux-gnueabi/ops-openvswitch/1.0-r0_switch=/usr/src/debug/ops-openvswitch/1.0-r0_switch > -fdebug-prefix-map=/build/tmp/sysroots/x86_64-linux= > -fdebug-prefix-map=/build/tmp/sysroots/switch= -DOPS -fPIC -INone -I > /build/tmp/sysroots/dover/usr/include/python2.7 -c ovs/_json.c -o > build/temp.linux-x86_64-2.7/ovs/_json.o > > | ovs/_json.c:2:30: fatal error: openvswitch/json.h: No such file or > directory > > > > I tried several option, to the best of my knowledge, to pass he include > path to the build system (using include_dirs in setup.py, through > automake.mk etc). But I can’t seem to get my head around this. I am a > novice to yocto & autotools. I am starting to doubt if the approach I am > following is even correct?
I don't think that the OVS use of Python is very special. My guess is that your question can be answered by looking in some more generic place for advice on (cross?)compiling Python binary modules. I don't have experience in this particular area, so I'm not able to offer more useful advice than that. Maybe someone else will speak up, if we're lucky. _______________________________________________ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
