You're using a side-effect of the low "avx-ness" of the plugins to create a
black-list. I'm worried that might have unintended consequences down the road.
Better to take a pattern to exclude from the move?
On 6/26/18, 3:12 PM, "Dev on behalf of Thiago Macieira"
<dev-bounces(a)lists.clearlinux.org on behalf of thiago.macieira(a)intel.com> wrote:
On Monday, 25 June 2018 11:40:38 PDT Thiago Macieira wrote:
I think the latter case is very rare and therefore I suggest we start
Well, I've managed to reduce the script to a few lines. This is what gets
added to the .spec file:
mkdir -p haswell
find -L . -type f -maxdepth 1 -print0 | xargs -tr0 mv -t haswell/
find -H . -type f -name '*.so' -print0 | xargs -tr0I@ mv @ @.avx2
I did a quick test with a small module (qtserialbus) and the results can be
seen in the relevant parts of the build log (attached). The resulting .spec
file has the main libs in /usr/lib64/haswell, but the plugins got deleted due
to low score.
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center