New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add CPPFLAGS argument for C preprocessor directives. Bump versions to 0.76 & avoid test/29* conflict. #45
Conversation
… 0.76 & avoid test/29* conflict.
@sisyphus |
Sorry I’m not empowered to make a pull request for either of those modules. On Jun 26, 2015, at 10:13 PM, sisyphus <notifications@github.commailto:notifications@github.com> wrote: @sisyphushttps://github.com/sisyphus — |
I believe I am empowered to perform the merge .... at least there's a "Merge pull request" button staring at me, just screaming out to be pressed. Plus I haven't paid a lot of attention to this thread, I'm old & stupid & lazy, with minimal git fu and I don't want to go stepping on someone else's toes. Sorry if I'm therefore being obstructionist; that's certainly not a role that I want to take on. As an interim fix can you get mileage from: Or do you really need to be able to specify CPPFLAGS separate from CCFLAGS ? Cheers, |
@sisyphus |
Add CPPFLAGS argument for C preprocessor directives. Bump versions to 0.76 & avoid test/29* conflict.
From: William N. Braswell, Jr. |
@sisyphus |
Can't you just upload your own "unofficial release" of Inline-C-0.76 to CPAN. I don't know whether I'm empowered to make an official release of Inline::C, but I certainly don't know the process for making one. Has Ed gone missing, too ? Cheers, |
I also do not know the procedure to release v0.76 to CPAN, and I do not wish to create unofficial releases if at all possible. |
The correct term for what I was thinking of is "Unauthorized Release". Basically, anyone can make one by simply uploading a source distro to CPAN. If you think that might be useful to you, let me know, and I'll upload that unauthorized Inline-C-0.76 tomorrow. (Hell, FAIK it might turn out to be an official release .... which might make things interesting. I'm assuming that I can't do any long lasting damage that couldn't be fixed by simply deleting my Inline-C-0.76 release from CPAN.) |
?If you put the 0.76 version on your site, I will certainly try it! Thank you - a. From: sisyphus notifications@github.com The correct term for what I was thinking of is "Unauthorized Release". Basically, anyone can make one by simply uploading a source distro to CPAN. If you think that might be useful to you, let me know, and I'll upload that unauthorized Inline-C-0.76 tomorrow. (Hell, FAIK it might turn out to be an official release .... which might make things interesting. I'm assuming that I can't do any long lasting damage that couldn't be fixed by simply deleting my Inline-C-0.76 release from CPAN.) Reply to this email directly or view it on GitHubhttps://github.com//pull/45#issuecomment-117056253. |
@sisyphus |
When combined with the pending Inline::Filters v0.17 code, this pull request solves Inline::C issue #42
perl11/Inline-Filters#1
This is a resubmitted pull request, to bump all version numbers to v0.76 (necessary for Inline::Filters dependency check), and to avoid test/29* file name conflict with @mohawk2's also-pending pull request.