octave-maintainers
[Top][All Lists]
Advanced

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

Re: Miscellaneous build warnings


From: Daniel J Sebald
Subject: Re: Miscellaneous build warnings
Date: Mon, 3 Jul 2017 16:31:38 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0


On 07/03/2017 04:11 PM, Torsten wrote:
On 03.07.2017 20:30, Torsten wrote:
On 03.07.2017 19:05, Rik wrote:
I'm seeing the following when building Octave:

libgui/src/settings-dialog.ui: Warning: The name 'horizontalLayout_17'
(QHBoxLayout) is already in use, defaulting to 'horizontalLayout_171'.
libgui/src/settings-dialog.ui: Warning: The name 'horizontalSpacer_33'
(QSpacerItem) is already in use, defaulting to 'horizontalSpacer_331'.
src/shared-fcns.h:174:1: warning: ‘std::__cxx11::string
prepend_octave_home(const string&)’ defined but not used [-Wunused-function]

None of this looks tragic, but maybe someone knows if they can be silenced.

I will have a look at it.

While trying to silence the warnings from settings-dialog.ui I get the
following error during compilation:

../libgui/src/main-window.cc: In member function ‘void
main_window::display_release_notes()’:
../libgui/src/main-window.cc:462:39: error: ‘octave::config’ has not
been declared
       std::string news_file = octave::config::oct_etc_dir () + "/NEWS";
                                       ^

This does not seem to be related to the warnings?

I'm seeing the same thing in a different part of the build. I think this ties in with the third warning:

src/shared-fcns.h:174:1: warning: ‘std::__cxx11::string
prepend_octave_home(const string&)’ defined but not used [-Wunused-function]

because it is the octave-config.in.cc file, in particular initialize(), that uses the prepend_octave_home() routine to create some configuration variables in the Octave variable space. JWE is in the process of sizeable reorganizing, so we'll leave it to his train of thought. Once configuration variables comes back in via octave::config, that third warning should disappear on its own.

Dan



reply via email to

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