[Top][All Lists]

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

[Octave-bug-tracker] [bug #41636] mkoctfile doesn't accept -std=c++11 op

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #41636] mkoctfile doesn't accept -std=c++11 option
Date: Wed, 19 Feb 2014 00:55:51 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36

Update of bug #41636 (project octave):

                  Status:                    None => Need Info              
        Operating System:       Microsoft Windows => Any                    


Follow-up Comment #1:

The most straightforward way currently is through the use of environment
variables. If you're running mkoctfile from a shell, something like

$ CXXFLAGS="$(mkoctfile -p CXXFLAGS) -std=c++11" mkoctfile ...

should work. If you're using the Octave function, then maybe something like

octave:1> setenv ("CXXFLAGS", [octave_config_info.CXXFLAGS " -std=c++11"]);
octave:2> mkoctfile ...

Does that work for you or do you still have the need to pass -std options as
options to mkoctfile?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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