Alas, and alack, while it was indeed simple to patch up configure to use MagickCore-config if it exists, the end result was a complete failure when using ImageMagick7. They apparently deprecated and removed the main header file we use to access the ImageMagick API, "magick/api.h". They don't even mention *THAT* mess in their porting document.
This suggests that getting Xastir to build with ImageMagick7 may be a big effort. https://github.com/Xastir/Xastir/issues/148 So there you have it. Yes, Xastir only works with versions of IM up to 6, and that will probably stay the case for a while. On Tue, Jul 16, 2019 at 11:06:02AM -0600, we recorded a bogon-computron collision of the <[email protected]> flavor, containing: > Turns out Magick-config was deprecated in ImageMagick6, and they want us to > use MagickCore-config instead. > > I confirmed that the flags returned by FreeBSD's Magick-config for IM6 > are identical to those returned by MagickCore-config. > > Magick-config was removed in IM7. > > This is probably a simple matter to fix in Xastir's configure script, just > a matter of searching for MagickCore-config and using it if it's found, > and only searching for and using Magick-config if the new one isn't > (indicating > a really old IM install). > > We won't do a quickie release to address *this* issue. But it should be > fairly simple to get going, and then it's a matter of figuring out if doing it > actually lets us work with IM7, too. > > I've opened an issue on github for it: > > https://github.com/Xastir/Xastir/issues/147 > > On Tue, Jul 16, 2019 at 10:07:44AM -0600, we recorded a bogon-computron > collision of the <[email protected]> flavor, containing: > > I lied. I went ahead and deinstalled inkscape and IM6, then installed IM7 > > to test if Xastir could work with it. > > > > I can indeed confirm that at this time Xastir won't build against > > ImageMagick7 > > just yet. It's not clear exactly whether it COULD work, but at this point > > configure isn't even able to tell it exists. > > > > Xastir's configure script uses the "Magick-config" script that > > ImageMagick6 installs to determine the CFLAGS, LDFLAGS, and LIBS needed to > > link against Magick libraries, and ImageMagick7 has replaced that script > > with three different ones, and it is not clear which one corresponds to what > > we need at this point. In order to support Magick7 we'll have to figure > > out which of those three scripts actually gives the correct values for us > > to find the appropriate libraries and headers to get the "WriteImage" > > function > > linked in (which is what configure tests for), *AND* confirm whether > > anything > > we're doing with Magick uses features they deprectated in 6 and removed in > > IM7. > > > > The good news is that we had a little fire drill for the last release where > > we rooted out all the deprecation warnings, and that may save us here if > > we can get the right LIBS, LDFLAGS, and CFLAGS out of some Magick*-config > > script. > > > > Hooray for IM. It may be just a matter of adjusting configure to look > > for extra scripts (MagickWand-config?), or it may be a deeper problem. At > > any rate, we'll certainly not get it solved today. > > > > For now, you are probably best either forcing a dependency on IM6 for the > > BSD > > port (just as the Inkscape port does at the moment) *OR* go back to the old > > plan of using GM and gcc. > > > > As someone who has carefully avoided ever volunteering to maintain any > > ports, I > > don't know how difficult this will be, but I recommend that you craft your > > port so the user has the option of installing it with either IM6 or GM. > > Naturally, the GM selection will force you to use gcc, but this is the only > > option available for getting a real, functional Xastir if IM7 is already > > installed. > > > > We'll have to dig a little to see if we can make IM7 work with Xastir, but > > I wouldn't count on it happening fast enough to address your immediate > > concerns > > of getting the BSD port updated and unbroken. > > > > On Tue, Jul 16, 2019 at 08:20:25AM -0600, we recorded a bogon-computron > > collision of the <[email protected]> flavor, containing: > > > On Tue, Jul 16, 2019 at 06:21:50PM +1000, we recorded a bogon-computron > > > collision of the <[email protected]> flavor, containing: > > > > Hi Tom, > > > > > > > > > On 16 Jul 2019, at 12:14 pm, Tom Russo <[email protected]> wrote: > > > > > > > > > > Years ago, ImageMagick was so frequently breaking their API that we > > > > > went to > > > > > preferring GraphicsMagick -- if configure detects both, it uses > > > > > GraphicsMagick. > > > > > But if only IM is installed, or if both are installed and GM doesn't > > > > > work, > > > > > we use IM. > > > > > > > > FreeBSD now has both v6 and v7 of ImageMagick in ports. it looks to me > > > > like Xastir only supports ImageMagick v6? Can you confirm that? > > > > > > I can't confirm at the moment. My system has Magick6 installed to satisfy > > > the inkscape dependency, and I can't play around right now to test if > > > Xastir > > > will build against Magick7, or dig into the differences between 6 and 7 to > > > see if Xastir is doing anything screwy with deprecated Magick6 features > > > that > > > were removed in 7. > > > > > > -- > > > Tom Russo KM5VY > > > Tijeras, NM > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > [n-z][a-m] > > > > -- > > Tom Russo KM5VY > > Tijeras, NM > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > [n-z][a-m] > > > > _______________________________________________ > > Xastir mailing list > > [email protected] > > http://xastir.org/mailman/listinfo/xastir > > -- > Tom Russo KM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] -- Tom Russo KM5VY Tijeras, NM echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] _______________________________________________ Xastir mailing list [email protected] http://xastir.org/mailman/listinfo/xastir
