Joshua Brindle wrote:
Daniel J Walsh wrote:
What do you think of this one. Removed excess swig cruft,
You need to run
make swigify to generate those changes.
Ok, looking at this now. I don't completely get how it works. I'm trying
to reproduce what you are doing by hand but nothing comes out of gcc:
[root@localhost src]# echo '#include "../include/selinux/selinux.h"' >
temp.c
[root@localhost src]# gcc -c temp.c -aux-info temp.aux
[root@localhost src]# ls temp.*
temp.c temp.o
What is the purpose of the aux-info thing, and why doesn't it work on my
F11 machine?
also, I'm not sure if the best place for selinuxswig_exception.i is
swigify or pywrap. In the swigify case it shouldn't be in the clean
target because if you check out the repo and do make clean; make pywrap
you'll get an error. (I can make these fixes, I'm just trying to figure
out how it all works first).
Oh, one more thing, should this be python specific? (E.g, should it be
named selinuxswig_python_exception.i ?)
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.
