You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, I::M makes a blib/Inline, then works from there.
The alternative idea is that instead of working into blib/Inline and trying to hide your work, it could generate a *.xs file next to the *.pm, in the same spirit as a *.xs is used to make a *.c, then *.o, etc. Then the normal build system could take over and install the *.so into blib, as normal.
Likely benefits are this will reduce the amount of code in hooking into the build systems eg EUMM.
The text was updated successfully, but these errors were encountered:
I::M doesn't make a blib/Inline, it just tells Inline to use that as its DIRECTORY.
The whole point of Inline::Module is to just provide some minimal glue that let's Inline.pm and Inline::C work like normal and then have the results be in a place where module frameworks need them at various times. Inline::Module is currently under 500 lines and the plugins for dzil and module-build and such are tiny.
However I like the gist of your idea. I reinterpret it to mean, do more stuff author side and dist it, if the same thing would always happen user side. We might be able to get to just XS files but I'd rather take a safer refactoring approach.
It would be interesting if there were a method to make Inline::C return its *.xs file, probably akin to bind. That would make this task almost trivial.
Currently, I::M makes a blib/Inline, then works from there.
The alternative idea is that instead of working into blib/Inline and trying to hide your work, it could generate a *.xs file next to the *.pm, in the same spirit as a *.xs is used to make a *.c, then *.o, etc. Then the normal build system could take over and install the *.so into blib, as normal.
Likely benefits are this will reduce the amount of code in hooking into the build systems eg EUMM.
The text was updated successfully, but these errors were encountered: