Skip to content

conda-build abi3 with C++ binaries incorrectly detected as build scripts #6008

Description

@larsoner

Checklist

  • I added a descriptive title
  • I searched open reports and couldn't find a duplicate

What happened?

See conda-forge/openmeeg-feedstock#77 (comment), adapting from there:

The openmeeg feedstock produces several C++ executables such as om_mesh_smooth, plus a Python library that (SWIG-)wraps to some shared libraries. I'm trying to move this package to abi3, but I'm getting:

conda_build.exceptions.CondaBuildUserError: Noarch package contains binary script: om_mesh_smooth

This is a binary C++ executable, not a Python script. Is there some way to get it to ignore these when iterating in rewrite_script in conda-build?

@isuruf suggested I open an issue here about this since it seems like there isn't a way to do this currently.

I'm going to skip all the conda info etc. below since it's all part of the standard conda-forge feedstock infrastructure as of today (2026 June 9), and should be accessible at least for a while in the action run above.

Metadata

Metadata

Assignees

No one assigned

    Labels

    type::bugdescribes erroneous operation, use severity::* to classify the type

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions