ok, I'm back and caffeinated :) If you go to http://p3rl.org/Module::Build::WithXSpp and look at https://metacpan.org/pod/Module::Build::WithXSpp#FEATURES-AND-CONVENTIONS it says
By default, Module::Build::WithXSpp will automatically generate a main XS file for your module which includes all XS++ files and does the correct incantations to support C++.If Module::Build::WithXSpp detects any XS files in your module, it will skip the generation of this default file and assume that you wrote a custom main XS file.
So I think that answers that
If you go to https://metacpan.org/pod/Module::Build::WithXSpp#JUMP-START-FOR-THE-IMPATIENT it describes the expected layout
So if your module_name is GenoEye (GenoEye.pm) and you have some .xs files (GenoEye_Page.xs) but you don't have GenoEye.xs, then GenoEye.xs (module_name.xs) won't be generated for you (because of GenoEye_Page.xs)
So what you're missing is a GenoEye.xs (module_name.xs) which you need to create , something like WithIntAndString.xs something that uses
INCLUDE_COMMAND: $^X -S xsubpp -- GenoEye_Page.xs
I prefer running examples to reading docs, easier to figure out what docs to read instead of reading all the docs
In reply to Re: Module::Build::WithXSpp does not correctly handle XS files correctly? ( module_name.xs )
by Anonymous Monk
in thread Module::Build::WithXSpp does not correctly handle XS files correctly?
by llancet
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |