octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GSOC second part


From: John W. Eaton
Subject: Re: GSOC second part
Date: Mon, 06 Jul 2015 19:09:15 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.2.0

On 07/06/2015 06:22 PM, Carnë Draug wrote:
On 6 July 2015 at 22:13, Piotr Held <address@hidden> wrote:
[...]
I have published on the repo version 0.2.0. Should I try to get it to Octave
Forge? I am not sure if it's ready.

First of all, I use lambdas for one function, so I needed to add -std=c++11
to my CFLAGS (which I probably could rename CXXFLAGS). I don't have any
autoconf scripts to check if the compiler someone uses actually can compile
code using that flag. Do you have any ideas on this?
[...]

The image package also makes use of lambdas and requires that flag.  Take
a look at how it does it.

http://hg.code.sf.net/p/octave/image/file/e977104b2492/src/configure.ac

http://hg.code.sf.net/p/octave/image/file/e977104b2492/src/m4/ax_cxx_compile_stdcxx_11.m4

http://hg.code.sf.net/p/octave/image/file/e977104b2492/src/Makefile.in

Carnë


Modifying user variables like CPPFLAGS, CFLAGS, or CXXFLAGS in configure scripts is generally discouraged:


https://www.gnu.org/software/automake/manual/html_node/Flag-Variables-Ordering.html

Also, what will happen if -std=c++11 is not supported? Does building the entire package fail, or is a feature disabled? If possible, please make the lack of specific compiler features as harmless as possible.

Thanks,

jwe




reply via email to

[Prev in Thread] Current Thread [Next in Thread]