> On Aug 12, 2020, at 10:12 AM, Benoit Ganne (bganne) <bga...@cisco.com> wrote: > > Hi Christian, > > Thanks for the head's up. > >> I think maybe the right thing to do here is create a custom cmake build >> rule to stage the entire python package in build-root/build* > > Alternatively, do you know if we can add an arbitrary file to be packaged by > setup.py? If we could just tell ssetup.py 'take also this absolute filename' > that would allow us to generate the vpp_ffi.py in build-root and left the > rest unchanged...
Not exaclty. I think if you made the generated file part of a sub-pkg maybe you could use this? https://docs.python.org/3/distutils/setupscript.html#listing-whole-packages <https://docs.python.org/3/distutils/setupscript.html#listing-whole-packages> Alternatively, is there a way to figure out if ASAN is required by the ffi dlopen at runtime? Then we wouldn't need to generate different source files. Thanks, Chris. > > Best > ben >
signature.asc
Description: Message signed with OpenPGP
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#17203): https://lists.fd.io/g/vpp-dev/message/17203 Mute This Topic: https://lists.fd.io/mt/75917538/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
