Skip to content

Is it possible to link with xsl's output using only public APIs? #79

Description

@creationix

From what I can tell, the xsAll.h header is meant for internal use and brings in all kinds of sx. and fx... namespacing whereas the xs... symbols in xs.h and xsmc... in xsmc.h looks public.

I'm having trouble including xsAll.h in my main.cpp file. I get all kinds of compiler errors, it looks like it brings in code that's not valid C++.

I'd love to stick to just xs.h or xsmc.h, but I can't seem to figure out how to hook up the xsl output since it uses the txPreparation* xsPreparation() function in mc.xs.c (which isn't even in the mc.xs.h so I'm thinking this is a private API as well)

Please tell me there is a way to keep xsc and xsl in my workflow, but avoid xsAll.h and extern txPreparation* xsPreparation().

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions