|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #49653] Build failure with ImageMagick |
Date: | Sun, 30 Dec 2018 20:35:20 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 |
Update of bug #49653 (project octave): Priority: 3 - Low => 1 - Later Release: 4.2.0 => dev _______________________________________________________ Follow-up Comment #6: This bug still affects the current stable and default branches. I think we would still be open to a patch that fixes building Octave with ImageMagick from someone affected by this. But "using namespace Magick;" isn't an appropriate fix, we try to avoid importing entire namespaces into Octave sources. The following minimal examples all show the same error: #include <Magick++.h> int x = MaxRGB; #include <Magick++.h> int x = QuantumRange; #include <Magick++.h> int x = Magick::QuantumRange; #include <Magick++.h> int x = MagickCore::QuantumRange; _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?49653> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |