module-build-general

[Module::Build] order of extra_compile_flags in compile_c

[R. B. <ro...@pa...>]

I recently used Module::Build in my first CPAN project
(Device:Cdio). This is a OO Perl wrapper for my libcdio library and I
used SWIG to help me. (See ticket 17666 on rt.cpan.org; and many
thanksfor considering as an inclusion this after the next M:B
release.)

One thing that came up in this endeavor was the order or the C flags
in the compilation (compile_c).  It is helpful to turn off some gcc
warning messages until such time SWIG is fixed to not cause gcc to
emit them. So I changed the order of applying user cflags
(extra_compiler_flags) to come *after* the cflags that are picked up
as part of the Perl configuration (via Config). Another possibility is
to add a new option to allow cflags specified before *and* afterwards.

(If this is something I should add a ticket for in rt.cpan.org, let me
know.)

Thanks.

Re: [Module::Build] order of extra_compile_flags in compile_c

[Ken W. <ke...@ma...>]

Hi Rocky,

Are you suggesting that in general the extra_compiler_flags should come  
after the default flags?  I think that's reasonable.  The change would  
have to be made in ExtUtils::CBuilder though, yes?

  -Ken

On Feb 16, 2006, at 11:27 AM, R. Bernstein wrote:

> I recently used Module::Build in my first CPAN project
> (Device:Cdio). This is a OO Perl wrapper for my libcdio library and I
> used SWIG to help me. (See ticket 17666 on rt.cpan.org; and many
> thanksfor considering as an inclusion this after the next M:B
> release.)
>
> One thing that came up in this endeavor was the order or the C flags
> in the compilation (compile_c).  It is helpful to turn off some gcc
> warning messages until such time SWIG is fixed to not cause gcc to
> emit them. So I changed the order of applying user cflags
> (extra_compiler_flags) to come *after* the cflags that are picked up
> as part of the Perl configuration (via Config). Another possibility is
> to add a new option to allow cflags specified before *and* afterwards.
>
> (If this is something I should add a ticket for in rt.cpan.org, let me
> know.)
>
> Thanks.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log  
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel? 
> cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Module-build-general mailing list
> Mod...@li...
> https://lists.sourceforge.net/lists/listinfo/module-build-general

Re: [Module::Build] order of extra_compile_flags in compile_c

[R. B. <ro...@pa...>]

Ken Williams writes:
 > Hi Rocky,
 > 
 > Are you suggesting that in general the extra_compiler_flags should come  
 > after the default flags?  

I think so, but I pose this to the forum to get others' experience and
views. In the problems I encountered, it had to come after Perl's
Config C flags. If you want to hedge the bet, then two compiler_flags
can be used. (If one then I'd say after.)

 > I think that's reasonable.  The change would  
 > have to be made in ExtUtils::CBuilder though, yes?

I did a cut and past of compile_c from Module::Build::Base version
0.2611. Things may have changed since then. You would be in more of a
position to know.

Thanks for listening.